Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MichaelP
Jedi Yak
2489 Posts |
 Posted - 2002-04-30 : 15:16:05
|
| I've for a SPID that is locking an entire DB. I've tried KILL spid# and that put it in a killed/rollback state. It's still at 0% complete and will NOT go away.Thx for ANY help folks!Michael |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-04-30 : 15:37:39
|
| Yeah, sometimes you get an exceptionally nasty process that just can't be killed... If you have SQL Probe, you could try their "Strong KILL" option... Otherwise (or in case the "Strong Kill" still isn't enough to blow away the diehard spid) your only option is to stop/start the server. Here is a KB article (Q171224) that talks about why certain processes don't die easily: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q171224---------------Strong SQL Developer wanted in the Boston area. Please e-mail if interested. |
 |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2002-05-01 : 09:13:48
|
| Well here's what i discovered. I have a trigger that calls xp_cmdshell. The EXE that got called got hung up somehow. It never returned, so the trigger never "finished" and the db etc was locked.I used task manager to kill the EXE and everything cleared up!Anyway, thought I'd share that with everyone!Michael |
|
|
|
|
|
|
Kill a SPID that will not die