|
visakh16
Very Important crosS Applying yaK Herder
India
48076 Posts |
 Posted - 03/06/2013 : 03:48:40
|
i think there was some large transaction happening when KILL statement was fired and its taking time to rollback it. unless it completes rollback and reaches stable state you can start any other processes
Also i dont know why you KILL other processes. What if there was some important process executing at that stage? It will have risk of bringing DB to unstable state if kill didnt happen properly.
A much better approach would be to check if any process if running and once its done then start with your job. In actual scenario you should have set schedule in such a way that minimum overlap happens while your critical jobs are executing.
------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/
|
 |
|
SQL job is blocked
