|
|
|
|
|
Why does the SQL Server
Database Maintenance Wizard warn about using it on databases greater than 400Mb in size? The DMW sets up an "aggressive" set of dbcc and other healthchecks. On "large" databases this sort of housekeeping can take a long time, so you might not want to do everything every night. In this situation you might want to set up your own maintenance tasks, perhaps only running checkdb once per week, and newalloc every night, with index rebuilds once a month or so. MS's choice of "large" is 400Mb - probably a bit low given the speed of current cpu's/disks etc. The answer is, if you're happy with the time it takes to run the DMW generated tasks, then stick with it, regardless of your database size. |
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.