Sorry for not responding earlier. All the lower process ID's are processes created by the sql server its-self. The user processes start at 50 I think. So thats why you cant kill spid 7.

Other than that Im not exectly sure whats going on. Try looking in the current information/ locks area to see what locks are being applied. You might be able to see what two connections are blocking each other.

Eric



>Hi Eric,
>
>Thanks for responding as I am in a bit of a jam here. It appears that one SPID is blocking another, but unfortunately I don't know enough about SPID to diagnose the problem. I have EM online intermittently, and the SPID that appears to be blocking another is 7, but it won't let me KILL it. It also does not show up when I run sp_who. Not wure what that means. I am running DBCC OPENTRAN, but it is still running.
>
>Unfortunately, I was not able to run TRUNCATE TABLE as I was only deleting some of the records. Thanks again for your help. I am pulling my hair out :-).
>
>>You can use DBCC CHECKDB, but I'm not sure it will give you the info your looking for. Try running DBCC OPENTRAN to see if there are any open transactions. If so, I would probably try to kill the culprit connection, if that didnt work, I would bite the bullet, restart the server and do a restore.
>>
>>Just another tip, if you are deleting all the records in a table you can use TRUNCATE TABLE, this will toast all the records without logging the deletions.