Re: Linked server execution plans
From: Narayana Vyas Kondreddi (answer_me_at_hotmail.com)
Date: 08/26/04
- Next message: John Scott: "Replres.dll"
- Previous message: bing: "Re: connection problem"
- In reply to: Charles J Ryan: "Linked server execution plans"
- Next in thread: Charles J Ryan: "Re: Linked server execution plans"
- Reply: Charles J Ryan: "Re: Linked server execution plans"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 22:20:47 +0100
Having a stored procedure on the linked server, and calling it using 4-part
name acceptable in this case?
-- Vyas, MVP (SQL Server) http://vyaskn.tripod.com/ "Charles J Ryan" <charlesryan1@msn.com> wrote in message news:eNb9Bz6iEHA.3612@TK2MSFTNGP12.phx.gbl... > I have created a linked server to a non sql server database using the OLEDB > for ODBC provider. > > When I issue a simple query such as: > > select * from linked_server..schema.table_name where field1 = '111111' > > It takes the same amount of time as: > > select * from linked_server..schema.table_name > > Looking at the execution plan the reason for this becomes obvious. The plan > always uses a table scan passing only the select portion of the query, and > then applies a filter with the where clause once ALL records have been > retrieved from the linked server. > > Is there any way to override the execution plan and force it to pass through > the entire select statement, including the where clause, for the remote > server to process without using OPENQUERY? > >
- Next message: John Scott: "Replres.dll"
- Previous message: bing: "Re: connection problem"
- In reply to: Charles J Ryan: "Linked server execution plans"
- Next in thread: Charles J Ryan: "Re: Linked server execution plans"
- Reply: Charles J Ryan: "Re: Linked server execution plans"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|