The SQL Server database transaction log file does not grow by the configured file growth value

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

SYMPTOMS
The file growth value that is configured for the SQL Server database transaction log file is 4 gigabytes (GB) or multiples thereof (for example, 8 GB, 12 GB, and so on). However, the transaction log file does not grow by that value. Instead, the transaction log file grows by increments of only 250 KB kilobytes (KB). Additionally, you notice that there are lots of virtual log files in the transaction log file.
RESOLUTION

Cumulative update information

Microsoft SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for Microsoft SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2633145 Cumulative update package 11 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

Microsoft SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2633146 Cumulative update package 4 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
WORKAROUND
Change the file growth value for the SQL Server database transaction log file so that it is not exactly divisible by 4 GB.
MORE INFORMATION
You can use the following query to identify the SQL Server database transaction log file:

SELECT name FROM sys.master_files name
FROM sys.master_files WHERE database_id = DB_ID('<db name>')
AND type = 1
AND is_percent_growth = 0
AND growth % 524288 = 0

For more information about the products or tools that automatically check for file growth vales of 4 GB or multiples thereof on your instance of SQL Server and on the versions of the SQL Server product, see the following table:
Rule softwareRule titleRule descriptionProduct versions against which the rule is evaluated
System Center AdvisorSQL Server database file might not grow using the configured growth valueSystem Center Advisor determines whether the SQL Server database transaction log file is configured for a growth value of 4GB or multiples thereof and generates a warning if this is the case. Review the information that is provided in the "Information Collected" section of the warning, and make the necessary changes to the transaction log that is affected.SQL Server 2008
SQL Server 2008 R2

If you have large number of virtual log files in the transaction log, you will encounter long database recovery. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2028436 Certain database operations take a very long duration to complete or encounter errors when the transaction log has numerous virtual log files
Properties

Article ID: 2633151 - Last Review: 01/09/2012 22:13:00 - Revision: 2.0

Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2008 Enterprise, Microsoft SQL Server 2008 R2 Enterprise

  • KB2633151
Feedback