February 7, 2008 at 4:23 pm
I've been reading a lot about setting up maintenance plans today; books, articles, BOL...lots of reading.
But a few questions come to mind.
I have about 10 datasizes on a few servers that require backups and maintenance plans. Im working on implementing those as I write this.
Curious though; as I was working with the 'designer' part of the plan, I started to think what is the best approach to creating a plan?
Things I was wondering are:
What should be included in a maintenance plan?
--backup the database (obviously)
--check database integrity
--rebuild index
--reorganize index
--update statistics
should all of those be included on a routine maintenance plan?
Also, I am guessing it is ok to tie those all into one plan?
I was thinking of creating a plan that would include the following the this order:
-check database integrity
-update statistics
-reorganize index
-rebuild the indexes
-backup the database
I just want to make sure I do things correctly, since this going on production database boxes and I am pretty new to all this.
Appreciate it.
Jas
February 7, 2008 at 5:02 pm
My advice is to create a backup plan as per the business needs may be full db backup every day and that other backups as they need. then you can schedule your other maintenance jobs to run on the week ends so that they don't affect the system performance.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
February 8, 2008 at 11:54 am
I would also add that when it comes to re-indexing it is best to test the level of fragmentation in the individual indexes and perform index defrags or index rebuilds accordingly versus using the maintenance plan to run a blanked reindex job against all indexes.
- Tim Ford, SQL Server MVPhttp://www.sqlcruise.comhttp://www.thesqlagentman.com http://www.linkedin.com/in/timothyford
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply