December 15, 2008 at 11:05 am
We have a process that we can see running with Profiler, but user activity only reports a SLEEPING status. Why wouldn't it indicate either runnable or suspended? At first I told the user their process wasn't running because I was only checking activity monitor. I then decided to query sysprocesses directly and refresh the results at least once a second, but I only saw SLEEPING. However, running Profiler I can see a lot of activity, possibly looping. Why would it report SLEEPING?
Thanks, Dave
December 15, 2008 at 12:04 pm
It means the process itself still has work to do, but it's waiting on something. BOL refers to blocking as a possible cause.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 15, 2008 at 2:58 pm
I checked for blocking and there was none. I also saw 0 for the waittime so there was no waiting. Besides, I can see the same command executing over and over again so the status should at least be RUNNABLE while the command is executing. Shouldn't it?
For what it's worth here is the command.
FETCH API_CURSOR000000000000B7CA
Thanks, Dave
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply