Afficher un message
Vieux 27/03/2008, 15h48   #2
Aaron Bertrand [SQL Server MVP]
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Deadlocks in msdb on SQL2005

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
>



  Réponse avec citation
 
Page generated in 0,07843 seconds with 9 queries