Thursday 20 September 2012

SSAS 2012 Cube Processing Consuming all memory


Server becomes unresponsive while processing the Cube

If your server is becoming unresponsive and other applications on the SSAS Server are not able to work while processing the Cube follow the following steps:
 

  1. See if the SSAS server also is your database server.
    1. Limit the memory of the Database sever to minimum (for a 16GB box you can limit it to 2.5GB).

  1. Separate the SSIS instance from the SSAS Instance.
    1. If you can't do that then make sure that no SSIS Job is getting executed while processing the Cube.

  1. Do your memory allocation such that any point in time OS should get at least 2-3 GB of memory of its routine operations.
    1. Restrict the TotalMemoryLimit of SSAS intance to 60(for a 16 GB server it will be close to 9.6GB). This is the Percentage of the total memory SSAS engine will use while execution.
    2. Restrict the LowMemoryLimt to 40(for a 16 GB server it will be close to 6.4GB).
    3. Restrict the VertipaqMemoryLimit to 50 (for a 16 GB server it will be close to 8GB)

No comments:

Post a Comment