Post reply

HELP - need to kill big transaction that''s taking too long to rollback

  • September 28, 2006 at 10:23 am

    #62204

    Hi all,

    I have a big transaction running on a table that I had to kill and rollback.  Unfortunately, the transaction has been rolling back for 1.5 hours and is supposedly only 6% done rolling back.  I need to stop this transaction, and I'm looking for the fastest way to do it with doing the least amount of damage. 

    Is there any nuke button that I can press to kill this process with extreme prejudice? - at this point I don't care about the integrity of the table I was running the transaction on - I just want it to die.

    Is there any way to force the table to drop, thus killing the process? 

    Is there any way to make a new log file for this database, and kill the log file that has the rolling back?

    If I stop SQL Server, will it try to wait until the transaction is done/rolledback before it will actually stop?

    Please HELP!  Thanks in advance

    -Rob

  • September 28, 2006 at 11:31 am

    #663095

    When you get into a rollback situation, there is nothing to do but wait, unless the process that is rolling back is being blocked.

    Stopping SQL Server is *NOT* going to help

    If you deatach the database and attach it without the Transaction log you may lose data. Not sure you want to do that

    My advice:

    Try to see if the process is not being blocked. If it is not ensure you have enough resources, disk space, memory etc. If it is blocked "remove" the blocker.

    Good Luck


    * Noel

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply