|
|
|
Valued Member
 
Group: General Forum Members
Last Login: Tuesday, June 16, 2009 9:55 AM
Points: 69,
Visits: 197
|
|
I am currently using Maintenace Plans to schedule jobs for User / System databases. Is it recommended to run each step at completely different times so there is no overlap. ie. run Intgerity checks.
thanks
Steve
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Thursday, June 25, 2009 2:28 AM
Points: 206,
Visits: 420
|
|
Steve Hindle (10/16/2008)
I am currently using Maintenace Plans to schedule jobs for User / System databases. Is it recommended to run each step at completely different times so there is no overlap. ie. run Intgerity checks.
thanks
Steve
Assuming your running 2005 with some form of service pack (RTM is not a good place to be), I would have two plans completely. You tend to want to do more with user databases the system. E.g., not to much point in running index rebuilds on system databases because they don’t really change.
It’s a bit my maintenance over head but I would do it that way.
And yes would definitely schedule jobs at different times. A clash probably wouldn’t cause to much bother but its good practice to separate. Makes it easier to read the server log to!
;)
Adam Zacks
-------------------------------------------
If you try to fail, and succeed, which have you done?
|
|
|
|
|
Valued Member
Group: General Forum Members
Last Login: Tuesday, June 16, 2009 9:55 AM
Points: 69,
Visits: 197
|
|
| Thanks for the confirmation. Yes I have separate system and user Maintenance Plans, with jobs scheduled to be run at different times.
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Thursday, June 25, 2009 2:28 AM
Points: 206,
Visits: 420
|
|
Hi there,
Just re-read your original question and realised my response ignored your question.
Rather then scheduling the different steps/parts to run at different time, use the progression/inheritance lines.
In that way you can control what sequence the individual tasks run in. Keep in mind that you don’t want to remove and old backup before the new one has succeeded.
I tend to stick the History cleanup out on its own and it runs independently.
Adam Zacks
-------------------------------------------
If you try to fail, and succeed, which have you done?
|
|
|
|
|
Valued Member
Group: General Forum Members
Last Login: Tuesday, June 16, 2009 9:55 AM
Points: 69,
Visits: 197
|
|
| By using progression/inheritance are you meaning have all the tasks in one subplan and use the Precedence contraints?
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Thursday, June 25, 2009 2:28 AM
Points: 206,
Visits: 420
|
|
Correct. There is no need to over complicate the plan (as long as its not to complex ie TSQL and other bespoke tasks).
I keep most of my plans to one step and use the inheritance lines to control flow.
There will most likely be those that disagree but mine i are quite straight forward installations and I find these easier to maintain.
Also means that its easier for others to read and maintain without screwing things up. ;)
Adam Zacks
-------------------------------------------
If you try to fail, and succeed, which have you done?
|
|
|
|
