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 |
|
gangadhara.ms
Aged Yak Warrior
549 Posts |
 Posted - 2010-07-08 : 02:24:35
|
| Dear All,I am creating the maintance plan for the database backup of 5 databases in SQL server 2005 management studio.Actualy one set of databses needs to be scheduled at perticular time let say 12:00 PM and another set of database back up needs to be scheudled at 9:00 AM How can we do this in SQL 2005 in a single maintance plan ??Thanks,Gangadhar |
|
|
Peter99
Constraint Violating Yak Guru
498 Posts |
Posted - 2010-07-08 : 12:16:30
|
| create sub-plan for each task and then scheudle as per your requirement. |
 |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2010-07-08 : 21:51:32
|
| Agreed - use multiple sub-plans in a single maintenance plan. However, why do you have to use a single maintenance plan?BTW - you must be on SQL Server 2005 SP2+ (minimum 9.00.3054), if not - there are known issues with maintenance plans that could cause you problems. I would recommend installing at least SP3, and any additional CU's that apply in your environment. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-07-09 : 03:27:56
|
| A single plan would allow you to do "all databases" - so if you add one you won't accidentally forget to make a backup plan ...I'm sure there is a good reason for having split backup times! but it alludes me.Back them all up at 12:00 PM and then re-backup the 9:00AM one (with a retention time of 1 day, say, and exclude it [or the 12:00 PM version] from Tape Backup?) |
|
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2010-07-09 : 16:27:05
|
| Kristen - there is just one small little problem with using the All Databases option (which I've used before - don't get me wrong).Set that up on 5 databases, let it run for a few days - and then remove one of the databases. This will probably cause your maintenance plan to fail. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2010-07-09 : 17:38:49
|
| Yeah, the whole Maintenance Plan thing leaves a lot to be desired.Dunno about SQL 2005 (I haven't used maintenance plans since SQL 2000, and even back then I soon gave them up as a bad job) although the brief look I had in SQL 2005 things looked a lot better (I haven't even looked in SQL2008 ...) but in SQL 2000 if you set up a plan that did TLog backups, and included a database that was in SIMPLE Recovery Model, and some other states - Read Only perhaps, the plan failed ...Microsoft should really make a bullet proof, idiot proof, tool where the only questions you have to fill in are what folder you want to backups in, and how critical your data is. If you fail to even start the maintenance wizard it should start backing up to a default folder the moment SQL Server is installed ... |
|
|
|
|
|
|
|
|
Maintanace plan Creation in SQL 2005