﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 - General  / Deadlocks and metadata locks / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Fri, 24 May 2013 17:29:43 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Deadlocks and metadata locks</title><link>http://www.sqlservercentral.com/Forums/Topic1398680-391-1.aspx</link><description>No one ? :w00t: Not even Sean ? Gila ? GSquared ?</description><pubDate>Thu, 20 Dec 2012 08:58:30 GMT</pubDate><dc:creator>sqlGDBA</dc:creator></item><item><title>Deadlocks and metadata locks</title><link>http://www.sqlservercentral.com/Forums/Topic1398680-391-1.aspx</link><description>I have a deadlock situation that I am having some difficulty understanding. Attached is the deadlock graph - I am trying to understand why we see so many metadata locks. Is a metadata lock the same as a Schema lock ? I think not, but the Object ID in the matadata lock actually belongs to a user table(not system tables/management views).I would appreciate any insights anyone may have as to what exactly a metadata lock is and why does SQL Server use them ?</description><pubDate>Wed, 19 Dec 2012 14:42:38 GMT</pubDate><dc:creator>sqlGDBA</dc:creator></item></channel></rss>