Critical State Monitor

ID: Microsoft.SQLServerAppliance.PDW2.StorageInternal.VolumeStateMonitor.Critical
Description: This monitor detects if volume free space is in Critical state.
Target: SQL 2012 PDW Internal Volume Component
Enabled: Yes

Operational States

Monitor State	Message	Priority	Severity	Auto Resolution
Critical (Error)	Volume free space status is CRITICAL	Medium	Critical	Yes

Name

Default

Summary

Volume free space is critically low!

Causes

The current volume used disk space is beyond 97% of total capacity. This has many possible causes, including:

Databases growing too quickly. The databases could have too many tables, the tables could be growing faster than expected, or both.
Too many databases have been created and not removed.
External facing nodes are storing too many user files.

For example, the Landing Zone node might have too many large load files.

Resolutions

To diagnose the issue:

1) Use the PDW Admin Console or health DMVs to view the current values for the properties of the volume.

2) Review the disk space used on this volume. To calculate disk space used, subtract the value for volume_free_space from volume_size.

3) Use the volume_name to help determine if TEMPDB is an issue or to determine the distribution of user data stored on this volume.

4) Use DBCC SHOWSPACEUSED to determine which databases and tables are consuming the most space.

To resolve this issue:

1) Delete unnecessary databases or user files to reduce the data stored on the volume.

2) If log space is large then try using DBCC SHRINKLOG to reduce reserved space.

3) If the previous suggestions do not resolve the issue, contact Microsoft Support.

External References

This monitor does not contain any external references.