DB Total Space

Microsoft.SQLServer.2005.Database.DBSizePercentMonitor (UnitMonitor)

Monitors the space available in the database and on the media hosting the database in percentage terms.

Knowledge Base article:

Summary

Monitors the space available on the database and on the media hosting the database. The space available on the media hosting the database is only included as part of the space available if auto grow is enabled for at least one of the files.

Causes

An unhealthy state is caused by having low available space across all database files. Low available space can be caused by:

Inadequate file configuration settings (size, max size, auto grow, etc.)
Inadequate space left on media

Use the following links to view the performance data: Database Performance Data

This monitor aggregates the space available for each file within a database depending on each file’s configuration:

No Auto Grow

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

Auto Grow Enabled

In addition to the difference between the file size and the used space, the available 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 available 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 available space could also mean that the file is approaching the max size specified for a file.

The available 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 part of the available space because we cannot grow any longer.

Resolutions

This issue may be resolved by either:

Increasing the allocated size for a file or all files within a file group if auto grow is disabled
Increasing the max size value for a file if auto grow is enabled
Enabling auto grow for at least one file
Moving files to another drive with more free space if growth space is limited
Modifying the thresholds for this monitor to suit the workload
Alternatively if total DB space is not a concern for the database:
- Disable this monitor for this specific file group or all file groups

See SQL Server Books Online: Files and File Groups Architecture

Element properties:

Target

Microsoft.SQLServer.2005.Database

Parent Monitor

Microsoft.SQLServer.2005.Database.DBSpaceMonitor

Category

PerformanceHealth

Enabled

False

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

High

Alert Auto Resolve

True

Monitor Type

Microsoft.SQLServer.2005.DBAndLogSizeMonitorType

Remotable

True

Accessibility

Public

Alert Message

Database Out of Space

The database "{0}" in SQL instance "{1}" on computer "{2}" is running out of space. See "alert context" tab for more details.

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.SQLServer.2005.Database.DBSizePercentMonitor" Accessibility="Public" Enabled="false" Target="SQL2005Core!Microsoft.SQLServer.2005.Database" ParentMonitorID="Microsoft.SQLServer.2005.Database.DBSpaceMonitor" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.2005.DBAndLogSizeMonitorType" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SQLServer.2005.Database.DBSizePercentMonitor.AlertMessage">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>High</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="SQL!Microsoft.SQLServer.Database"]/DatabaseName$</AlertParameter1>

      <AlertParameter2>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.ServerRole"]/InstanceName$</AlertParameter2>

      <AlertParameter3>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</AlertParameter3>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UnderThreshold1" MonitorTypeStateID="UnderThreshold1" HealthState="Error"/>

    <OperationalState ID="OverThreshold1UnderThreshold2" MonitorTypeStateID="OverThreshold1UnderThreshold2" HealthState="Warning"/>

    <OperationalState ID="OverThreshold2" MonitorTypeStateID="OverThreshold2" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>900</IntervalSeconds>

    <SyncTime/>

    <ConnectionString>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ConnectionString$</ConnectionString>

    <ServerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ServerName>

    <SqlInstanceName>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.ServerRole"]/InstanceName$</SqlInstanceName>

    <ObjectName>$Target/Host/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/PerformanceCounterObject$:Database</ObjectName>

    <CounterName>DB Total Free Space (%)</CounterName>

    <InstanceName>$Data/Property[@Name='Database']$</InstanceName>

    <DatabaseName>$Target/Property[Type="SQL!Microsoft.SQLServer.Database"]/DatabaseName$</DatabaseName>

    <Value>$Data/Property[@Name='DBFreeSpacePercent']$</Value>

    <Threshold1>10</Threshold1>

    <Threshold2>20</Threshold2>

    <TimeoutSeconds>300</TimeoutSeconds>

  </Configuration>

</UnitMonitor>