SQL blocked process query.

techstep

I know it seems like childs play. But, for some its all new to them.  Your database is slowing down. You have processes blocked all over the place. Your world is crumbling.

You get up and just walk out.  You are done. Its over.

OR you just fire up SQL Management Studio (2005+), connect to your database and start a new query. You then just type:

sp_who2

and hit “Execute”. (Though, I am told use should even system known stored procedures should be executed with EXEC preceding the stored procedure.)

EXEC sp_who2

What does this do?

Results of sp_who2
I stole this from someone else. Sorry.

Now, you really do not want to even bother looking at the first 50 SPIDs (System Process IDs). They are system events and generally do not effect slowdowns. The user processes start after SPID 50. \

On a side note. You can look at specific SPIDs with:

EXEC sp_who2 97

Now, you will notice a column there called “BlkBy” this is the “Blocked By” column and that is what we are looking for. So, you would scroll through the list of SPIDs till you find one that is blocked by another SPID. Then you scroll around till you find that process. It may be blocked to. If it is you continue down the rabbit hole till you get to the last one that ISN’T blocked by another process. THAT one is your blocker! Gotcha!