Analysis 2005 Cube Processing in 64-Bit Environment

I have problems with processing cubes on AS2005. I get this error message while processing:

Memory error: Allocation failure: Not enough storage is available to process this command. Error in the OLAP storage engine.

This machine has 6GB of memory and once it hits 3.5GB the processing stops. AWE is turned on.

I would appreciate, if anyone can help on this.

Thanks,

Gopal

Analysis Services is not AWE aware. So it can only use 2GB on a 32bit box (3GB if you have /3GB switch in boot.ini). Looks like the processing operation is running out of memory.

What are the number and sizes of dimension and partition tables? Do you have aggregations? Look at the processing log (in the process dialog) and find out what is the operation that causes out of memory - dimension processing, partition processing, building aggregations, etc.

This could also happen due to excessive parallelism. Try processing the dimensions and partitions individually.

|||

Thanks for your reply.

I managed to process the partitions and dimensions individually. That worked.

Gopal

|||

Hi.

Just a short question:

Is it really true that SSAS can use only 2GB RAM on a 32bit system? The technical reference for SQL Server 2005 Standard and Enterprise states that SQL Server can use the amount of RAM supported by the operating system which is 4GB for a Server 2003 Standard edition and 32GB for a Server 2003 Enterprise edition, both on 32bit systems. Does this apply only to the SQL Server Database Engine then and not the Analysis Services Server?

Regards

Kjetil

T.K. Anand wrote:

Analysis Services is not AWE aware. So it can only use 2GB on a 32bit box (3GB if you have /3GB switch in boot.ini). Looks like the processing operation is running out of memory.

What are the number and sizes of dimension and partition tables? Do you have aggregations? Look at the processing log (in the process dialog) and find out what is the operation that causes out of memory - dimension processing, partition processing, building aggregations, etc.

This could also happen due to excessive parallelism. Try processing the dimensions and partitions individually.

|||

In the 64-bit versions of Analysis Services...has this memory use limit been removed?

...cordell...

|||Yes - 64bit version doesn't have these limitations.

An error 1059 - (The Service did not Start due to a logon failure)

I installed SQL Server on my PC and it has been running fine for a few
months. Now I cannot start it but get this message:
----
--
An error 1059 - (The Service did not Start due to a logon failure) occurred
while performing this Service Operation on the MSSLQServer)
----
--
I recently changed by network password; Is there something that has to be
done to SQL Server when this is done ?It sounds like the services are running under your windows
account. If that's the case, you need to change the password
for the service accounts if they are the same as yours.
Looks like this is SQL Server 2005 so you can use the SQL
Server Configuration Manager to change the password for the
services.
-Sue
On Thu, 27 Jul 2006 12:19:02 -0700, rmcompute
<rmcompute@.discussions.microsoft.com> wrote:

>I installed SQL Server on my PC and it has been running fine for a few
>months. Now I cannot start it but get this message:
>----
--
>An error 1059 - (The Service did not Start due to a logon failure) occurred
>while performing this Service Operation on the MSSLQServer)
>----
--
>I recently changed by network password; Is there something that has to be
>done to SQL Server when this is done ?