December 24, 2010 at 11:55 am
I'm trying to tie several existing mantenance jobs & scripts into a single SQLAgent job.
I'm finding that that if I add a step of type "SQL Server Integration Services Package" and select a pre-exiting Mantenance Plan, the step will run in about 1 second and report success, but not actually do what it si supposed to do, such as a database backup or DBCC check.
What am I missing?
December 26, 2010 at 9:53 am
Try adding an output file to the job step. It should give more information regarding the job execution.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
December 26, 2010 at 10:14 am
You need to modify the command line when executing maintenance plans. The reason for this is because of the sub-plan capability, which just creates separate containers inside a single package for each sub-plan.
To identify which sub-plan needs to run, you have to pass on the command line the appropriate command to enable that sub-plan.
The easiest way to get this command line is to schedule the maintenance plan and save the plan. Once that is done, you will have the default agent job available and you can pull the command line from the job. Once you have that, add it to your agent job and remove the schedule for the maintenance plan.
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
December 27, 2010 at 12:54 pm
You can copy the sql script of step job that you want to merge with first job. And then create step 2 inside the first job. Save this job as the schedule will be same now. Should run properly.
Disable the other job.
December 27, 2010 at 2:03 pm
I agree with the last post. I would tend to find the original job, and then copy the command line.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply