Contents
What happens when a process is blocked?
A process always exists in exactly one process state. A process that is blocked is one that is waiting for some event, such as a resource becoming available or the completion of an I/O operation. When the other task is blocked, it is unable to execute until the first task has finished using the shared resource.
How do you kill a head blocker?
Killing a Blocking Process After you have connected, right click on the instance name and select ‘Activity Monitor’ from the menu. Once Activity Monitor has loaded, expand the ‘Processes’ section. Scroll down to the SPID of the process you would like to kill. Right click on that line and select ‘Kill Process’.
What is a head blocker?
in my limited understanding , head blocker means a session is currently running and is locking a resource and that resource is also needed by another session. so all sessions that need access to that resource cannot continue thus the “blocked by” that I see in activity monitor.
Is it useful to have blocked process report?
Having a blocked process report is useful but often in such situation, there are a lot of processes that sometimes blocked each other’s and we have to find out among this can of worms the real responsible.
How to find blocked processes in SQL Server?
Most of times it happens because ill-behaved process that blocks other tasks for short periods. How can we find this kind of problem? SQL Server has a server configuration called Blocked Process Threshold. We can set a value, in milliseconds, and SQL Server will generate a report every time a process is blocked by this amount of time.
How to get an alert over a BLOCKED process?
Alerts: It’s possible to generate an alert over blocked process reports and generate an email as alert response. You can create an extended events session to capture the blocked process report: After creating and starting the session, we can query the reports captured by this session.
Which is the process that is blocking a session?
Let’s begin by the first category. You can see here the hierarchy tree and the blocked interactions that exist between the different processes. The above picture shows the process id = 72 that is blocking the process id = 73. In turn, the process = 73 is blocking other sessions (with id = 75, 77).