SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


KILLED/ROLLBACK STATE - SERVICE RESTART


KILLED/ROLLBACK STATE - SERVICE RESTART

Author
Message
Vinodh247
Vinodh247
Old Hand
Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)

Group: General Forum Members
Points: 342 Visits: 758
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
Vinodh247
Vinodh247
Old Hand
Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)

Group: General Forum Members
Points: 342 Visits: 758
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
Abu Dina
Abu Dina
SSCrazy
SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)SSCrazy (3K reputation)

Group: General Forum Members
Points: 2981 Visits: 3325
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

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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)

Group: General Forum Members
Points: 224486 Visits: 46317
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

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


GilaMonster
GilaMonster
SSC Guru
SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)SSC Guru (224K reputation)

Group: General Forum Members
Points: 224486 Visits: 46317
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

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


Vinodh247
Vinodh247
Old Hand
Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)Old Hand (342 reputation)

Group: General Forum Members
Points: 342 Visits: 758
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search