Post reply

Spid value showing -3 unable to kill

  • March 13, 2012 at 2:44 am

    #265755

    I'm having a problem after restarting my sql server instance.

    I've discovered through sp_who that the tempdb appears to be blocked from starting due to a -3 spid, I checked the master..syslockinfo table and the Uow value is '00000000-0000-0000-0000-000000000000' I've attempted to kill of this transaction but to no avail

    Any suggestions people

  • March 13, 2012 at 2:53 am

    #1458334

    A SPID -3 is realted to a rollback and should resolve after a while automatically.

    See also http://social.msdn.microsoft.com/Forums/eu/sqldatabaseengine/thread/e1fe4044-1c25-4c6d-9aa5-7828ec4e2451

    [font="Verdana"]Markus Bohse[/font]

  • March 13, 2012 at 3:00 am

    #1458342

    check the error log to see which database is being recovered and then run DBCC CHECKDB across all your databases to check for corruption

    the error log should give a percentage of the restoration process

  • March 13, 2012 at 5:53 am

    #1458403

    Thanks had to eventually stop the sql server service, remove the data files for the database which was struggling with recovery and then restored the database from a backup.

    All is fine now, thanks for you help:-)

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

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