Hi all,
I have a stored-procedure running on an SQL2k5 box which is updating a table on a SQL2k linked server.
I have ensured that the "Collation Comaptible" optiions are set True at both ends of the link, but still my query seems to perform a full table scan (some 2million+ rows) for a single update.
The where clause is matching a single value of the primary key ( an integer identity column) and updating a single row in the table.
collation of the remote DB (on the sql2k box) is SQL_Latin1_General_CP1_CI_AS
collation of the local DB (where the Sp runs from ) is SQL_Latin1_General_CP1_CI_AS
can anyone suggest how to prevent the full table scan? this is taking anything from 45 minutes to 1.5 hours to run,
many thanks in advance