June 15, 2011 at 8:18 am
Hello!
This is impossible to answer for our specific problem, I know. But does anyone know what I should look for on our server to determine the cause on our server?
Case description:
A web service has more than 10000 id's to run through a stored procedure on the SQL Server. It divides this into 10 buckets and send 10 requests to the server with 1000 id's each. The processing starts OK with 3 threads finishing after a reasonable time. Then 6 threads stop processing and the 7th run to completion. Then the next thread picks up again and runs to completion, and so on.
I would like to see why SQL Server determines it is best to suddenly suspend 7 threads. My current idea is to query for the execution plan of each batch and look for changes and look at some performance counters at the same time. Hopefully I see something changes at the time the parallell execution stops and enter single threaded execution.
Does anyone have a better idea of what to look for?
Best regards,
Vemund Haga
June 15, 2011 at 8:46 am
Can you please post the actual execution plan?
If you want to capture all the details including the performance counters then use SQLDiag with perfstats script. A little bit of googling will give you all the details.
July 5, 2011 at 6:05 pm
where do you download sqldiag and perfstats from?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply