Monitors for a significant decrease of ROWS data free space over a number of sample periods. Note that this monitor is disabled by default. Use overrides to enable it when necessary.
Knowledge Base article:
Summary
Monitors for a significant decrease of ROWS data free space over a number of sample periods. A rapid large change in value could indicate a problem.
Causes
An unhealthy state is caused by a large change in ROWS data free space over a set number of sample periods. This can be caused by:
A large autogrowth setting for a file set to autogrowth.
A fast growing file that consumed a large amount of free space within a short period.
A foreign object or file consumed a large amount of free space hosted on the same disk as this file
Use the following link to view the performance data: Database Performance Data
This monitor aggregates the space available for each ROWS data file within a Filegroup 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.
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.
Resolutions
This issue may be resolved by either:
Decreasing the growth amount for files with autogrowth
Modifying the thresholds for this monitor to suit the workload
Alternatively if space percentage change is not a concern for the database:
Disable this monitor for this specific database or all databases
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 exceeds this threshold. Being between this threshold and the warning threshold (inclusive) will result in the monitor being in a warning state.
45
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
Number of samples
Indicates how many times a measured value should breach a threshold before the state is changed.
5
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
Timeout for query execution (seconds)
The workflow will fail and register an event, if the query execution takes longer than the specified period.
60
Timeout for database connection (seconds)
The workflow will fail and register an event, if it cannot access the database during the specified period.
15
Warning Threshold
Warning threshold. Exceeding this threshold will result in the monitor changing to at least a warning state.
Home
ENU