Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Can't Kill SPID “Transaction Rollback in Progress” Expand / Collapse
Author
Message
Posted Sunday, March 3, 2013 2:16 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:03 AM
Points: 40,385, Visits: 36,829
Welsh Corgi (3/3/2013)
How do you check what the rollback session is waiting for?


Same way you check what any session is waiting for, sys.dm_exec_requests

If you believe that Kill with the statusOnly option is not working, file a bug report on Connect.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1426016
Posted Sunday, March 3, 2013 5:18 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, September 29, 2014 10:57 PM
Points: 4,242, Visits: 4,290
GilaMonster (3/3/2013)
[quote]Welsh Corgi (3/3/2013)
How do you check what the rollback session is waiting for?


GilaMonster
Same way you check what any session is waiting for, sys.dm_exec_requests

If you believe that Kill with the statusOnly option is not working, file a bug report on Connect.[/quote


I'm not going to ask you to open Google but do you have a favorite query to identify this?


For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1426047
Posted Monday, March 4, 2013 12:36 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 10:03 AM
Points: 40,385, Visits: 36,829
Welsh Corgi (3/3/2013)
GilaMonster (3/3/2013)
[quote]Welsh Corgi (3/3/2013)
How do you check what the rollback session is waiting for?


GilaMonster
Same way you check what any session is waiting for, sys.dm_exec_requests

If you believe that Kill with the statusOnly option is not working, file a bug report on Connect.[/quote


I'm not going to ask you to open Google but do you have a favorite query to identify this?


Query sys.dm_exec_requests, filter on the session_id that you killed, check the blocking_session_id and the wait-related columns.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1426100
Posted Wednesday, May 15, 2013 5:00 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 7:07 AM
Points: 2, Visits: 4
This is also my problem. I'm afraid to reboot the service cause some forums says that it might cause database to be suspect..

Do you really recommend to bounce the service? I have no backup and I can't backup because of this killed\rollback status
Post #1453010
Posted Wednesday, May 15, 2013 5:04 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 15, 2013 7:07 AM
Points: 2, Visits: 4
SPID 59: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 63447061 seconds.

the estimated time is increasing from time to time.. what should i do? will i wait for it? or restart the service?

i afraid that my database will be suspect.
Post #1453014
Posted Wednesday, May 15, 2013 5:43 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, November 14, 2014 10:40 PM
Points: 422, Visits: 2,661
Why don't you guys run dbcc inputbuffer (spid#)

It will show which tsql code is currently running.

SueTons.


Regards,
SQLisAwe5oMe.
Post #1453026
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse