May 16, 2003 at 4:22 pm
I ran into a problem today where an orphanded spid was creating a blocking issue with several spids being blocked in a cascading effect.
I wasn't able to "kill" this spid. When I ran the command, it didn't go away.
I had to reboot the server to remedy the situation. Anyone know what could have been happening?
Ep
May 16, 2003 at 5:16 pm
When you go to kill a SPID, SQL Server has to rollback all the transactions that were in progress at the time. This may take some time. That's one possibility.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
May 19, 2003 at 9:17 am
NExt time you kill the spid , run kill [spid] with statusonly, and that will show you the rollback process. If it shows that is has reached 100% and that there is no remaining time, and the spid is still active, then you won0t be able to kill, and you will have to reboot the server.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply