What’s the issue?
Every SQL Server database file (data and log) has an autogrowth setting that controls how the file expands when it runs out of space. Autogrowth can be configured as either a percentage of the current file size or a fixed amount in megabytes. The default for new databases was historically been 1 MB for data files and 10 percent for log files, both of which are problematic. This finding flags any database file configured for percentage-based growth or fixed growth smaller than 64 MB.
Why is this a problem?
Small autogrowth increments cause frequent growth events, and each growth event briefly pauses database activity while the file is extended, which can cause query timeouts on busy systems. Percentage based growth is even worse because as the file gets larger, each growth event also gets larger and takes longer, creating unpredictable pauses. Frequent log file growth also produces an excessive number of virtual log files (VLFs) inside the log, which slows down recovery, log backups, and database startup.
Without Instant File Initialization enabled, every data file growth must be zeroed out first, multiplying the impact. Together, these issues turn a routine background operation into a recurring source of performance problems and unpredictable behavior.
What should you do about this?
Identify affected files by querying sys.master_files and reviewing the is_percent_growth and growth columns. For each file, change the autogrowth setting to a fixed value sized appropriately for the database’s growth pattern. Common starting points are 64 MB for data and log files, though large or rapidly growing databases should use larger increments. Apply the change with ALTER DATABASE [DatabaseName] MODIFY FILE (NAME = N’LogicalFileName’, FILEGROWTH = 64MB);. For log files specifically, also review the existing VLF count using DBCC LOGINFO and rebuild the log if there are excessive VLFs (generally more than a few hundred), by shrinking the log down and growing it back in larger chunks.
Ensure Instant File Initialization is enabled so data file growth is fast. Beyond fixing autogrowth settings, the better long term practice is to size data and log files proactively based on expected growth so autogrowth events become rare exceptions rather than routine occurrences.