<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx</link><description>Back in SQL Server 2000, and all previous versions, the set option SET DEADLOCK_PRIORITY had 2 values, LOW and NORMAL, and LOW did not mean that you had lower priority for being selected the victim. Setting this option to LOW was like setting the martyr</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#193</link><pubDate>Sat, 09 Sep 2006 17:03:06 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:193</guid><dc:creator>Hugo Kornelis</dc:creator><description>Hi Kalen,&lt;br&gt;&lt;br&gt;The answer to your final question (what will happen if everyone gives themselves the highest priority) is that the end result will be the same as when nobody uses this option. On a deadlock, SQL Server will first compare deadlock priorities; if they are equal, the deadlock victim is the one that's the least expensive to rollback.&lt;br&gt;&lt;br&gt;So nobody setting a deadlock priority or everybody setting the maximum deadlock priority yields the same end results.</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#194</link><pubDate>Sat, 09 Sep 2006 17:04:36 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:194</guid><dc:creator>Hugo Kornelis</dc:creator><description>Oops, forgot to add....&lt;br&gt;&lt;br&gt;If you wish to receive more comments, allowing anonymous comments might help. (Though in all honesty, I have anonymous comments enabled on my site, and I'm not exactly swamped with comments either)</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#195</link><pubDate>Sat, 09 Sep 2006 23:26:13 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:195</guid><dc:creator>Matthew Martin</dc:creator><description>That's cool, I'll probably use that. &amp;nbsp;I would probably put UPDATES/INSERTS on high priority and SELECTS on low priority, but one would imagine that connections just doing SELECTS are the first candidates for deadlock kills anyhow. &amp;nbsp;Unless deadlock victims are normally chosen at random--&lt;br&gt;&lt;br&gt;I'm an avid reader of SQL blogs, and even famous sorts like Kim Tripp and Bill Vaugn have bloglines.com subscribers in the single and double digits. (RSS subscriptions being a really rough gauage of readership)&lt;br&gt;&lt;br&gt;As soon as the book ships, the comments will be numerous to be a hassle.</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#198</link><pubDate>Sun, 10 Sep 2006 18:09:14 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:198</guid><dc:creator>Adam Machanic</dc:creator><description>Kalen,&lt;br&gt;&lt;br&gt;Be patient -- you just started last week and not many people know you're here yet! &amp;nbsp;However, you were included in today's Database Daily update from SSC, so that will help a bit. &amp;nbsp;And as Hugo pointed out, you have anonymous comments disabled at the moment. &amp;nbsp;If you enable that option, you may see more comments from people who don't want to sign up. &amp;nbsp;Personally, I have them disabled as I don't want any kind of blog SPAM.</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#199</link><pubDate>Sun, 10 Sep 2006 18:10:29 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:199</guid><dc:creator>Adam Machanic</dc:creator><description>Looking again after signing out, I guess you do have anonymous comments enabled... get ready for the flood ;-)&lt;br&gt;</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#200</link><pubDate>Sun, 10 Sep 2006 22:20:48 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:200</guid><dc:creator>Kalen Delaney</dc:creator><description>Hi Adam&lt;br&gt;&lt;br&gt;Yes, I know I just started ... but there were all these 'views' and no one was saying anything. Besides, I had a smiley there. :-) &amp;nbsp;I just wanted readers to know that comments are more than welcome.&lt;br&gt;&lt;br&gt;And I've certainly got plenty to do while waiting for all the comments to start rolling in. &lt;br&gt;&lt;br&gt;--Kalen</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#208</link><pubDate>Thu, 14 Sep 2006 09:28:28 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:208</guid><dc:creator>ACALVETT</dc:creator><description>I just heard about your blog and it brought a big smile to my face. Looking forward to reading more great articles.&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#219</link><pubDate>Mon, 18 Sep 2006 07:56:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:219</guid><dc:creator>Richard</dc:creator><description>Hi&lt;br&gt;&lt;br&gt;Slightly nervous about posting in such exalted company! &amp;nbsp;Will be keeping a close eye on your blog now I have seen it.&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#234</link><pubDate>Thu, 21 Sep 2006 16:32:03 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:234</guid><dc:creator>TKnoob</dc:creator><description>Just saw your blog. &amp;nbsp;Love your books. &amp;nbsp;Please continue to blog away. &amp;nbsp;And thanks.</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#247</link><pubDate>Mon, 25 Sep 2006 08:38:18 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:247</guid><dc:creator>Why 21?</dc:creator><description>What is the point in having 21 possible values when three is enough?</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#338</link><pubDate>Thu, 02 Nov 2006 22:08:00 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:338</guid><dc:creator>Kevin3NF</dc:creator><description>Hi Kalen,&lt;br&gt;&lt;br&gt;I just stumbled across this site today, and this was the second post I read. &amp;nbsp;I've been studying deadlocks recently, so this was quite timely. &amp;nbsp;&lt;br&gt;&lt;br&gt;Thanks,&lt;br&gt;&lt;br&gt;Kevin3NF</description></item><item><title>Did You Know?  Nobody upgraded the SET OPTIONS screen in SQL Server Management Studio</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#1789</link><pubDate>Tue, 17 Jul 2007 22:16:57 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:1789</guid><dc:creator>Kalen Delaney</dc:creator><description>&lt;p&gt;In SQL Server Management Studio, the screen where you choose which SET options to enable for all connections&lt;/p&gt;
</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#1901</link><pubDate>Mon, 23 Jul 2007 11:13:29 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:1901</guid><dc:creator>Rob</dc:creator><description>&lt;p&gt;This was very helpful Kalen. &amp;nbsp;Very interesting information. &amp;nbsp;I am going to take advantage of this in SQL Server 2005 now.&lt;/p&gt;
</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#7424</link><pubDate>Fri, 20 Jun 2008 19:43:41 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:7424</guid><dc:creator>kalen</dc:creator><description>&lt;p&gt;I have spent 2 hours looking for an answer and you are the only one who gave it to me. Thank you.&lt;/p&gt;
</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#43716</link><pubDate>Mon, 04 Jun 2012 16:00:40 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:43716</guid><dc:creator>Jeremy Odom</dc:creator><description>&lt;p&gt;Is it best to set DEADLOCK_PRIORITY from within your stored procedure or just before the stored proc is called? &lt;/p&gt;
</description></item><item><title>re: Did you know? -- New Deadlock Priorities</title><link>http://sqlblog.com/blogs/kalen_delaney/archive/2006/09/09/192.aspx#43718</link><pubDate>Mon, 04 Jun 2012 16:54:07 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:43718</guid><dc:creator>Kalen Delaney</dc:creator><description>&lt;p&gt;Jeremy&lt;/p&gt;
&lt;p&gt;I recommend setting it only in the scope in which you need it. If you only need it for the proc, set it in the proc, and then when the proc is over, it will be automatically reset to the value it was before.&lt;/p&gt;
&lt;p&gt;~Kalen&lt;/p&gt;
</description></item></channel></rss>