Monitors the space available in the database and on the media hosting the database in percentage terms. Note that this monitor does not count free space for FILESTREAM Filegroups.
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 a 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 Filegroups.
Causes
Unhealthy state is caused by low space free space across all database files. Low free space can be caused by:
Inadequate file configuration settings (size, max size, autogrowth, etc.)
Inadequate space left on the 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 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
In addition to the difference between the file size and the used space, the free space for files with autogrowth 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 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 a part of the free 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 Filegroup if autogrowth is disabled
Increasing the max size value for a file if autogrowth is enabled
Enabling autogrowth for a file that is almost completely filled
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
Home
ENU