Re: Deadlocks in msdb on SQL2005
I had raised a bug on Connect about the cleanup just running the delete
stored proc without a job name parameter bug 322320, but then Andrew Kelly
corrected me in how attaching a cleanup task to a maintenance plan had no
idea what the job was called so it could add the parameter.
I may look at running the cleanup a number of times a day so it does not
deadlock with other maintenance jobs adding to the jobhistory.
Thanks again.
Chris
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:%23m9FvxBkIHA.5208@TK2MSFTNGP04.phx.gbl...
> If you can reproduce this easily, I would file a bug on connect. Multiple
> maintenance plans should play nice.
>
>
>
> "Chris Wood" <anonymous@microsoft.com> wrote in message
> news:OGC8ovBkIHA.4244@TK2MSFTNGP06.phx.gbl...
>> Understanding how the cleanup tasks work now rather than before we
>> created the jobs makes this a much better idea. We may well have to
>> change our backups to just do the one cleanup job a day.
>
>
|