The monitor reports a warning when the available disk space for SSAS tabular database storage folder drops below the 'Warning Threshold' setting expressed as percentage of the sum of the estimated database storage folder size and disk free space. The monitor reports a critical alert when the available space drops below the 'Critical Threshold' setting.
SSAS tabular database folder may grow over time, while the data is being continuously added from data sources. Therefore, the administrators would like to monitor the issue to be sure that there is always sufficient space left in the storage location for the database folder.
When the available disk space on the drive, where the database storage location is configured becomes too low, some failures may occur, delaying user’s queries, or affecting other applications as well, which share the same allocation of disk space. This appears to be unhealthy for the server. Consequently, it is important to monitor and ensure that a sufficient margin of available space remains, to avoid costly and time-consuming failures, which may incur production outages or delays. It is especially actual for databases that tend to grow quickly over time.
The resolution(s) for low available disk space depend upon the root causes, which must be investigated in each case when this issue occurs. The condition may be alleviated by any of the following potential approaches:
Remove data consuming disk space on the same drive with the DB storage folder.
Delete older partitions from the table.
The entire database may be moved by detaching it from the tabular instance, moving it, and reattaching to its new location.
Backup and restore procedures can help to move the data from one server to another, and to meet disk space requirements.
Increase the size of the logical drive on which the data folder is stored by means of Disk Manager.
Move the tabular data folder to a drive with more available disk space.
Modify the thresholds accordingly to suit the expected workload and conditions in the environment.
Disable the monitor entirely if disk space is not a concern for the instance.
Configure Server Properties in Analysis Services
TechNet documentation for SSAS Performance Counters
Name | Description | Default Value |
Critical Threshold (%) | Health state changes to 'Critical' when the 'Database Free Space (%)' performance counter drops below the threshold. | 5 |
Enabled | Enables or disables the workflow. | Yes |
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 (%) | Health state changes to 'Warning' if the 'Database Free Space (%)' performance counter drops below the threshold but is higher than 'Critical Threshold (%)'. | 10 |
Target | Microsoft.SQLServer.AnalysisServices.Windows.TabularDatabase | ||
Parent Monitor | System.Health.PerformanceState | ||
Category | PerformanceHealth | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.MonitorType.Database.FreeSpacePercent | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.Monitor.TabularDatabase.FreeSpace" Accessibility="Public" Enabled="true" Remotable="true" Priority="Normal" Target="SQLAS!Microsoft.SQLServer.AnalysisServices.Windows.TabularDatabase" TypeID="Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.MonitorType.Database.FreeSpacePercent" ParentMonitorID="SystemHealth!System.Health.PerformanceState" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.Monitor.TabularDatabase.DatabaseFreeSpace.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='UsedOnDatabaseDriveGB']$</AlertParameter1>
<AlertParameter2>$Data/Context/Property[@Name='TotalOnDatabaseDriveGB']$</AlertParameter2>
<AlertParameter3>$Target/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Database']/StorageLocation$</AlertParameter3>
<AlertParameter4>$Data/Context/Property[@Name='DatabaseDefaultForlderSizeGB']$</AlertParameter4>
<AlertParameter5>$Data/Context/Property[@Name='DatabaseFreeSpacePercent']$</AlertParameter5>
<AlertParameter6>$Data/Context/Property[@Name='DatabaseFreeSpaceGB']$</AlertParameter6>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="Success" MonitorTypeStateID="Above" HealthState="Success"/>
<OperationalState ID="Warning" MonitorTypeStateID="Between" HealthState="Warning"/>
<OperationalState ID="Error" MonitorTypeStateID="Below" HealthState="Error"/>
</OperationalStates>
<Configuration>
<ServiceName>$Target/Host/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Instance']/ServiceName$</ServiceName>
<DatabaseName>$Target/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Database']/DatabaseName$</DatabaseName>
<ConnectionString>$Target/Host/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Instance']/ConnectionString$</ConnectionString>
<DataDir>$Target/Host/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Instance']/DataDir$</DataDir>
<CriticalThreshold>5</CriticalThreshold>
<WarningThreshold>10</WarningThreshold>
<IntervalSeconds>900</IntervalSeconds>
<SyncTime/>
<TimeoutSeconds>300</TimeoutSeconds>
</Configuration>
</UnitMonitor>