September 16, 2009 at 6:19 am
The Gurus,
Could someone tell me the right (best) order for maintenance plan tasks?
1. Backup database task
2. Check database integrity task
3. Maintenance cleanup taks
4. ...
5. ...
Many thanks in advance.
Regards,
Sahoong.
September 17, 2009 at 12:45 pm
Check out Ola's Maintenance Script. I think it is better than MS maintenance plans.
September 17, 2009 at 1:09 pm
If you want to do a maintenance task, I'd check integrity first (if you have time), then backup, then maintenance cleanup, then history cleanup.
If you can't do integrity every night, do it once a week at least.
September 18, 2009 at 3:59 am
Many thanks to you and Steve Jones for your response.
Regards.
September 18, 2009 at 4:06 am
Steve Jones - Editor (9/17/2009)
If you want to do a maintenance task, I'd check integrity first (if you have time), then backup, then maintenance cleanup, then history cleanup.If you can't do integrity every night, do it once a week at least.
100% agree!
sahoong,
Would also like to mentione that sometimes your maintenance plan schedule and its steps differ from how much busy your database is and what is the size of yoru database.
September 18, 2009 at 11:51 am
You may want to consider appropriate timing for your transaction log backups with respect to your full backups. Keep in mind the transaction log bakup is useful only in terms of the preceeding full backup. So for example lets say you take a transaction log backup at 22:00 and then your regular Full backup happens at 23:00. What happens if the user calls and says the database needs to be restored as of 22:30. You can't do it. You can give then 22:00 by using the previous Full and applying logs or you can give then a restore back to 23:00. If its currently 23:30 you could even give then a restore as of 22:25 by running another transaction log backup immediately and using the STOPAT parameter when doing the restore.
Now if you took a transaction log backup immediately before your Full BACKUP at 23:00 you would have no problem restoring to 22:30. So I recommend that somehow you schedule your transaction log backup to occur imediately prior to your Full backup, the every X hours as you see fit. This could also be accomplished by scheduling your transaction log backup at whatever time you want and then just define your Full backup job to first run a transaction log backup then to run the Full backup.
Just a thought.
Francis
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply