Regular maintenance is critical for running a healthy database. Maintenance reduces file fragmentation and provides backups that may be stored off site. The order in which you complete the various maintenance steps has significant consequences. In this blog post, I'll give you my recommended maintenance sequence and explain the logic behind it.
So, what should always come first? The DBCC CHECKDB statement. The database must have integrity before you take any action. An image of a corrupted database is a poor starting point for a restore and recovery process.
The typical, pro forma advice (see
http://www.mssqltips.com/tip.asp?tip=1094) is to perform the following tasks in this order:
Check the database integrity.
Shrink the database.
Reorganize the index.
Rebuild the index.
Update the statistics.
Back up the database.
Clean up the history.
As you can see in the following screen shot, the SQL Server Maintenance Plan Wizard offers these tasks.
Read more:
PTC Windchill on SQL Server Posted via email from jasper22's posterous
Posts
0 comments:
Post a Comment