Should SQL 2000 and 2005 maintenance plans be resilient to a database being detached or offlined?
I detached / offlined a few databases, and now the maintenance plans are failing in their entirity because SQL can't find/connect to the database. It seems to me a simple matter for SQL to either re-calculate the script upon such a change OR to have a wizard-generated maintenance plan that will (at worst) just emit a warning about the unavailable databases and continue with the independent parts of the script, such as the other databases.
As it is, it seems to me to be required that I go into each step-block of the "User DBs" maintenance plan, switch the setting to "All databases", ok out of the wizard, save, go back in and set it back to "All databases except the system databases", ok out of the wizard, and save. That's a lot of clicks! (That's 2005, with a similarly awkward list for 2000)
Is it normal? or is something else wrong?