﻿<?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 High Availability  / DEADLOCK_PRIORITY vs System Processes / 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>Wed, 19 Jun 2013 20:10:45 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: DEADLOCK_PRIORITY vs System Processes</title><link>http://www.sqlservercentral.com/Forums/Topic1042167-1549-1.aspx</link><description>ah well if it's application then it's processes/code that you need to change - if it's system stuff then you need to find a quiet time. I support real 7 x 24 hour systems so things like index rebuilds are quite painful.You can set the deadlock priority for your session ith a set command - check it out in BOL.  However it doesn't stop deadlocks - just allows you to favour one session over another as the deadlock victim which is why I've never used it to date.</description><pubDate>Tue, 11 Jan 2011 13:39:01 GMT</pubDate><dc:creator>colin.Leversuch-Roberts</dc:creator></item><item><title>RE: DEADLOCK_PRIORITY vs System Processes</title><link>http://www.sqlservercentral.com/Forums/Topic1042167-1549-1.aspx</link><description>[font="Verdana"][quote]...I don't think you can alter the priority for system processes, you could try altering your sessions but [b]I figure that might be risky.[/b][/quote]:discuss: how?In general I want to get rid of Blocking/Dead locking ultimately, as if a process which may take more than 1 hour for execution and a single sql statement which can trigger out deadlock and would may cause/stop the long running process...!:-)[/font]</description><pubDate>Tue, 11 Jan 2011 04:38:26 GMT</pubDate><dc:creator>Abrar Ahmad_</dc:creator></item><item><title>RE: DEADLOCK_PRIORITY vs System Processes</title><link>http://www.sqlservercentral.com/Forums/Topic1042167-1549-1.aspx</link><description>not quite sure what you're asking but yes "system" processes can evoke deadlocks - that's why you have to configure your server to avoid such issues. Index rebuilds for instance can also cause deadlocks.I don't think you can alter the priority for system processes, you could try altering your sessions but I figure that might be risky.</description><pubDate>Thu, 06 Jan 2011 15:24:02 GMT</pubDate><dc:creator>colin.Leversuch-Roberts</dc:creator></item><item><title>DEADLOCK_PRIORITY vs System Processes</title><link>http://www.sqlservercentral.com/Forums/Topic1042167-1549-1.aspx</link><description>[font="Verdana"]During execution of a critical application process; a system process (e.g db auto shrink) evoked and the process prolonged to manually rollback. Is DEADLOCK_PRIORITY can be useful against system processes?We need to disable db auto shrink, but .... any other solution? :cool:[/font]</description><pubDate>Mon, 03 Jan 2011 23:12:49 GMT</pubDate><dc:creator>Abrar Ahmad_</dc:creator></item></channel></rss>