How to KILL a Suspended Sys Process?

I have a suspended process that sits in running processes returned by SP_WHO
for 3 days already.
SPID:10
Status: SUSPENDED
Login Name: sa
DB NAME: master
Command:CHECKPOINT
CPU Time: 2625937
DiskIO: 358622
An attempt to "kill 10 " failed saying that only user processes can be
killed.
Rebooting is not an option since it is a production server.
Is there anything else i can do to kill this process without re-starting the
server?
The job does not affect the performance of the server, but all attempts to
updatestats and backup database fail, and i am 100% sure that this is
because of this process.
Any help please.
Thank you.
low numbered spids are SYSTEM processes. You cannot (for obvious reasons)
KILL them.
What is it that makes you 100% think checkpoint thread is the root of your
problems?
Have you checked the sql error log for messages related to checkpointing?
TheSQLGuru
President
Indicium Resources, Inc.
"Michael Kansky" <mike@.zazasoftware.com> wrote in message
news:u$zA7RFgHHA.284@.TK2MSFTNGP05.phx.gbl...
>I have a suspended process that sits in running processes returned by
>SP_WHO for 3 days already.
> SPID:10
> Status: SUSPENDED
> Login Name: sa
> DB NAME: master
> Command:CHECKPOINT
> CPU Time: 2625937
> DiskIO: 358622
> An attempt to "kill 10 " failed saying that only user processes can be
> killed.
> Rebooting is not an option since it is a production server.
> Is there anything else i can do to kill this process without re-starting
> the server?
> The job does not affect the performance of the server, but all attempts to
> updatestats and backup database fail, and i am 100% sure that this is
> because of this process.
> Any help please.
> Thank you.
>
|||On Apr 16, 2:24 pm, "Michael Kansky" <m...@.zazasoftware.com> wrote:
> I have a suspended process that sits in running processes returned by SP_WHO
> for 3 days already.
> SPID:10
> Status: SUSPENDED
> Login Name: sa
> DB NAME: master
> Command:CHECKPOINT
> CPU Time: 2625937
> DiskIO: 358622
> An attempt to "kill 10 " failed saying that only user processes can be
> killed.
> Rebooting is not an option since it is a production server.
> Is there anything else i can do to kill this process without re-starting the
> server?
> The job does not affect the performance of the server, but all attempts to
> updatestats and backup database fail, and i am 100% sure that this is
> because of this process.
> Any help please.
> Thank you.
the spids between 0 and 50 are system processes not user processes. If
you don't know what is going on, you can always find a down time and
stop/start the MSSQL service. This will kill and restart all system
processes.
Kristina

How to KILL a Suspended Sys Process?

I have a suspended process that sits in running processes returned by SP_WHO
for 3 days already.
SPID:10
Status: SUSPENDED
Login Name: sa
DB NAME: master
Command:CHECKPOINT
CPU Time: 2625937
DiskIO: 358622
An attempt to "kill 10 " failed saying that only user processes can be
killed.
Rebooting is not an option since it is a production server.
Is there anything else i can do to kill this process without re-starting the
server?
The job does not affect the performance of the server, but all attempts to
updatestats and backup database fail, and i am 100% sure that this is
because of this process.
Any help please.
Thank you.low numbered spids are SYSTEM processes. You cannot (for obvious reasons)
KILL them.
What is it that makes you 100% think checkpoint thread is the root of your
problems?
Have you checked the sql error log for messages related to checkpointing?
TheSQLGuru
President
Indicium Resources, Inc.
"Michael Kansky" <mike@.zazasoftware.com> wrote in message
news:u$zA7RFgHHA.284@.TK2MSFTNGP05.phx.gbl...
>I have a suspended process that sits in running processes returned by
>SP_WHO for 3 days already.
> SPID:10
> Status: SUSPENDED
> Login Name: sa
> DB NAME: master
> Command:CHECKPOINT
> CPU Time: 2625937
> DiskIO: 358622
> An attempt to "kill 10 " failed saying that only user processes can be
> killed.
> Rebooting is not an option since it is a production server.
> Is there anything else i can do to kill this process without re-starting
> the server?
> The job does not affect the performance of the server, but all attempts to
> updatestats and backup database fail, and i am 100% sure that this is
> because of this process.
> Any help please.
> Thank you.
>|||On Apr 16, 2:24 pm, "Michael Kansky" <m...@.zazasoftware.com> wrote:
> I have a suspended process that sits in running processes returned by SP_W
HO
> for 3 days already.
> SPID:10
> Status: SUSPENDED
> Login Name: sa
> DB NAME: master
> Command:CHECKPOINT
> CPU Time: 2625937
> DiskIO: 358622
> An attempt to "kill 10 " failed saying that only user processes can be
> killed.
> Rebooting is not an option since it is a production server.
> Is there anything else i can do to kill this process without re-starting t
he
> server?
> The job does not affect the performance of the server, but all attempts to
> updatestats and backup database fail, and i am 100% sure that this is
> because of this process.
> Any help please.
> Thank you.
the spids between 0 and 50 are system processes not user processes. If
you don't know what is going on, you can always find a down time and
stop/start the MSSQL service. This will kill and restart all system
processes.
Kristina

How to KILL a Suspended Sys Process?

I have a suspended process that sits in running processes returned by SP_WHO
for 3 days already.
SPID:10
Status: SUSPENDED
Login Name: sa
DB NAME: master
Command:CHECKPOINT
CPU Time: 2625937
DiskIO: 358622
An attempt to "kill 10 " failed saying that only user processes can be
killed.
Rebooting is not an option since it is a production server.
Is there anything else i can do to kill this process without re-starting the
server?
The job does not affect the performance of the server, but all attempts to
updatestats and backup database fail, and i am 100% sure that this is
because of this process.
Any help please.
Thank you.low numbered spids are SYSTEM processes. You cannot (for obvious reasons)
KILL them.
What is it that makes you 100% think checkpoint thread is the root of your
problems?
Have you checked the sql error log for messages related to checkpointing?
--
TheSQLGuru
President
Indicium Resources, Inc.
"Michael Kansky" <mike@.zazasoftware.com> wrote in message
news:u$zA7RFgHHA.284@.TK2MSFTNGP05.phx.gbl...
>I have a suspended process that sits in running processes returned by
>SP_WHO for 3 days already.
> SPID:10
> Status: SUSPENDED
> Login Name: sa
> DB NAME: master
> Command:CHECKPOINT
> CPU Time: 2625937
> DiskIO: 358622
> An attempt to "kill 10 " failed saying that only user processes can be
> killed.
> Rebooting is not an option since it is a production server.
> Is there anything else i can do to kill this process without re-starting
> the server?
> The job does not affect the performance of the server, but all attempts to
> updatestats and backup database fail, and i am 100% sure that this is
> because of this process.
> Any help please.
> Thank you.
>|||On Apr 16, 2:24 pm, "Michael Kansky" <m...@.zazasoftware.com> wrote:
> I have a suspended process that sits in running processes returned by SP_WHO
> for 3 days already.
> SPID:10
> Status: SUSPENDED
> Login Name: sa
> DB NAME: master
> Command:CHECKPOINT
> CPU Time: 2625937
> DiskIO: 358622
> An attempt to "kill 10 " failed saying that only user processes can be
> killed.
> Rebooting is not an option since it is a production server.
> Is there anything else i can do to kill this process without re-starting the
> server?
> The job does not affect the performance of the server, but all attempts to
> updatestats and backup database fail, and i am 100% sure that this is
> because of this process.
> Any help please.
> Thank you.
the spids between 0 and 50 are system processes not user processes. If
you don't know what is going on, you can always find a down time and
stop/start the MSSQL service. This will kill and restart all system
processes.
Kristina

How to kill a process....

Hi there.
I've got a number of processes that are stuck on my server and are locking
up a table or two and I'd like to kill them. Unfortunately, after trying to
"Kill process" in SQL ENterprise manager, the processes involved are still
there with the following details:
Status: runnable
Command: KILLED/ROLLBACK (see I tried to kill them earlier)
Application: SQL Query analyser (although this instance of Query analyser
has since been closed)
Any ideas how to get rid of them?...len wrote:
> I've got a number of processes that are stuck on my server and are locking
> up a table or two and I'd like to kill them. Unfortunately, after trying t
o
> "Kill process" in SQL ENterprise manager, the processes involved are still
> there with the following details:
When you kill a process in SQL it has to perform a rollback on the
process. This means that if this process was in the middle of updating 1
million records, it would have to roll back all of those records to the
state before the process started.
Aaron Weiker
http://aaronweiker.com/
http://www.sqlprogrammer.org/