Monitors the space available in the database and on the media hosting the database in percentage terms. This monitor does not count free space for FILESTREAM and Memory-Optimized Data file groups. Note: This monitor is disabled by default. Please use overrides to enable it when necessary.
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 autogrowth is enabled for at least one of the files. Note that this monitor does not count free space for FILESTREAM and In-Memory OLTP Data filegroups.
An unhealthy state is caused by having low free space across FILESTREAM database files. Low free space can be caused by:
Inadequate file configuration settings (size, max size, autogrowth, 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 Autogrowth
For a file that has no autogrowth, free space would be the difference between the initial size for a file and the used space.
Autogrowth Enabled
For a file with autogrowth, free space would be calculated as the available free disk space that can be used for extension of the database file with respect to the last autogrowth step size. Because the last autogrowth step size can exceed disk capacity, calculations of the free space are performed as a function of autogrowth step values. For example, if autogrowth is set to 20% on the disk, the size of which is 10 GB and the current database size is 9 GB, the free space will be displayed as 0 GB because the last gigabyte cannot be used.
Low free space for database files that have autogrowth could mean that the file is approaching the limits of the hosting logical drive. For files with autogrowth 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 part of the free space because we cannot grow any longer.
This issue may be resolved by either:
Increasing the allocated size for a file or all files within a Filegroup if autogrowth is disabled
Increasing the max size value for a file if autogrowth is enabled
Enabling autogrowth 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 Filegroup or all Filegroups
See SQL Server Books Online: Files and Filegroups Architecture
Name | Description | Default Value |
Alert Priority | Defines Alert Priority. | High |
Alert Severity | Defines Alert Severity. | MatchMonitorHealth |
Azure Maximum File Size (MB) | The maximum size of data file stored in Azure BLOB Storage. The workflow will consider this value as a maximum storage capacity for each file. | 1048576 |
Critical Threshold | The monitor will change its state to Critical if the value drops below this threshold. Being between this threshold and the warning threshold (inclusive) will result in the monitor being in a warning state. | 10 |
Enabled | Enables or disables the workflow. | No |
Generates Alerts | Defines whether the workflow generates an Alert. | Yes |
Interval (seconds) | The recurring interval of time in seconds in which to run the workflow. | 900 |
Synchronization Time | The synchronization time specified by using a 24-hour format. May be omitted. |
|
Timeout (seconds) | Specifies the time the workflow is allowed to run before being closed and marked as failed. | 300 |
Warning Threshold | The monitor will change its state to Warning if the value drops below this threshold. | 20 |
| Target | Microsoft.SQLServer.Windows.Database | ||
| Parent Monitor | Microsoft.SQLServer.Windows.Rollup.Database.DBSpace | ||
| Category | PerformanceHealth | ||
| Enabled | False | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | High | ||
| Alert Auto Resolve | True | ||
| Monitor Type | Microsoft.SQLServer.Windows.MonitorType.Database.DBSize | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
<UnitMonitor ID="Microsoft.SQLServer.Windows.Monitor.Database.FilestreamSizePercent" Accessibility="Public" Enabled="false" Target="SqlDiscW!Microsoft.SQLServer.Windows.Database" ParentMonitorID="Microsoft.SQLServer.Windows.Rollup.Database.DBSpace" Remotable="true" Priority="Normal" TypeID="Microsoft.SQLServer.Windows.MonitorType.Database.DBSize" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.Windows.Monitor.Database.FilestreamSizePercent.AlertMessage">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>High</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.Database"]/DatabaseName$</AlertParameter1>
<AlertParameter2>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</AlertParameter2>
<AlertParameter3>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</AlertParameter3>
<AlertParameter4>$Data/Context/Property[@Name='FdFreeSpaceMB']$</AlertParameter4>
<AlertParameter5>$Data/Context/Property[@Name='FdFreeSpacePercent']$</AlertParameter5>
</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>
<MachineName>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/MachineName$</MachineName>
<NetbiosComputerName>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/NetbiosComputerName$</NetbiosComputerName>
<InstanceName>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/InstanceName$</InstanceName>
<DatabaseName>$Target/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.Database"]/DatabaseName$</DatabaseName>
<AzureMaxFileSizeMB>1048576</AzureMaxFileSizeMB>
<ValuePropertyName>FdFreeSpacePercentMon</ValuePropertyName>
<Threshold1>10</Threshold1>
<Threshold2>20</Threshold2>
<ConnectionString>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/ConnectionString$</ConnectionString>
<InstanceVersion>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Version$</InstanceVersion>
<InstanceEdition>$Target/Host/Property[Type="SqlCoreLib!Microsoft.SQLServer.Core.DBEngine"]/Edition$</InstanceEdition>
<MonitoringType>$Target/Host/Property[Type="SqlDiscW!Microsoft.SQLServer.Windows.DBEngine"]/MonitoringType$</MonitoringType>
<SqlTimeoutSeconds>15</SqlTimeoutSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
</Configuration>
</UnitMonitor>