Kill will not 'kill'

Kill will not 'kill'

Post by j » Fri, 17 Aug 2001 02:04:42


I have a process that will not be killed in SQL65. It is blocking another
process and I do not want to re-start teh service.

Any suggestions??

Thank You



Kill will not 'kill'

Post by Erland Sommarsko » Fri, 17 Aug 2001 07:02:10

> I have a process that will not be killed in SQL65. It is blocking another
> process and I do not want to re-start teh service.

I'm afraid that you are caught between the devil and the deep blue sea.
The process may have very good excuses for refusing to be killed. It
may for instance may be engaged in a longer rollback exercise, and
believe me you want that rollback to complete, because you would have
a mess of a database.

If you restart the server in this situation, the query still need to
be rolled back when SQL Server starts, but this is done in recovery
mode, when no one is allowed to the database and is considerably
faster. Still, if there is a lot to recover, the recovery may take
some time as well.

Erland Sommarskog, Abaris AB

SQL Server MVP


Kill will not 'kill'

Post by Suzanne Jackows » Fri, 17 Aug 2001 10:18:49


In this case, the process is probably rolling back, and hopefully has
finished by the time I write this.  If is is rolling back (and you may be
able to tell by looking at the SPID in sp_who2 output as well as observing
system I/O and processor usage), the best course is usually to wait.

Note that stopping the service during a rollback is a common mistake - it
cannot save you from a lenghty rollback, but instead puts you in the worse
position of waiting until it rolls forward and then rolls back all over

The only ways to get out of waiting for the rollback altogether involve
either restoring from backup or risking serious corruption and data loss,
and all are tedious procedures that tend to take a lot longer than just
waiting for the rollback to complete.

So sit tight and good luck!

Microsoft SQL Server Support


1. When Kill Doesn't Kill

I attempted a multiple update that caused an endless process  because I had
failed to deal with multiple updates in my trigger.  I tried to cancel the
process first through Enterprise Manager and then through ISQL but could
not get it to cancel.  If I had waited long enough my logs would have
filled up and the process would have aborted, but instead I stopped SQL
Service on my workstation (I am at a test bench).  When I returned to
Enterprise Manager my database had a 'Restoring' beside it.  It never
restored itself, however, and so I dropped it and created a new database
with a backup I had.

How do you kill a process that does not want to die?

Thanks for any information.
Donna S.

2. au_lname

3. I can't kill user session when I want to kill..!!!1

4. running *.sql files from a dos prompt

5. why not 'KILL @aux'?

6. Latest Study Guides for Oracle 8i 9i OCP OCA exam

7. ORA-1034 (Oracle not Available) It's killing me

8. An example of Instead of update trigger on a view

9. can't kill process

10. Can't kill DBCC Checktable

11. Open current Error log and it hangs user - and can't kill Process

12. Can't kill process in SQL 7.0

13. How to kill PID's?