SPIDs blocking itself
Running sp_who2 on our SQL Servers during peak time (where more data come in),
that the same spid is displayed multiple times and some of them blocking itself.
DISKIO and Lastbatch on all these will the same, while the CPUTime are different.
This is how the result of sp_who2 looks:
SPID Status BlkBy Command CPUTime DISKIO LastBatch
92 Sleeping . UPDATE 8109 70191 12/07 16:03
92 Sleeping 92 UPDATE 2828 70191 12/07 16:03
......
Why is it happening? Thanks for your help.
A background of what we do:
Data are loaded by processes (stored procedures) running every 15 minutes. Users will also be viewing and editing the data from GUI, at the same time.
Nothing to worry about... http://support.microsoft.com/default.aspx/kb/906344 -- Adam MachanicPro SQL Server 2005, available nowhttp://www..apress.com/book/bookDisplay.html?bID=457-- <Baskar Joshi@discussions.microsoft.com> wrote in message news:b74f081f-5969-432b-a18f-be59d3ff8755@discussions.microsoft.com... Running sp_who2 on our SQL Servers during peak time (where more data come in), that the same spid is displayed multiple times and some of them blocking itself.DISKIO and Lastbatch on all these will the same, while the CPUTime are different.This is how the result of sp_who2 looks:SPID Status BlkBy Command CPUTime DISKIO LastBatch92 Sleeping . UPDATE 8109 70191 12/07 16:0392 Sleeping 92 UPDATE 2828 70191 12/07 16:03......Why is it happening? Thanks for your help.A background of what we do:Data are loaded by processes (stored procedures) running every 15 minutes. Users will also be viewing and editing the data from GUI, at the same time.
Adam is correct. If you are using SQL Server 2000 SP4, the blocking you are seeing is a result of better reporting of such events, i.e. it has always been there. I am not sure about SQL Server 2005 as I just started working with it but my suspicion is that it is the same issue if you are seeing it in the sp_who2 results.
Michael
