Re: Changing Query behavior based on local vs. remote context?
- From: "Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx>
- Date: Thu, 16 Aug 2007 16:08:14 -0400
Sounds like larger network packets are getting dropped. Some bridges that do not do packet splitting can cause this.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Keith" <keith@xxxxxxx> wrote in message news:%23Ej27KC4HHA.1824@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I'm not sure if this is the right ng for this question, but here goes...
I just installed a product that uses SQL Express. When I run queries against the installed instance I get different behavior depending on if the query is run from Management Studio locally or from SSMS running on a remote machine. In both cases the user is a domain admin and the query is identical. The local query returns 1000+ rows, the remote query returns ZERO. If the query returns less than say 100 rows, there is no difference between remote and local.
Has anyone else seen this or use use/implemented it themselves?
I'm curious; how this behavior is defined/implemented? Is it database or instance specific? It seems to be instance-wide in my case but I'm not sure yet. I've been digging around in SSMS but haven't found any settings or properties that seem to apply to this, so any sugestions on where to look would be appreciated.
Thanks!
Keith
.
- Follow-Ups:
- Re: Changing Query behavior based on local vs. remote context?
- From: Keith
- Re: Changing Query behavior based on local vs. remote context?
- From: Erland Sommarskog
- Re: Changing Query behavior based on local vs. remote context?
- References:
- 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?
- Next by thread: Re: Changing Query behavior based on local vs. remote context?
- Index(es):
Relevant Pages
|