May 30, 2007 at 11:52 am
IN the BOL, the following is listed:
But for a couple of our database servers, this doesn't happen or more to the point the maintenance plan does not remove/delete the backups older than 3 days (that is what set it to)...This happens on SQL Server 7.0 & 2000...any thoughts???
May 30, 2007 at 12:06 pm
Had this problem with maintenance plans at my previous employer. We had to delete and recreate the maintenance plans to get it to work properly. If we had to make any changes, we got to the point we simply deleted the old plan and would create it again from scratch making the approriate changes we wanted to implement in the new plan.
Sorry I couldn't be more helpful, but maybe someone else has a better answer.
May 31, 2007 at 10:21 am
I just want to confirm Lynn's post. This has been an extremely sporadic issue in SQL 2000. The only solution was to drop and recreate the maintenance plan.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
May 31, 2007 at 10:37 am
Third confirmation here. Whack the plan and re-set it up. I'd also check the logs for the plan and see if anything else is amiss.
May 31, 2007 at 12:05 pm
One more confirmation. Drop the plan and recreate it. It sucks, but it works
May 31, 2007 at 2:25 pm
OK thanks guys! We are doing that now. I just wanted to through that question out there to see if someone else knew of something else we could try or do...but yes, we recreate the plan every few weeks and as long as we do that it works out fine but leave it for more than 3 weeks and you get database backups stacking up....Thanks again!
May 31, 2007 at 3:32 pm
And in 2005 there was/is an issue with SP2. If you have your expire set for DAYS, you need to recreate it after applying SP2 (I'm not sure they fixed with the SP2 update - SP2a).
-SQLBill
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply