如何在Sybase中杀死一个不守规矩的spid？-HowdoIkillanunrulyspidinSybase?

3  

System processes cannot be killed. For example in the output of sp_who where cmd is NETWORK HANDLER, MIRROR HANDLER and CHECKPOINT SLEEP (or rarely, CHECKPOINT) and AUDIT PROCESS cannot be killed. If they have status as "recv sleep", "send sleep", "alarm sleep" and "lock sleep" , they can be killed.

系统进程无法被杀死。例如,在sp_who的输出中,cmd是NETWORK HANDLER,MIRROR HANDLER和CHECKPOINT SLEEP(或很少,CHECKPOINT)和AUDIT PROCESS无法被杀死。如果他们的状态为“recv sleep”,“send sleep”,“alarm sleep”和“lock sleep”,则可以将其杀死。

In sp_who output, you cannot tell whether a process whose status is "recv sleep" belongs to a user who is using SQL Server, but may be pausing to examine the results of a command, or whether the process indicates that a user has rebooted a PC or other terminal, and left a stranded process.You can learn more about a questionable process by querying the sysprocesses table for information. For ex :

在sp_who输出中,您无法判断状态为“recv sleep”的进程是属于正在使用SQL Server的用户,还是可能暂停以检查命令的结果,或者进程是否指示用户已重新引导PC或其他终端,并留下了搁浅的进程。您可以通过查询sysprocesses表获取有关可疑进程的更多信息。例如:

select hostprocess, program_name from sysprocesses where spid = 8

从sysprocesses中选择hostprocess,program_name,其中spid = 8

If program_name is isql you know that this spid can be killed.(and so forth ... )

如果program_name是isql,你知道这个spid可以被杀死。(等等...)

0  

I have a client application that sometimes does similar things. The client is usually in the middle of a select, but is no longer retrieving rows. (This may be a client side cursor, but I'm not sure). These spids seem un-killable. I have to find the user and ask them to log off.

我有一个客户端应用程序,有时做类似的事情。客户端通常位于select的中间,但不再检索行。 (这可能是客户端游标,但我不确定)。这些spid似乎是不可杀戮的。我必须找到用户并要求他们注销。

The other scenario in which I've had these is after errors or stacktraces on the server. Check your errorlog to see if there's any dodgy entries in there. If there is then a restart is going to be your only option.

我有这些的另一种情况是在服务器上出现错误或堆栈跟踪之后。检查您的错误日志,看看那里是否有任何狡猾的条目。如果有,那么重启将是您唯一的选择。