DB File Space (rollup)

Microsoft.SQLServer.2008.DBFileGroup.DBFileSpaceMonitorRollUp (DependencyMonitor)

Monitors the space available in a Filegroup.

Knowledge Base article:

Summary

Monitors the space available in a Filegroup and on the media hosting the Filegroup. The space available on the media hosting the files is only included as a part of the space available, if auto grow is enabled for one of the files.

Causes

Unhealthy state is caused by low space available for this Filegroup. Low free space can be caused by:

Use the following link to view the performance data: DB Filegroup Free Space Performance Data

No Auto Grow

For a file that has no auto grow, free space would be the difference between the initial size for a file and the used space.

Auto Grow Enabled

With auto grow enabled, the available disk space is included as a part of the over free space. In addition to the difference between the file size and the used space, the free space for files with auto grow enabled would be the minimum of either the difference between the max size and the file size and the free space left on disk.

Low free space for database files that have auto grow could mean that the file is approaching the limits of the hosting logical drive. For files with auto grow enabled with a max size, low free space could also mean that the file is approaching the max size specified for a file.

The free space calculations also take into account that the file can also fail to grow if the growth amount of the file is greater than the amount left on disk, and that the file cannot grow if the difference between the max size and the current file size is less than the growth amount. In these situations, available free space left on disk is not included as a part of the free space, because we cannot grow any longer.

Resolutions

This issue may be resolved by either:

See SQL Server Books Online: Files and Filegroups Architecture

Overrideable Parameters

Name

Description

Default Value

Alert Priority

Defines Alert Priority.

Normal

Alert Severity

Defines Alert Severity.

MatchMonitorHealth

Enabled

Enables or disables the workflow.

Yes

Generates Alerts

Defines whether the workflow generates an Alert.

Yes

Element properties:

TargetMicrosoft.SQLServer.2008.DBFileGroup
Parent MonitorMicrosoft.SQLServer.2008.Database.DBFileGroupSpaceMonitor
AlgorithmBestOf
Source MonitorMicrosoft.SQLServer.2008.Monitoring.DBFileSpaceMonitor
RelationshipMicrosoft.SQLServer.2008.DBFileGroupHostsDBFile
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
RemotableTrue
AccessibilityPublic
Alert Message
Filegroup is running out of space
The Filegroup «{0}» for the database "{1}" in SQL instance "{2}" on computer "{3}" is running out of space. See knowledge section for more details.

Source Code:

<DependencyMonitor ID="Microsoft.SQLServer.2008.DBFileGroup.DBFileSpaceMonitorRollUp" Accessibility="Public" Enabled="true" Target="SQL2008Core!Microsoft.SQLServer.2008.DBFileGroup" ParentMonitorID="Microsoft.SQLServer.2008.Database.DBFileGroupSpaceMonitor" Remotable="true" Priority="Normal" RelationshipType="SQL2008Core!Microsoft.SQLServer.2008.DBFileGroupHostsDBFile" MemberMonitor="Microsoft.SQLServer.2008.Monitoring.DBFileSpaceMonitor">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.2008.DBFileGroup.DBFileSpaceMonitorRollUp.AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="SQL!Microsoft.SQLServer.DBFileGroup"]/GroupName$</AlertParameter1>
<AlertParameter2>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.Database"]/DatabaseName$</AlertParameter2>
<AlertParameter3>$Target/Host/Host/Property[Type="SQL!Microsoft.SQLServer.ServerRole"]/InstanceName$</AlertParameter3>
<AlertParameter4>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter4>
</AlertParameters>
</AlertSettings>
<Algorithm>BestOf</Algorithm>
<MemberUnAvailable>Error</MemberUnAvailable>
</DependencyMonitor>