Re: Changing Query behavior based on local vs. remote context?
- From: "Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx>
- Date: Thu, 16 Aug 2007 20:33:06 -0400
Unless you install the product on another machine and get the same behavior, which I have.
Considering that this behavior is present along with the installation of this particular product, and that other named SQL and SQL Express instances on the same machine do not demonstrate this behavior - even when returning result sets orders of magnitude larger and on the same physical network - I'm inclined to believe that this behavior is not machine specific but rather localized to the named instance installed by this particular product. Meaning, some configurable property of SQL Server.
Tidbits like these are always good to know. The answers we gave were based on the info given. I would ping the makers of the product then and see if they can provide a clue. Other than some ANSI settings at the connection or database object level that may return different results I know of no settings or configuration that would produce this behavior. Things like ANSI PADDING, ANSI NULLS etc can affect how SQL Server treats the data for joins and the Where clause which can produce different result sets. But none of that is based on the size of the result set. I would check to see if the connection settings are the same for both the local and remote SSMS. But like I said that doesn't explain all the symptoms you mention.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Keith" <keith@xxxxxxx> wrote in message news:O%23h0HtF4HHA.484@xxxxxxxxxxxxxxxxxxxxxxx
"Andrew J. Kelly" <sqlmvpnooospam@xxxxxxxxxxxx> wrote in message news:OeY8weE4HHA.3916@xxxxxxxxxxxxxxxxxxxxxxxOK then I would have to agree with Geoff in that it sounds like an issue with the servers communications. If you can run this fine locally and all other machines have issues it kind of narrows it down to that machine:).
Unless you install the product on another machine and get the same behavior, which I have.
Check the event logs and see if there are errors on that server.
The Event Viewer does not show any errors, nor does the error log in the instance's data directory.
Considering that this behavior is present along with the installation of this particular product, and that other named SQL and SQL Express instances on the same machine do not demonstrate this behavior - even when returning result sets orders of magnitude larger and on the same physical network - I'm inclined to believe that this behavior is not machine specific but rather localized to the named instance installed by this particular product. Meaning, some configurable property of SQL Server.
I'm totally willing to believe that this is a bug in the product - a misconfiguration of some kind - but it sounds like most folks don't think that this type of (mis)configuration is even possible.
Oh, did I mention that this is a Microsoft product's install of SQL Express ;-)
k
.
- References:
- Changing Query behavior based on local vs. remote context?
- From: Keith
- Re: Changing Query behavior based on local vs. remote context?
- From: Andrew J. Kelly
- Re: Changing Query behavior based on local vs. remote context?
- From: Keith
- Re: Changing Query behavior based on local vs. remote context?
- From: Andrew J. Kelly
- Re: Changing Query behavior based on local vs. remote context?
- From: Keith
- Changing Query behavior based on local vs. remote context?
- Prev by Date: Re: Changing Query behavior based on local vs. remote context?
- Next by Date: Re: Rights to execute jobs?
- 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
|
