Wednesday, March 21, 2012

FileGrowth changes after the execution of DBCC SHRINKDATABASE

Using sp_helpfile to my database (SQL Server 2005,SP1) I get the following results

Data File size=5103616 KB, maxsize=Unlimited, growth=204800 KB

Log File size=504 KB, maxsize=Unlimited, growth=204800 KB

I execute a maintenance plan having only a Shrink Database Task. This task produces the following t-sql

USE [myDB]
GO
DBCC SHRINKDATABASE(N'myDB', 10, TRUNCATEONLY)

Now, executing sp_helpfile I get the same result but if i restart sql server I realize that the Data file's growth changes to growth=25600% (there is no other action or job using my Database)

What could cause this?

Thanks in advance

Probably your transaction log file still contains uncommitted transactions. Execute a BACKUP LOG dbname WITH TRUNCATE_ONLY before you run the shrink command|||

Thank you for your answer but it didnt work :(

I execute backup log , I execute sp_helpfile and the data file's growth has the normal size. But when I restart SQL Server , the data file's growth becomes equal to 102400%

I cant really undestand what may cause this ....

Any ideas?

|||

This problem disappears if I choose growth=10% and not growth in MB

Restarting SQL Server , the growth remains 10%.

It seems that the growth in MB makes the problems. But I don't prefer to have growth in %.

Any ideas?

No comments:

Post a Comment