Post reply

SHRINKDATABASE killed but rollback appears to be stuck

  • August 13, 2013 at 11:52 pm

    #281166

    Hello...I've found several useful tips/tricks on this site over the years, and am hoping someone can help me with this one as well.

    A shrinkdatabase was executed and killed 8-10 hours later. The problem is that:

    select percent_complete, estimated_completion_time, cpu_time, total_elapsed_time, * from sys.dm_exec_requests

    suggest that there has been no progress in the last 2-3 hours, and the estimated_completion_time increases.

    How can I proceed?

    Thanks,

  • August 14, 2013 at 3:02 am

    #1641265

    should never be shrunk on a regular basis find out more here ....[/url]

  • August 14, 2013 at 5:03 am

    #1641304

    Is the process being blocked by other processes? What is that process waiting on?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • August 14, 2013 at 5:07 am

    #1641310

    Wait. Do not restart SQL (the roll back will just continue with the DB unavailable). Check what the shrink process 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

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

Viewing 4 posts - 1 through 3 (of 3 total)

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