I have inherited a database from another site. It starts
out at approximately 10GB for the data file. If I run a
maintenance plan with the default settings for the
Optimizations the data file grows from 10GB to 17GB GB and
the log file grows from 255MB to 6 GB.

Anyone have any explanation why this grows so big?

I assume the maintenance reindexes the databases (reorganize data and index
pages on the second tab of the maintenance plan wizard) and the database
runs under the full recovery model, so all the reindexing operations are
logged.

--
Jacco Schalkwijk
SQL Server MVP


"Bill Holland" <hollandwl (AT) state (DOT) gov> wrote

The Optimization runs a DBREINDEX which is logged.
Another option is to consider DBCC INDEXDEFRAG. However, you
don't need to defrag indexes unless they are fragmented to
start with. The updated Books Online DBCC SHOWCONTIG topic
has a script which will defrag only where you actually have
some fragmentation.
You should read the following article for guidelines on
defragging:
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx.

-Sue

On Tue, 29 Jun 2004 03:07:13 -0700, "Bill Holland"
<hollandwl (AT) state (DOT) gov> wrote: