Can't kill a process

[TheDrider]

I have a process that is hung and doesn't want to die. I've tried to kill it, I've tried to bounce the service, and then I rebooted the machine. The only change was that the rogue process is now spid 51 instead of its original 53.

The spid does appear to have a lock on masterdb and tempdb. The process info says it has 2 open transactions, it's app is MS SQLEM, and it says it's not Blocked By or Blocking anything else.

How can I really kill this process?

 

[ptheriault]

What's the status of the spid? is it rolling back?

What do you get for a message when you kill it?

What is the host machine for the spid?

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[TheDrider]

The status is "runnable" and it's current command SELECT INTO. This is on my local machine.

I don't get any error messages at all, either through the Enterprise Manager or from Query Analyzer. It just doesn't die.

Why would the process persist even after a hard reboot?

Thanks for any info you can provide on this.

 

[ptheriault]

When you run sp_who2 or sp_who your spid will show up as running and the command will be "select into". You don't have a roug spid. The fact that you have a different spid from after the reboot tells me that. You will always see your own process. also spids > 50 are user and spids< 50 are system so don't try to kill them.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[TheDrider]

Please excuse my earlier retardation. My other laptop was maintaining a second connection to this database. I was my own worst enemy...