Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
donpolix
Yak Posting Veteran
97 Posts |
 Posted - 2008-01-30 : 11:35:07
|
| Hi guys, just wanna hear your opinions on which would be better for maintenance plans.Build separate schedules for each task (integrity checks, optimizations, backups)? Or a single schedule for the entire plan?Thanks!Donn Policarpio |
|
|
chwanhun
Starting Member
22 Posts |
Posted - 2008-01-30 : 14:51:04
|
| I'm not totally sure how Maintenance plans work but, I would do a single schedule for each plan. This way if one of them fails, the others will still run. So for example, if the integrity check fails, the backup will still run. |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-01-30 : 18:46:47
|
| depends on how big is the database and index ,optimizations consumes time if table is big. |
|
|
|
donpolix
Yak Posting Veteran
97 Posts |
Posted - 2008-01-31 : 19:28:45
|
quote:
Originally posted by chwanhun
I'm not totally sure how Maintenance plans work but, I would do a single schedule for each plan. This way if one of them fails, the others will still run. So for example, if the integrity check fails, the backup will still run.
Thanks.In a single plan, you can still continue to the next task regardless of the result of the previous one using On Completion. On the other hand, doing separate scheds for each task, one might execute longer as expected and may overlap with other task's schedule.Donn Policarpio |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-01-31 : 23:24:59
|
| Depends on how many tasks and how often you need to do, you don't want to do full backup and log backup in single schedule for instance. |
|
|
|
|
|
|
|
|
Maintenance plan: separate or single schedules