The monitor reports a warning, when the available free space for the default instance storage drops below Warning Threshold setting, expressed as percentage of the sum of estimated default storage folder (Data Directory) size and disk free space. The monitor reports a critical alert, when the available space drops below Critical Threshold. The monitor does not take into account databases or partitions located in folders other than the default storage folder (Data Directory).
The monitor reports a Warning, when the available free space for the default instance storage drops below Warning Threshold setting, expressed as percentage of the sum of estimated default storage folder (Data Directory) size and disk free space. The monitor reports a critical alert, when the available space drops below Critical Threshold. The monitor does not take into account databases or partitions located in folders other than the default storage folder (Data Directory).
When the available disk space as a percentage of the default storage folder (Data Directory) size for the instance becomes low, the database can become unhealthy, negatively affecting the performance or even causing a server fail. A common cause for this behavior may be fast growing database(s), but could also occur due to other data sharing available disk space with the default storage folder (Data Directory) for the instance.
The resolution(s) for disk space exhaustion 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:
Modify dimension design to remove unnecessary attributes, or limit the scope of members included from underlying data source to reduce dimension size.
Remove data consuming disk space on the same drive with SSAS instance default storage folder (Data Directory), but not part of SSAS instance itself.
Use Storage Location property to move cube partitions to non-default location with more free disk space.
Increase the size of the logical drive on which the data folder is stored with Disk Manager.
Copy the data folder in its entirety to a new drive with more available space, and then change the Data Directory setting for the instance in its msmdsrv.ini configuration to point to the new location, and restart the service to use the new location.
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, if AS Instance 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 AS Instance Free Space (%) performance counter drops below the threshold, but is still higher than Critical Threshold (%). | 10 |
Target | Microsoft.SQLServer.AnalysisServices.Windows.Instance | ||
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.Instance.FreeSpacePercent | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.Monitor.Instance.FreeSpace" Target="SQLAS!Microsoft.SQLServer.AnalysisServices.Windows.Instance" ParentMonitorID="SystemHealth!System.Health.PerformanceState" TypeID="Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.MonitorType.Instance.FreeSpacePercent" Accessibility="Public" Enabled="true" Remotable="true" Priority="Normal" ConfirmDelivery="false">
<Category>PerformanceHealth</Category>
<AlertSettings AlertMessage="Microsoft.SQLServer.AnalysisServices.Windows.Monitoring.Monitor.Instance.FreeSpace.AlertMessage">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Target/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Instance']/DataDir$</AlertParameter1>
<AlertParameter2>$Data/Context/Property[@Name='TotalOnInstanceDriveGB']$</AlertParameter2>
<AlertParameter3>$Data/Context/Property[@Name='InstanceDefaultForlderSizeGB']$</AlertParameter3>
<AlertParameter4>$Data/Context/Property[@Name='UsedOnInstanceDriveGB']$</AlertParameter4>
<AlertParameter5>$Data/Context/Property[@Name='ASInstanceFreeSpacePercent']$</AlertParameter5>
<AlertParameter6>$Data/Context/Property[@Name='ASInstanceFreeSpaceGB']$</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/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Instance']/ServiceName$</ServiceName>
<ConnectionString>$Target/Property[Type='ASCore!Microsoft.SQLServer.AnalysisServices.Core.Instance']/ConnectionString$</ConnectionString>
<DataDir>$Target/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>