April 23, 2010 at 1:51 pm
Hi,
if i create for example a maintenance plan that backup my database,after successfully created the maintenance plan i go and edit the sql agent job that correlate with that maintenance plan and insert another step inside this job (not in the maintenance plan itself,in the sql agent jobs) i save my work and it is ok.
but when i edit the maintenance plan itself after i save the work the new step in the sql agent that i added before is deleted.why is that?
THX
April 23, 2010 at 2:43 pm
Because the maintenance plan recreates the agent job every time you make changes to it and save it.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
June 17, 2011 at 7:22 am
I just experienced this issue as well. I have a job that runs a database backup as the first step. There are several steps after that to do other processes based on a successful database backup being taken.
I had to change the path that the backup job used to write the backup files. When I saved the maintenance plan change I didn't realize the job was entirely recreated and that all the subsequent steps were lost.
In order to prevent this from happening, what is the recommended approach to preserve job steps dependent upon a maintenance plan as one of the job steps? If I had scripted out the jo, made my maintenance plan change and saved it, then recreated the job using the script would the change to the maintenance plan still be there? I just want to know how to prevent this in the future as I have other backup file paths to change on other servers.
Thanks!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply