The monitor reports a warning when memory allocations by the SSAS instance surpass the configured WarningThreshold, expressed as a percentage of the TotalMemoryLimit setting for the SSAS instance. The monitor issues a critical alert when these allocations surpass the configured CriticalThreshold.
Knowledge Base article:
Summary
The monitor reports a warning when memory allocations by the SSAS instance surpass the configured WarningThreshold, expressed as a percentage of the TotalMemoryLimit setting for the SSAS instance. The monitor issues a critical alert when these allocations surpass the configured CriticalThreshold.
Causes
SSAS can approach or exceed the TotalMemoryLimit setting under some circumstances. In some cases, a single operation requires memory beyond these limit, and despite the server’s best effort to clear memory from other less immediate tasks, allocations may sometimes necessarily exceed the configured limits, or else the operations must be forced to fail.
This can occur when processing large dimensions or fact data, particularly if there exist attributes with data types consuming large amounts of space (e.g. long strings, binary data, etc.), or if the dimension contains numerous members. Also, queries executed on the server may cover very large spaces, particularly if multiple dimensions are being cross joined or significant calculations are required to derive results for cells not aggregated previously by a wise administrator, or simply not possible to aggregate in advance.
Resolutions
When memory limits for a server are exceeded, there are numerous approaches administrators may use to remediate the issue. After considering the underlying activity causing the memory usage, requirements for workload on the server, available resources, and other factors, as well as reviewing and considering the SSAS Multidimensional Performance Guide thoroughly, or consulting Microsoft support, as necessary, any of the following approaches may be used to address the issue:
Identify the session(s) responsible for the most significant memory allocations, and manually terminate them.
Identify the session(s) responsible for the most significant memory allocations, and address them on a case-by-case basis to reschedule processing jobs or reports, pre-allocate with cache warming queries during times of lower utilization, or by designing specific aggregations in advance, to be built during processing, and hence reducing memory consumption by user queries subsequently.
Increase physical memory on the host computer.
Decrease memory usage by other processes on the host computer, such as instances of the SQL Server relational database engine or other instances of SSAS.
Increase the TotalMemoryLimit or configured thresholds for the alert to avoid the condition.
Disable the monitor entirely if memory usage is not a concern on the server.
Current memory utilization for SSAS ({3} GB) surpasses the configured threshold, expressed as a percentage of the TotalMemoryLimit setting for the instance.
Total memory on the server: {2} GB
Total memory usage: {5} GB
Memory used by non-SSAS processes: {4} GB
Memory used by SSAS: {3} GB
SSAS Memory Limit Low: {6} GB ({7}\%)
SSAS Memory Limit High: {0} GB ({8}\%)
Home
ENU