April 9, 2002 at 6:14 am
Hi all,
We have a view, which spans data in 2 databases. This was viewed in EM but unfortunately, EM crashed. We were therefore left with locks on a few tables in 2 databases.
The Kill process didn't appear to do anything when run from my machine, query analyser or the server itself.
There were no other locks or blocks that I could see?
Any idea's why the kill statement would appear to have done nothing?
Thanks,
Clive
Clive Strong
April 9, 2002 at 6:55 am
I get the sometimes and have to shut down the server to correct.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
April 9, 2002 at 10:25 am
Might be slow to rollback, but I agree with Antares, a reboot might be necessary.
Are there any blocks showing? Can you trace back the blocks and kill the root process?
Steve Jones
April 9, 2002 at 10:30 am
Hi Antares & Steve,
In the end, I did reboot the server. There was a block initially from a job that was running, but once I stopped the job, the blocks disapeared, but the process that had all the locks remained and would still not go!
Server is fine....was just curious as to why when I wanted to kill the process nothing happened..!
Thanks for your reply's!
Clive
Clive Strong
June 11, 2002 at 3:14 pm
This might be usefull reading material:
INF: Understanding How the Transact-SQL KILL Command Works (Q171224)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q171224
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply