August 2, 2007 at 9:03 am
Hi,
We have a scheduled job that basically runs a procedure. This procedure has a cursor that goes through about 170 tables in the dabase and updates the credit card numer value to 1111111111 for these columns.
When I tested the procedure, it took about 3 minutes to run in query analyzer.
After scheduling the procedure , I see this weird pattern. The job runs for few minutes, go in the 'suspended' status for say 1-2 hours, wakes up and updates few tables, again goes in 'suspended' status. Ultimately, it finishes in almost 5 hours.
This server is like a backup server and barely used. So, I am not sure if I have to worry about I/O contention. But I would still like to figure out what's going on with this process and how can I fix it? Do you think changing the workerthread config will help ( incraesing from 255 to 512)?
Thanks,
N
August 2, 2007 at 12:08 pm
run profiler to capture before running the proc and review the trace file, that should give you more details whats happening.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply