Hello everybody,

does anyone know what is the best practice for setting *.mdf autogrowth
parameter?
Database is now about 4GB big and shold be bigger for about 200MB every
year.

If I put 10% is that correct?

Regards and thanks in advice

On Wed, 20 Oct 2010 09:22:13 +0200, "m" <miroslavsi (AT) gmail (DOT) com> wrote:

The general answer is that no-one likes autogrowth. It does it too
late. (i.e. when the database is full) rather than keeping free space
available.

There are a number of scripts out there to automatically resize the
database

I use the one from here
http://www.sqlservercentral.com/scripts/T-SQL/67185/

(SQL 2005)

Here's the SQL 2000 version

http://www.sqlservercentral.com/scripts/T-SQL/67186/

This creates a stored procedure to grow the databases, and you then
schedule this with Agent to run every week or month or whatever, it
just tops off the database file when necessary.

Iain

On Wed, 20 Oct 2010 09:22:13 +0200, m wrote:

In addition to the reply by Iain Sharp - the best practice is to
manually grow the databases during off hours, and in large chunks at
once. Repeatedly growing in small chunks increases fragmentation.

--
Hugo Kornelis, SQL Server MVP
My SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis

m (miroslavsi (AT) gmail (DOT) com) writes:
In that case, make the database 6 GB, and you don't have to worry about
growth for a decade. Well, you should probably monitor the space usage,
as trends could change.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx