Is ok to kill process with security id 0x01 ??
-
As stated in the subject; Is ok to kill process with security id 0x01 ??
Thank you for your help.
-
Typically no as thats the SA login and runs system process, now depending how you have your security setup it might be that everything is logging in as SA, which is a very bad idea.
If the SPID is <= 50 then no dont kill it, if it isn't trace it back to a user or machine and if its not the server find out what the person on the other end is doing before doing anything with the SPID.
-
anthony.green (9/27/2012)
If the SPID is <= 50 then no dont kill it,In my experience, Service Broker internally activated sessions are often on SPIDs less than 50
____________________________________________________
Deja View - The strange feeling that somewhere, sometime you've optimised this query before
How to get the best help on a forum
http://www.sqlservercentral.com/articles/Best+Practices/61537
-
How have you identified that this spid is causing an issue?
-
Do you know what the session is doing? Do you know what effect rolling back anything it's doing will have?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
Thank you all for your quick responese. Is good to know no < 50 killing.
-
Well, you can't kill a system process (and the old rule that spids < 50 are system is no longer true, there can be system spids with session IDs higher)
KILL 1Msg 6107, Level 14, State 1, Line 1
Only user processes can be killed.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply