microsoft newsgroup web access
     dot net    |    ms sql    |    ms access    |    office    |    windows    |   
Microsoft ms sql group
sqlserver.ce
sqlserver.clients
sqlserver.clustering
sqlserver.connect
sqlserver.datawarehouse
sqlserver.dts
sqlserver.fulltext
sqlserver.msde
sqlserver.mseq
sqlserver.notificationsvcs
sqlserver.odbc
sqlserver.olap
sqlserver.programming
sqlserver.replication
sqlserver.reportingsvcs
sqlserver.security
sqlserver.server
sqlserver.setup
sqlserver.tools
sqlserver.xml
  
    

Server query processed at local and not remote SQL Server



Hi, I have a client who is conneting to my server from theirs via a linked
server they've set up.

They perform the following query:
DECLARE @abcid int

SET @abcid = 123

SELECT abc_id
FROM [Server1\NamedInstance1].DB01.dbo.View01
WHERE (abc_id = @abcid)

The execution plan in Qu. Analyser returns half a million rows from my
server then is filtered to just 11 rows that are required. The 'where'
statement is missing from the query execution plan.

The same query

Tue, 11 Jan 2005 18:47:03 -0800 "=?Utf-8?B?RGF2ZUE=?="

Re: Server query processed at local and not remote SQL Server



If the settings are exactly the same, the collation
compatible option is set to true and the collations are the
same on the servers, I'm not sure why different servers
would process the query differently. But one option to try
with Openquery is to build the SQL statement dynamically so
you can build in the parameter. Then pass the string you
build into an EXEC to execute the Openquery statement.

-Sue

On Tue, 11 Jan 2005 18:47:03 -0800, "DaveA"
wrote:

>Hi, I have a client who is conneting to my server from theirs via a linked
>server they've set up.
>
>They perform the following query:
>DECLARE @abcid int
>
>SET @abcid = 123
>
>SELECT abc_id
>FROM [Server


Wed, 12 Jan 2005 09:19:27 -0700 Sue Hoegemeier

Re: Server query processed at local and not remote SQL Server



I'd double check the provider being used for the linked
server, MDAC versions on the server and the linked server
configurations. Make sure they are using the SQL Server OLE
DB provider on both servers that link to your server. Also
they should check the dynamic parameters property for the
SQL Server OLE DB provider. They would want to restart the
service after making any changes to the provider settings.
You may also want to make sure their telling you that
everything is configured the same isn't a matter of they
weren't the same to start with but now they made the changes
and the it still doesn't work. And

Wed, 12 Jan 2005 22:10:36 -0700 Sue Hoegemeier


COPYRIGHT © 2004, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE
http://www.meetholland.com

advertisement:   complete list of microsoft newsgroup    |    uk based newsgroup    |