I have seen cases where indexes ed greatly with deadlocks even if it
didn't cure them. If you have two processes which have transactions which
can deadlock with each other, then making one or both of these processes run
faster can greatly reduce the chances that they are both running at the same
time and thus at least decrease the number of deadlocks.

Tom

"Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:OK7$qnBkIHA.1188@TK2MSFTNGP04.phx.gbl...
> Typically, adding an index will not resolve deadlock problems, though it
> may the error get raised faster. :-) However, that might not always
> be the case. Do you have more information about the deadlock? Which
> object is deadlocked, and what is the other process trying to do? Adding
> Geoff's indexes aren't going to hurt anything, so I would suggest just
> adding them, and then wait to see if you get the deadlock again. Who
> knows, maybe it is the magic pill... but impossible to know without having
> more information about the deadlock itself...
>
>
>
> "Chris Wood" <anonymous@microsoft.com> wrote in message
> news:OaF3pkBkIHA.1168@TK2MSFTNGP02.phx.gbl...
>> Hi,
>>
>> We run maintenance plan created SSIS packages to backup our databases.
>> The final step is the cleanup of the jobhistory. We see the occasional
>> deadlock coming from sp_maintplan_delete_log.
>>
>> Now I know that msdb backup tables have no indexes. We are looking at
>> implementing Geoff Hiten's suggested indexes
>> http://weblogs.sqlteam.com/geoffh/ar...ce-Tuning.aspx
>>
>> Will this our deadlocks?
>>
>> Thanks
>>
>> Chris
>>
>
>