Re: Sql 2005 can't update maintenance plans?

Paul,

Again thanks for taking the time to respond.

My Full, Differential and Transaction Log backup process are in separate
Maintenance plans that contain only one Step (or SSIS) object. More than
once I've updated these objects by adding a database and saved the update.
Upon reopening the SSIS object (in SMS) the new database list shows
correctly. Unfortunately, the backup refuses to process the new database
(and continues to use the old database list) until I completely drop the
Maintenance plan (which automatically drops the associated Server Agent job)
and totally rebuild it. It's like the Server Agent job doesn't get the
'word' that the database list has been updated.

This happens consistently on my instance. Makes me crazy.

We use SSIS heavily for data import, export & transformation purposes. I
guess one option would be to create the maintenance plan objects using SSIS
directly rather than via the SMS wizard and then physically create the
necessary Server Agent jobs within SMS to call the backup jobs created
within SSIS. Arrrrrggggg.

At this point the issue is simply an annoyance since we don't add many new
databases anymore.

Again thanks to you and Mr. Wie Lu for your suggestions.

Barry
in Oregon




"Paul Shapiro" <paul@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:e$egODepGHA.4188@xxxxxxxxxxxxxxxxxxxxxxx
Editing the maintenance plan in Management Studio opens the SSIS design
view, although it is still in Management Studio. If the maintenance plan
includes more than one task, then each task is a separate item in the SSIS
design view. You need to individually edit each one of those items to
fully add a new database to that existing maintenance plan.
Paul Shapiro

"frostbb" <frostbb@xxxxxxxxxxxxxxxxx> wrote in message
news:OyNsPjSpGHA.1440@xxxxxxxxxxxxxxxxxxxxxxx
Paul,

Thanks for the response.

Guess I thought I ... was ... explicitly saving the changes since when I
reopened the maintenance plan the new database that I'd added was
included in the list.

What do you mean by editing eacho of the maintenance plan's lower-level
tasks ?? Are you using SMS or SSIS to manage your maintenance plans?

Any enlightenment would be greatly appreciated.

Barry
in Oregon


"Paul Shapiro" <paul@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OgR%23QjDpGHA.516@xxxxxxxxxxxxxxxxxxxxxxx
I've added databases to maintenance plans and the newly added databases
are being processed. It's more trouble than it was in SQL2K since you
have to edit each of the maintenance plan's lower-level tasks. In SQL2K
you could set the databases as a general property of the entire
maintenance plan. After making the edits, you have to explicitly save
the changes before closing the editor.
Paul Shapiro

"frostbb" <frostbb@xxxxxxxxxxxxxxxxx> wrote in message
news:OntzaWDpGHA.1592@xxxxxxxxxxxxxxxxxxxxxxx
Dan English posted the message below on Jan 24. Looks like the thread
has been expired from the microsoft.public.sqlserver.server news group.

I'm experiencing the same problem.

I'm wondering if a workaround for this issue has been published ?? <<
I would expect that a system stored proc is getting triggered
correctly after the update [ok] button is mashed.

Haven't had any luck finding further mention of this issue with my
Google searches since the return to "+2005 +"Maintenance Plan"
+Changes" returns a huge number of non-related hits.

Everytime we add a new database to our server I have to physically
delete and recreate my Full, Differential and Transaction Log backup
maintenance plans. To say the least it's a PIA ... although since
we're in the middle of a migration from a Unix to Sql Server platflom I
can basically recreate the plans in my sleep by this time. Regardless
its very frustrating that SSIS objects reflect the change but don't
actually physically implement the changes.

Thanks in advance.

Barry
in Oregon

==============================================================================

From:Dan English
Date:Tues, Jan 24 2006 10:42 am
Email: "Dan English" <dan_engli...@xxxxxxx>
Groups: microsoft.public.sqlserver.server

I created a couple of maintenance plans in Sql 2005 and they run fine.
When
I edit them and make changes though, the changes seem to be saved but
they
don't get executed. It seems I have to delete the entire plan and
recreate
it to make changes. Has anyone else noticed this?




.

Loading