Spotlight on SQL Server 10.0.3 - Getting Started Guide

Databases - Dynamic Log File Growths Remaining Alarm

The Databases - Dynamic Log File Growths Remaining alarm becomes active when a non fixed size log file in any database is in danger of running out of space to grow. It is raised when a log file is almost full and the file cannot automatically grow enough to relieve the problem. Once a log file fills completely, depending on the state of other log files within the database, attempts to update data in that database may fail. This alarm takes into account the amount of free space currently on the disk that the file resides on.

The alarm is raised when the number of growths remaining, given the files growth settings and the amount of free disk space available, falls below a threshold.

This alarm can occur when a log file is filling up and:

• The file is approaching, or has reached, its MaxSize settings
• Is defined with AutoGrow=Yes
• There are a limited number of growths that can occur before an out of disk space condition occurs.

• View the Log Files page on the Databases drilldown. Check for files with AutoGrow=Yes. Files in danger of filling will have a low Free Pct figure.

To resolve this problem free up disk space on the disk that the log file resides on.

Tips:

• You can configure this alarm to ignore certain values. See "Configure an Alarm to Ignore Certain Values" (page 1) for more information.

• You can configure different alarm severities for specific log files. See "Configure Keyed Alarms" (page 1) for more information.

Examples

This alarm will be raised in the following circumstances:

• The log file is 95% full, and has been defined such that AutoGrow=Yes and given the current growth increment, the file has a limited number of growths remaining before it consumes all available disk space.

Related Topics

Spotlight on SQL Server Alarms (page 1)

Databases Drilldown (page 1)