rollback | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive


I have a process a user killed and it leaves "KILLEDROLLBACK" in the cmd column after an sp_who. When I use KILL &lt<img src=’/community/emoticons/emotion-4.gif’ alt=’;p’ />rocess_id&gt; WITH STATUSONLY It tells me its 100% rolled back.<br /><br />What should I do with this process as it appears to be orphaned ?<br />Should I be running the cmd KILL &lt<img src=’/community/emoticons/emotion-4.gif’ alt=’;p’ />rocess_id&gt; WITH STATUSONLY on aan already killed process to check it’s status ?<br /><br />Thanks all
If 100% is rolled back, I suppose you can kill without statusonly.
Because I never pass for a similar case, I suggest to wait for others opinions.
Luis Martin …Thus mathematics may be defined as the subject in which we never know what we are talking about, nor whether what we are saying is true.
Bertrand Russell
I have seen that couple of times in my database..looks like bug..what i did is restart sql server and it will go away otherwise it will there for ever. -Nilay
The same status report can be obtained by executing twice the KILL spid|UOW command without the WITH STATUSONLY option; however, this is not recommended. The second execution of the command may terminate a new process that may have been assigned to the released SPID. KILL to terminate an orphan distributed transaction.
Terminate an orphan (SPID = -2) transaction with UOW _________
Satya SKJ