March 16, 2010 at 4:24 am
HI,
I have come in this morning and looking at a SQL server 2000 database spotted that things were barely running.
I decided that possibly stopping all jobs and restarting the service may be the solution (as this has worked before). I have done so and they disappeared from job activity monitor and tried to give the instance a restart.
However I get a message from windows that it is unable to stop the service. I can still log onto SQL as administrator and when i look at processes I can see many are KILLED / ROLLEDBACK.
However ALL of them are like:
SPID 87: transaction rollback in progress. Estimated rollback completion: 100%. Estimated time remaining: 0 seconds.
I am concerned that SQL is stuck on something. I'm assuming that restarting the server would be a bad solution, so can anyone help?
Cheers,
Sam
March 16, 2010 at 5:09 am
Had to resort to server reboot in the end. SQL came back up with no issues. This was a weird one for me. If anyone can explain this one I'm all ears. Did check task manager and spotted that no processes were running on SQL account.
March 16, 2010 at 9:41 am
Hard to tell there. I think it's entirely possible that some code just flaked, or something hung and a reboot fixed it. Typically if you didn't have a large transaction in process, the restart should be quick. Especially once you get to 100% in the rollback.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply