Very Computer

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.

You can't really kill a SQL Server process; you can only ask it to commit
suicide.  Under certain conditions,  a query cannot be killed because it
doesn't check to see if it has been asked to kill itself.

The database should have recovered itself following the restart.  However,
this may take a while if a lot of data needed to be backed out.

Hope this helps.