{"id":193,"date":"2012-05-03T13:00:23","date_gmt":"2012-05-03T13:00:23","guid":{"rendered":"https:\/\/sqlserverlearner.azurewebsites.net\/2012\/05\/03\/who-killed-my-sql-server-process\/"},"modified":"2012-05-03T13:00:23","modified_gmt":"2012-05-03T13:00:23","slug":"who-killed-my-sql-server-process","status":"publish","type":"post","link":"https:\/\/sqlserverlearner.com\/2012\/05\/03\/who-killed-my-sql-server-process\/","title":{"rendered":"Who Killed My SQL Server Process?"},"content":{"rendered":"
Who Killed My SQL Server process – session – connection – spid?<\/strong> You might be interested in policing as to who killed your process? In this post let us analyze a technique to sport the user who killed your process:<\/p>\n Using SQL Server error Log:<\/strong> So first query the latest error log for the word kill. You can find the logdate,the killed SPID ,Host name and host processid that killed the process in the result<\/p>\n
\nIf you are sharing single database server with multiple users you might many times end up your process being force killed and an error message shown below comes up.
\n
\nMsg 233, Level 20, State 0, Line 0
\nA transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 – No process is on the other end of the pipe.)
\n<\/font><\/p>\n
\nWas it done intentionally or some server side error occurred?<\/p>\n
\nSQL Server logs errors to the sql server error log, It can be found that it also logs the killing of processes in its error log.<\/p>\n
\n[sql]
\nEXEC sys.xp_readerrorlog 0,1,’kill’
\n[\/sql]
\nIf you cannot find any results then continue with the next error log
\n[sql]
\nEXEC sys.xp_readerrorlog 1,1,’kill’
\n[\/sql]<\/p>\n