Sunday, March 11, 2012

blocking processes on scheduler

About once or twice a week, our SQL server stops responding. When this happens, we are not able to connect to it via EM or QA. The only solution at this point is to restart the SQL Service. The SQL errorlog always shows the following type of error after t
his happens:
Process ID 72:167 owns resources that are blocking processes on Scheduler 3.
I am finding it hard to troubleshoot this because there is essentially no way to find out what process is causing the blocking. I know what the SPID causing the blocking was, but due to the restart of SQLService, I don't know what it was actually doing.
Can anyone shed more light on this problem? The only potential solution I can think of is to run a trace and capture all the events before the block occurs so that we can identify the cause of the blocking...
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:A008E96F-84B5-4D89-935A-C6B0C6C7A113@.microsoft.com...
> About once or twice a week, our SQL server stops responding. When this
happens, we are not able to connect to it via EM or QA. The only solution at
this point is to restart the SQL Service. The SQL errorlog always shows the
following type of error after this happens:
> Process ID 72:167 owns resources that are blocking processes on Scheduler
3.
> I am finding it hard to troubleshoot this because there is essentially no
way to find out what process is causing the blocking. I know what the SPID
causing the blocking was, but due to the restart of SQLService, I don't know
what it was actually doing.
> Can anyone shed more light on this problem? The only potential solution I
can think of is to run a trace and capture all the events before the block
occurs so that we can identify the cause of the blocking...
>
I would suggest that you turn on the SQL Server Profiler and let it capture
the database activity. By doing so, you should be able to see what was
happening in the server when it finally locks up. That should give you
some direction to start in.
Rick Sawtell
MCT, MCSD, MCDBA

No comments:

Post a Comment