Database dropped but Maintenance plan still tries to back it up

  • Hi all

    I deleted a database without issue, but when the maintenance plan runs and tries to back it up the dropped database name is not available and cause the plan to return an error. The backup tasks is set to all database and does not display the dropped db name. Does anyone know where this might be stored so that I can try deleting the record instead of redoing the plan?

    thanks

  • Make some minor change to the plan, then undo that change. That might reset it.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • I tried that, did not help. The sql behind the backup task does not use the dropped DB name, but it is listed in the error message.

  • In that case, there's almost certainly some place in the plan that lists specific databases to run, as opposed to "All User databases".

    Another possibility occurs to me: I think some early versions of SQL 2005 had trouble with maintenance plans. I'm not sure, but I seem to remember one of the service packs fixing that. Is it possible you have an unpatched copy of the software? (I could be misremembering this, and don't have time to research it right now. You might want to do so yourself.)

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • You are correct, the early versions had issues with Maintenance Plans. The server is up to date on service packs. I have deleted and rebuilt the Maintenance plan and that fixed the issue. I was hoping to find the plan as it is stored in tables and try and fix it that way. I will continue to look when time permits.

    so long story short... redoing the plan fixed the issue, but left me with more questions...

    thanks

  • Last time this happened to me I just changed the existing plan to "All Databases" and then changed it back to selected databases with the appropriate ones ticked--fixed the issue for me, although it's a bit awkward to have to do.

  • There are definite weaknesses in the wizard and the plan builder. I prefer custom code for that kind of thing. The plans are great for new DBAs who haven't yet learned the most advanced methods of getting these things done, but they do have their quirks that can be quite annoying.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Ouch! 😉

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply