May 3, 2002 at 12:39 pm
We have a SQL 2000 server running a T-SQL job that does some local file processing and record updates. Then the job updates a table on a linked server. Up until recently, the linked server was running SQL7.0. Then they upgraded to SQL2000. Now when I do an updated on the linked server, the records are actually updated, but I get a result of 0 records updated. Unfortunately this is part of my error checking procedure; to check how many records were updated.
I have found the NOCOUNT flag user option and we are having that checked out, but I was wondering if there are any other reasons why this is happening
May 3, 2002 at 1:08 pm
Nothing that sticks out in my miond off hand. Could be one of the other settings of the server or something else in your code that changed the way it worked with 7. If you post we can look at it but don't know that would help. I suggest two things. 1 make an update that would happen by hand and see if rows return. 2 use profiler to watch the job and see what steps 2000 is taking when doing this (like I said could be some server setting having the affect).
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply