January 3, 2011 at 11:12 pm
[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? 😎
[/font]
January 6, 2011 at 3:24 pm
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.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
January 11, 2011 at 4:38 am
[font="Verdana"]
...
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.
: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]
January 11, 2011 at 1:39 pm
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.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply