|
Hi, I've a query like so If I run this, I get multiple calls to exec sp_execute 100618, XXX If I change the query to The multiple calls are removed and replaced with a single, simple SELECT X FROM DB.DBO.LinkedServerTable FOR BROWSE I would like to know if this is a 'good' way to avoid the linked server sp__execute issue as this table may have millions of records in it soon. the local table also has millions. If the answer is to copy the remote table across I'm happy with that. Still would like an explanation of why FOR BROWSE helps though. I have tried it without the FOR BROWSE and it still executes one sp_execute per remote row help appreciated.
(comments are locked)
|
|
scrub that. The OPENQUERY was all that is required. The profile I was looking at was picking up the sp_execute from the very job I wanted to fix. FOR BROWSE doesn't matter.,
(comments are locked)
|

