RE: Analysis Service Shut Down during process - Out of Memory

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Thanks dshroyer! I have not heard of this approach.

The other thing I tried was to set ThreadPool \ Process \ MaxThreads to 150,
ThreadPool \ Process \ MinThreads to 8, and CoordinatorExecutionMode to -16.
I tried this approach and stil got the same "Out of Memory" error. However,
at least SSAS didn't shut down. I found this approach as my SSAS was hanging
at the end of processing and would not stop. I had to manually shut down the
SSAS service.

Jason

"dshroyer" wrote:

You might try changing the low memory limit property before processing. This
will cause SSAS to dump memory sooner. You'll want to change the setting to
40 ro 45 and then back to the default of 75 after the process completes.

Below is an example of the XMLA script that will change the property.


<Alter AllowCreate="true" ObjectExpansion="ObjectProperties"
xmlns="http://schemas.microsoft.com/analysisservices/2003/engine";>
<Object />
<ObjectDefinition>
<Server xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:ddl2="http://schemas.microsoft.com/analysisservices/2003/engine/2";
xmlns:ddl2_2="http://schemas.microsoft.com/analysisservices/2003/engine/2/2";>
<ID>SERVERNAME</ID>
<Name>SERVERNAME</Name>
<ServerProperties>
<ServerProperty>
<Name>Memory\LowMemoryLimit</Name>
<Value>40</Value>
</ServerProperty>
</ServerProperties>
</Server>
</ObjectDefinition>
</Alter>


"Jason" wrote:

Hello, my cube was almost done processing after 3hrs of full processing.
Then all the sudden my SSAS shut down. The error msg in the SQL Agent job
history was something like "communication link forcibly closed". I looked at
the application event log on the SSAS, and I noticed an "Out of Memory" error
on the MSOlapService.

I have 8Gb of mem on a Win2k3 svr. 100M row table is partitioned into 12
monthly partitions.

Can someone please tell me how to fix the Out of Memory issue without having
to put more memory on the server?

Are there certain counters I need to add to permon to determine exactly how
much memory I need to add to the server?

Thanks,
Jason
.



Relevant Pages

  • SSAS 2008 not using available memory
    ... SQL Server was configured to ... We continually observed the server using 90-99% percent of the memory. ... SQL is using 32GB and SSAS ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS 2005 perform worse performance that 2000
    ... sql server and leave all SSAS memory options default because MS does not ... recomend change memory settings. ... queries from cache filtered 500000, Total queries from cache direct 30000. ... read abouty this option I need to set only for ROLAP partitions. ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS 2008 not using available memory
    ... If you start Performance Monitor and look at the Memory Limit High KB and Memory Limit Low KB values, are they set correctly or do they appear to be arbitrarily low? ... The server will start to clean memory at the mid-point between Low and High memory limit and trend over time towards this mid-point. ... We have SSAS 2008 and SQL Server 2008 installed on a Windows 2008 Server ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS 2008 not using available memory
    ... The configuration has been in place for several days and the server has been ... this load cause SSAS consume 30GB of memory. ... As you can see we are nowhere near the mid-point for SSAS and have ... SSMS using the server properties. ...
    (microsoft.public.sqlserver.olap)
  • Re: SSAS 2008 not using available memory
    ... Cleaner Current Price 0.000 ... all we did was add physical memory. ... As you can see we are nowhere near the mid-point for SSAS and have ... The server will start to ...
    (microsoft.public.sqlserver.olap)