<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>BLOCK on DBA von Nebenan</title><link>https://dbavonnebenan.de/en/tags/block/</link><description>Recent content in BLOCK on DBA von Nebenan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 08 Jun 2025 07:49:24 +0200</lastBuildDate><atom:link href="https://dbavonnebenan.de/en/tags/block/index.xml" rel="self" type="application/rss+xml"/><item><title>Reporting Blocks and Deadlocks: When the 3rd-Party Vendor Demands Evidence</title><link>https://dbavonnebenan.de/en/reporting-sql-server-blocks/</link><pubDate>Mon, 28 Apr 2025 15:19:36 +0200</pubDate><guid>https://dbavonnebenan.de/en/reporting-sql-server-blocks/</guid><description>Knowing that SQL Server has blocking or deadlock problems is still quite easy. You usually notice this in the application, and with the right queries, you can also display the corresponding blocking chains. The simplest way to do this is with &lt;a href="http://whoisactive.com"&gt;http://whoisactive.com&lt;/a&gt;. I also have a custom development that I will present in a later</description></item></channel></rss>