• Management Pack:  SQL Server
  • MP Version:  6.1
  • Released:  8/5/2010
  • Publisher:  Microsoft

DB File Space Monitor

  • ID:  Microsoft.SQLServer.2005.Monitoring.DBFileSpaceMonitor
  • Description:  Monitors the space available on a database file and on the media hosting the file in percentage terms.
  • Target:  SQL Server 2005 DB File
  • Enabled:  Yes

Operational States

Name State Description
Under Lower Threshold Error  
Between Lower and Upper Threshold Warning  
Above Upper Threshold Success  

Overridable Parameters

Parameter Name Default Value Description Override
Interval (sec) 900  
Synchronization Time    
Lower Threshold 10  
Upper Threshold 20  
Timeout (sec) 300  

Run As Profiles


Monitor Knowledgebase


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


An unhealthy state is caused by having low available for this file. 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 link to view the performance data: DB File Free Space Performance Data (%)

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

With auto grow enabled, the available disk space is included as part of the over available space. 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.


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 file group available 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 Filegroups Architecture

External References
This monitor does not contain any external references.

See Also for SQL Server Management Pack


Posted : Wednesday, March 21, 2012 1:39:09 PM(UTC)

Comments: 2

You should keep in mind that file-level monitoring works rather good now but in case of extremely loaded server (e.g. which works all the time about 99% of CPU) or you have really huge number of DBs and files (e.g. 500 databases consist of 1000-2000 files) - you should think about Database-level space monitoring.