March 21, 2013 at 1:57 am
Hi all,
Is there any fix other than sql service restaRT when there is
transaction stuck in killed/rollback state (after killing a blocked transaction) in sysprocesses?
i had this situation and once i unsucessfully tried moving the database to offline mode(courtesy:google) to end the transaction.
any help will be appreciated.
____________________________________________________________________
Going in one more round when you don't think you can - that's what makes all the difference in your life --Rocky Balboa
Believe you can and you're halfway there. --Theodore Roosevelt
March 26, 2013 at 11:26 pm
Guys anybody there?? i posted this question some days ago and waitinng for a single reply, could anyone throw ur suggestions???
Gail can you help me on dis?
____________________________________________________________________
Going in one more round when you don't think you can - that's what makes all the difference in your life --Rocky Balboa
Believe you can and you're halfway there. --Theodore Roosevelt
March 27, 2013 at 3:42 am
I wouldn't advise restarting SQL Server as you could end up with a corrupted database after the restart. Let SQL Server finish it's rollback naturally. It's a pain but it will be a lot less than what you'll suffer if you go for the quick dirty fix of a restart.
---------------------------------------------------------
It takes a minimal capacity for rational thought to see that the corporate 'free press' is a structurally irrational and biased, and extremely violent, system of elite propaganda.
David Edwards - Media lens[/url]
Society has varying and conflicting interests; what is called objectivity is the disguise of one of these interests - that of neutrality. But neutrality is a fiction in an unneutral world. There are victims, there are executioners, and there are bystanders... and the 'objectivity' of the bystander calls for inaction while other heads fall.
Howard Zinn
March 27, 2013 at 5:02 am
Abu Dina (3/27/2013)
I wouldn't advise restarting SQL Server as you could end up with a corrupted database after the restart.
Not possible.
You could end up with a database in recovery for a while, you can not end up with a corrupt database. You could end up with a database in the recovery_pending state if you delete the log file after stopping SQL.
Corrupt database means that something outside of SQL, typically the IO subsystem has mangled the data file and damaged the contents. If a restart results in the IO subsystem writing garbage into the files, then the problem is the IO subsystem, not the restart.
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 27, 2013 at 5:07 am
If it's a killed process that's rolling back and there's a non-zero rollback percent complete and time remaining, and there's progress on the rollback, wait. If you restart SQL the rollback will continue after teh restart with the database unavailable (Recovering state).
The only time you want to restart when something's rolling back is when you have something 'stuck', normal sign of that is that the rollback percent complete is 0%, the estimated time remaining is 0 and there is absolutely no work being done. Even then, be careful. The only one i restart without too much concern is a rolling back backup that's stuck.
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 27, 2013 at 6:04 am
Thanks for your reply Gail 🙂
____________________________________________________________________
Going in one more round when you don't think you can - that's what makes all the difference in your life --Rocky Balboa
Believe you can and you're halfway there. --Theodore Roosevelt
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply