<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Head Blocker on SQL Server Scripts</title><link>https://www.sqlserver70.com/tags/head-blocker/</link><description>Recent content in Head Blocker on SQL Server Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>SQLServer70.com</copyright><lastBuildDate>Sun, 01 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sqlserver70.com/tags/head-blocker/index.xml" rel="self" type="application/rss+xml"/><item><title>SQL Server Blocking Detection: Find Blocked Sessions</title><link>https://www.sqlserver70.com/post/sql-server-blocking-detection-find-blocked-sessions/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.sqlserver70.com/post/sql-server-blocking-detection-find-blocked-sessions/</guid><description>
&lt;p&gt;Blocking happens when one session holds a lock that another session needs, so the second session waits. The query below lists every request that is waiting on another session right now: who is blocked, who is blocking, the wait type and wait time, the database, and the SQL text on both sides.&lt;/p&gt;
&lt;script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563"
crossorigin="anonymous"&gt;&lt;/script&gt;
&lt;ins class="adsbygoogle"
style="display:inline-block;width:728px;height:90px"
data-ad-client="ca-pub-1012089347386563"
data-ad-slot="8593449130"&gt;&lt;/ins&gt;
&lt;script&gt;
(adsbygoogle = window.adsbygoogle || []).push({});
&lt;/script&gt;
&lt;h2 id="purpose-and-overview"&gt;Purpose and Overview&lt;/h2&gt;
&lt;p&gt;The finding that matters in a blocking incident is the head blocker, the one session at the front of the chain that is not itself waiting on anyone. Everything behind it is a symptom. &lt;code&gt;sys.dm_exec_requests&lt;/code&gt; carries the &lt;code&gt;blocking_session_id&lt;/code&gt; column that links each waiting request to the session it is waiting on, and joining it to &lt;code&gt;sys.dm_exec_sessions&lt;/code&gt; and &lt;code&gt;sys.dm_exec_sql_text&lt;/code&gt; turns that single column into a readable list of victims, owners and statements.&lt;/p&gt;</description></item></channel></rss>