OldSkoolSkater
MIS
Hello
Running SQL7 sp3.
I am an admin of an inherited SQL server and have a question about process IDs.
I noticed that a scheduled job that truncates a table(through Enterprise Manager\Jobs) was taking far longer to complete than normal - hours rather than minutes, and when I looked into the problem I found that there were two SPIDs that were blocking/blocked against the database object.
One SPID was blocking on the table in question, and the other SPID was blocked by that SPID.
I tried to kill the blocking SPID through EM but it was a persistent little beggar and would not be killed off.
The only way I managed to kill it was to restart the SQLserver service (drastic, I know!)
The scheduled job then ran as it should.
Is there a better way of getting rid of blocking SPIDs, as this is an occasional problem that happens when you least want it to??
Cheers
Steve - Network Coordinating in the UK
Running SQL7 sp3.
I am an admin of an inherited SQL server and have a question about process IDs.
I noticed that a scheduled job that truncates a table(through Enterprise Manager\Jobs) was taking far longer to complete than normal - hours rather than minutes, and when I looked into the problem I found that there were two SPIDs that were blocking/blocked against the database object.
One SPID was blocking on the table in question, and the other SPID was blocked by that SPID.
I tried to kill the blocking SPID through EM but it was a persistent little beggar and would not be killed off.
The only way I managed to kill it was to restart the SQLserver service (drastic, I know!)
The scheduled job then ran as it should.
Is there a better way of getting rid of blocking SPIDs, as this is an occasional problem that happens when you least want it to??
Cheers
Steve - Network Coordinating in the UK