Autogrowth values keep changing

Hi!

We have 2 dbs on our dw-server and the autogrowth values for both the data- and logfiles on both of these dbs changes about once a month. The data autogrowth value changes from 10megs to a percentage value between 3200 and 6400 and the log-file value changes from 10 percent to a percentage value between 3200 and 6400. Resulting in huge files and filling the drive.

What am I missing here?

BR John

The value does not change on its own. Someone/process must be changing this. Perhaps, you should turn on audit to see who's responsible.|||

Just did it. Created a trace with the SQL Profiler to catch the SQL Batch-events. Now we just have to wait it out...

John

|||

Not a helpful reply, it can and it does.

I have now experienced the same bug myself. SQL 2005 on x64, has been running okay for months. Last month the database jumped from 3Gb to something like 60Gb, I found the autogrowth setting had switched from xxMB to 2048%. I thought I must have done this by mistake, so I shrank the DB and reset the autogrowth values.

This morning I log in, database is now 204GB and the autogrowth is set to 32768% !!! It stopped at 204Gb as there was no diskspace left. I've reset the autogrow again also set "maxsize" to 10GB.

This is definitely a bug and quite a serious one - it could quite easily take out an operational server by eating up disk space.

|||

Yes this is quite serious. It stops our ETL-process because of the drive being full.

Nothing in our tracelog yet...

|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

|||

Thanks!

BR John

|||

HowardRichards wrote:

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

b) it only manifests after the SQL server has been restarted

c) It has not been fixed in SP1 so here's hoping for SP2.

You won't see anything in the trace logs, it's a bug in the SQL engine. When it stores the settings for autogrow it does not correctly set one flag for percentage or non-percentage growth. If you restart SQL server you'll see the incorrect value/

Workarounds:

set Max size of the file to prevent the file from growing too large

turn off AutoGrow

use % based autogrow

I was not aware of this bug. Thanks for the correction.|||

It is a known bug, see http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=127177

a) it only seems to affect databases upgraded from SQL 2000

Regarding above comment ... I ran into that exact bug with a fresh install of SQL Server 2005 and SP1 on a completely new server. And it shut down my new 1 TB server!!!

Here's hoping SP2 does address it, as I have no interest in having my production servers needing that much coddling.

|||

Yes - we've been hit by this as well.

We had it set to autogrow by 250MB, until after a reboot where it changed to 32000%. Unfortunately we didn't spot this until we filled up our log file disk.

The annoying thing was that SQL Server Management Studio doesn't let you change back a value that has erroneously gone to 32000%, because it complains that the value exceeds the maximum allowed!!

So you need to change it using the alter database statement:

alter database dbname modify file (name = filename, filegrowth = 10%)

Roll on SP2...

|||

We just upgraded to SP2 for that reason (the fix is supposedly in there), but we're still unable to correct the value.

When attempting to change the value, the following error appears:

Value of ‘32768’ is not valid for “value’. “Value” should be between ‘Minimum’ and “Maximum’ Parameter name Value (System. Windows.Forms)

from the SQL Server 2005 SP2 fix list:

919611 (http://support.microsoft.com/kb/919611/)

FIX: The value of the automatic growth increment of a database file may be very large in SQL Server 2005 with Service Pack 1

Can anyone advise if running this statement will correct this issue permanently?

alter database MyTestDB
Modify File
(name=mytestdb, filegrowth = 500 mb)

Thanks!

|||Executing an alter database statement does not appear to prevent the behavior from resurfacing.