https://www.pachadata.com/en/tags/extended-events/Recent content in Extended Events on Rudi BruchezHugoenFri, 28 Aug 2026 16:14:17 +0200https://www.pachadata.com/en/docs/howtos/performance/blocking/Fri, 28 Aug 2026 00:00:00 +0000https://www.pachadata.com/en/docs/howtos/performance/blocking/<div class="alert alert-success" role="alert"><div class="h4 alert-heading" role="heading">TL;DR</div> <p>Blocking happens when one session waits for a lock held by another session. To find out <em>who</em> blocks <em>what</em>, you enable the <code>blocked process threshold</code> and start an Extended Events session that records a report every time a block exceeds that threshold. You let it run for a few days, compress the <code>.xel</code> files and send them for analysis. The impact on production is negligible.</p> </div> <p>This page is a procedure to follow from start to finish. If you are in a hurry, the five steps are: <a href="https://www.pachadata.com/en/docs/howtos/performance/blocking/#step-1--set-the-blocked-process-threshold">set the threshold</a>, <a href="https://www.pachadata.com/en/docs/howtos/performance/blocking/#step-2--create-and-start-the-event-session">create the session</a>, <a href="https://www.pachadata.com/en/docs/howtos/performance/blocking/#step-3--let-the-collection-run">let it run</a>, <a href="https://www.pachadata.com/en/docs/howtos/performance/blocking/#step-4--collect-and-send-the-files">collect the files</a>, <a href="https://www.pachadata.com/en/docs/howtos/performance/blocking/#step-5--clean-up">clean up</a>.</p>