<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Deadlocks on SQLSurfer</title>
		<link>http://localhost:1313/tags/deadlocks/</link>
		<description>Recent content in Deadlocks on SQLSurfer</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Thu, 27 Aug 2026 20:21:31 -0500</lastBuildDate>
		
			<atom:link href="http://localhost:1313/tags/deadlocks/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>SQL Server Blocks vs Deadlocks</title>
				<link>http://localhost:1313/posts/sql-server-blocks-vs-deadlocks/</link>
				<pubDate>Thu, 27 Aug 2026 20:21:31 -0500</pubDate>
				<guid>http://localhost:1313/posts/sql-server-blocks-vs-deadlocks/</guid>
				<description>&lt;p&gt;Deadlocks and excessive blocking is the bane of many development teams and DBAs. They are often at the root of performance problems. Understanding each of these problems and how to solve the root cause can be difficult. I find that the terms are used interchangeably and  frequently mixed. Understanding the difference, and diagnosing the issue is crucial to resolving these problems. Both happen due to incompatible locks being held or requested on tables, but they differ in their root cause. Some troubleshooting methods work for both problems, but deadlocks generally require logic changes to fix permanently and consistently.&lt;br&gt;&#xA;This post is aimed at giving a general background on blocking and deadlocks. It also shows some basic methods to find these problems and general ways to fix them. I&amp;rsquo;m not going into extreme detail. This is just an introduction.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
