June 13, 2003 at 9:45 am
Hi ,
I was trying to migrate a standard database maintenance plan across multiple Servers. I scripted out the job from the original server and tried to run in the new one , The job was created Successfully ,but on execution it failed with the following message.
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Any Suggestions...
Regards and thanks for all help.
Elias Peter
June 13, 2003 at 9:55 am
The maintenance plan itself must be created, not just the jobs. PITA, and I'm sure there's a way to script out the plan, but I haven't bothered. They are pretty static and creating them on each server, while a pain, is mostly a one time event, so I just do it.
Steve Jones
June 13, 2003 at 9:58 am
Hi,
I don't know whether this will help but I had a similar problem with a job I migrated to another server. I had to change the originating_server field in sysjobs to get the job enabled.
Ritch
"I didn't do anything it just got complicated" - M Edwards
June 17, 2003 at 1:59 pm
It is definetly easier to create then on each server.
June 17, 2003 at 2:06 pm
Thank you all. I thought there was a easier way of deploying same Job on multiple servers ,eventually I created one on each server.
June 17, 2003 at 5:56 pm
actually you can do your own maintenance jobs. you will notice that every time you create maintenance plan using the wizards, it creates one job for backup, integrity checks, and optimization. using SQLMAINT command (check syntax from BOL), you can create a batch job that would create those for you.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply