|
Home > Archive > MS SQL Server > August 2005 > trying to kill a SPID
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
trying to kill a SPID
|
|
|
| I have a spid from a db maint plan that kicked off during the night to
backup some of our databases. For some reason the spid seems to have hung,
is not doing any work, and cannot be killed. The CPU time is 0, the Disk I/O
is zero, the memory usage is 2, and the lastwaittype (from sysprocesses) is
NETWORKIO. (We had some network issues during the night with some other jobs
running on other machines that may be related and/or victims also.) I tried
to Kill the SPID and now it's state is in KILL / ROLLBACK. It's not
consuming any CPU or I/O, but I cannot kill the spid.
KILL spid WITH STATUSONLY reports rollback 100% & remaining time 0, but the
spid remains active.
I have stopped & restarted the SQL Agent (shot in the dark since it started
the SPID) w/o success. Any ideas how I can kill the spid w/o having to stop
& restart the SQL Server Service?
Thanks
| |
| doller 2005-08-12, 1:23 pm |
| hi,
use kill spid number
Have u refreshed ur process window
if the the problem exists stop and start sql services
hope it help u
from
killer
cw wrote:
> I have a spid from a db maint plan that kicked off during the night to
> backup some of our databases. For some reason the spid seems to have hung,
> is not doing any work, and cannot be killed. The CPU time is 0, the Disk I/O
> is zero, the memory usage is 2, and the lastwaittype (from sysprocesses) is
> NETWORKIO. (We had some network issues during the night with some other jobs
> running on other machines that may be related and/or victims also.) I tried
> to Kill the SPID and now it's state is in KILL / ROLLBACK. It's not
> consuming any CPU or I/O, but I cannot kill the spid.
> KILL spid WITH STATUSONLY reports rollback 100% & remaining time 0, but the
> spid remains active.
>
> I have stopped & restarted the SQL Agent (shot in the dark since it started
> the SPID) w/o success. Any ideas how I can kill the spid w/o having to stop
> & restart the SQL Server Service?
>
> Thanks
|
|
|
|
|