March 3, 2013 at 11:40 am
How can you check the progress of a rollback?
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/
March 3, 2013 at 1:08 pm
You gave the command in your first post. KILL <spid> WITH StatusOnly
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 3, 2013 at 1:50 pm
GilaMonster (3/3/2013)
You gave the command in your first post. KILL <spid> WITH StatusOnly
Well that does not work. I get 0% of 0%.
Thank you.
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/
March 3, 2013 at 1:53 pm
It does work, it's the correct and only way to get the rollback status and progress.
Check what the rolling back session is waiting for.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 3, 2013 at 2:02 pm
GilaMonster (3/3/2013)
It does work, it's the correct and only way to get the rollback status and progress.Check what the rolling back session is waiting for.
My experience is that it does not always work.
I have seen many threads in which this is a problem and does not work as it should.
How do you check what the rollback session is waiting for?
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/
March 3, 2013 at 2:16 pm
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 3, 2013 at 5:18 pm
GilaMonster (3/3/2013)
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/
March 4, 2013 at 12:36 am
Welsh Corgi (3/3/2013)
GilaMonster (3/3/2013)
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 15, 2013 at 5:00 am
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
May 15, 2013 at 5:04 am
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.
May 15, 2013 at 5:43 am
Why don't you guys run dbcc inputbuffer (spid#)
It will show which tsql code is currently running.
SueTons.
Regards,
SQLisAwe5oMe.
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply