Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
 Posted - 2009-05-11 : 12:44:16
|
I have a SQL server 2000 that is linked to a remote database server using an ODBC driver. The link works fine (which was a suprise  )I want to expose some of the data from the linked server, so I have setup a database on the SQL server to do this. What I would like is some advice on the optimum approach for writing queries. I currently have setup some views that are simply a select * from the underlying linked database. I did this so that queries can be written without me needing to get involved (this isn't a production server). Is there much of a performance hit (if any) doing it this way? Is it likely there would be much improvement through not using the Views but using the linked tables directly in the queries. Would I be much better off using stored procedures (these queries aren't likely to be used frequently and so would probably not stay cached long enough for a great benefit. How much does it depend on the ODBC driver or the remote serverDoes the processing all happen on the remote server (as the execution plans seem to suggest. thanks in advancesteve-----------ASCII and ye shall receive. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-05-11 : 22:45:21
|
| Yes, No matter what you choose ,Linked server can't take advantage of index or index hints. It goes through WHOLE REMOTE SCAN in Execution plan. |
 |
|
|
elwoos
Master Smack Fu Yak Hacker
2052 Posts |
Posted - 2009-05-13 : 04:53:49
|
| That confirms my suspicions, thankssteve-----------ASCII and ye shall receive. |
|
|
|
|
|
|
Remote control