March 13, 2009 at 7:45 am
I responded to an incident yesterday where users were reporting a lock up. When I ran sp_who2 I could see that a spid was blocking everything. The computer that was running the application that launched the spid was turned off. So I'm trying to figure out why that process was still there. Has anyone seen this behavior before? I saw this in the error log.
Process 0:0 (25a4) UMS Context 0x152F04B8 appears to be non-yielding on Scheduler 0.
March 13, 2009 at 4:37 pm
I have seen this before and my theory is that SQL is awaiting a response from the client but is unaware that the client connection was dropped (network issue in my case). I killed the SPID and it rolledback to 100% but wouldn't go away most likely because it was still trying to notify the client the SPID was killed. The only way I could clear it was to restart SQL services.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply