Re: Changing Query behavior based on local vs. remote context?
- From: "Keith" <keith@xxxxxxx>
- Date: Thu, 16 Aug 2007 15:39:31 -0700
"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:erXXwEE4HHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
Sounds like larger network packets are getting dropped. Some bridges that
do not do packet splitting can cause this.
I should add that this behavior does not happen running queries against any
other SQL Express, SQL 2005, SQL 2000, or MSDE instance - named or
otherwise, physical or virtual machine - anywhere on my network.
Only this particular instance behaves this way.
.
- References:
- Changing Query behavior based on local vs. remote context?
- From: Keith
- Re: Changing Query behavior based on local vs. remote context?
- From: Geoff N. Hiten
- Changing Query behavior based on local vs. remote context?
- Prev by Date: Re: default schema (SQL Server 2005)
- Next by Date: Re: Changing Query behavior based on local vs. remote context?
- Previous by thread: Re: Changing Query behavior based on local vs. remote context?
- Index(es):