Re: SQL 2005 SSAS - Cube processing fails due to memory error when more than one SSAS database exists (even when not part of the processing)

how many rows do you have?
do you use x64 or x32 servers? (I think x32)

do you have only SSAS installed on the server?

if you have other applications installed, then switch to an x64 OS and SQL Server install. My experience is bad if an x32 server share multiple application with SSAS installed.

also remove any unused cubes an database deployed in SSAS. This consume some memory for nothing. And reduce the number of unused attributes in the dimensions.


"JM" <john.murret@xxxxxxxxx> wrote in message news:4f0ea8a4-2be3-4e1c-bf89-0b627301507e@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Server Config:

-Xeon 3.60GHz

-8 GB RAM

-Windows Server 2003 R2 Enterprise SP2

-SQL Server 2005 Standard Edition SP2 Version 9.00.3050.00

-3GB BOOT.ini switch enabled



Issue:

-The processing of our Sales cube in our Production database (SSAS)
fails with Memory Error.



Normal process:

- Successfully process all dimensions in Production DB (SSAS)

- Restart SSAS service to clear memory

- Process Sales Cube in Production DB (SSAS)



Events related to the beginning of this failure:



For 2 weeks, this would fail every time our ETL would run. Then 2
weeks ago, we deleted our Development DB (SSAS) that was restored from
a backup of the Production DB.



Once that database was deleted, the processing of Sales Cube in
Production DB was successful every time for 2 weeks.



Last week, we restored the Development DB (SSAS) from a backup of the
Production DB. Now, when we try to process Sales Cube in Production
DB, it fails every time.



As you can see above, we restart the service before processing Sales
Cube in Production DB. Also, this is the only object that we try to
process. We never even reference of affect Development DB.



Somehow, the presence of this 2nd SSAS database causes our processing
to fail even though we never try to do anything with it. It's mere
presence on the SSAS instance is causing our processing on Sales Cube
in Production DB to fail.



My questions are:

- Since it is restored from a back up of Production DB, could
Development DB actually be getting processed as well when we specify
to process Production DB...i.e., they are sharing an object link so
that when we specify to process only one, it processes both?

- Is there any memory allocation that happens just because an SSAS
database exists? for example, if no one is querying it and it is not
processing, is it eating up lots of memory?



If you have any other thoughts which have a solution besides "put the
2nd SSAS database on a separate machine", please let me know. Thanks
so much in advance. -John

.

Relevant Pages
Loading