Posted by Joe Weinstein on 03/09/06 22:07

traceable1 wrote:

> I am running SQL Server 2000 SP4 (w/AWE hotfix) on a 32-bit Windows
> 2003 Server (SP1).
>
> I am trying to run an Index defrag and rebuild job. It has worked fine
> in the past, but lately I'm getting this:
>
> Msg 1205, Sev 13: Transaction (Process ID 73) was deadlocked on lock
> resources with another process and has been chosen as the deadlock
> victim. Rerun the transaction. [SQLSTATE 40001]
>
>
>
>
>>From what I've read, I can only lower the priority on other processes.
> Since there are multiple applications running several different things
> on this database, that seems impossible. I really just want this opt
> job to finish - it's fine if it takes a while or needs to go back and
> run something again, but it absolutely needs to finish!
>
> Without this optimization, our applications run extremely slow.
>
> Please help!

I have long wanted MS to separate deadlock priority from run priority.
If I have a big backround admin task, I would like to say that the run
priority is *low*, taking only idle cycles, but the deadlock priority
is very high, so that once the job begins, it will definitely finish at
some point.
Joe

[Back to original message]