I had a process that I had to kill. The process had ran over night and didn't seem to be progressing. I used the KILL <<SPID>> to end the process. I know and expected the spid to then enter a KILLED\ROLLBACK status. However when I check the state of the rollback with KILL <<SPID>> WITH STATUSONLY. the roll back shows 0% complete with 27605 seconds remaining. I have checked the status a number of times and no progress is visible in the rollback. The spid was killed approx 9 hours ago.
Details on the process are.
A number of select statements populating or updating 2 #temp tables then writing the result to a physical table. The spid was killed prior to any data being input into the final table. I have people requesting the server be rebooted but I have explained this will more than likely place the DB in suspect mode and the recovery could take longer than the roll back. I figured the proccess could take as long as 16 hours to rollack but with it still at 0% I am at a loss.
Any ideas?
Shoot Me! Shoot Me NOW!!!
- Daffy Duck
Details on the process are.
A number of select statements populating or updating 2 #temp tables then writing the result to a physical table. The spid was killed prior to any data being input into the final table. I have people requesting the server be rebooted but I have explained this will more than likely place the DB in suspect mode and the recovery could take longer than the roll back. I figured the proccess could take as long as 16 hours to rollack but with it still at 0% I am at a loss.
Any ideas?
Shoot Me! Shoot Me NOW!!!
- Daffy Duck