I have a job that usually runs for about 2 hours. This morning it was still running at 5 hours and I decided to kill it. It has been in a "KILLED/ROLLBACK" status for quite a while now. When I run the KILL command again to get the status of the rollback, I get the following:
SPID 84: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds.
Is there anyway I can boost priority or tell SQL Server to "hurry up"? :)
Or is there a way for me to say "I don't care about the state of the table. Just quit."