Dear all

I implemented a SQL Server 2005 Olap system on a 64bit box with 8GB RAM.
As far as I know msmdsrv.exe is the processname of SSAS.

This SSAS process uses only 1GB RAM - but there is 2GB of free memory. What
I think is strange is that the use of RAM stays with 1GB, even when more
people start queries against the cube. I wronly assumed that msmdsrv.exe
would claim more memory if the workload rises.

With SSIS the situation is different - the process sqlservr.exe gets as much
memory as possible. I had set a max. inside SQL Management Studio to prevent
this process gets all memory.

Seeing this situation I was asking myself, if I missed a memory configuration.

Running SSIS, SSAS and SSRS on one machine some memory assignments perhaps
could increase performance.

Do you have an idea what is happening here?

Regards,

Marc

SSAS use the memory he need.
so you can be surprised by the memory usage, but if its what the system
required, you don't need more.

remember that AS2005 don't load in memory all the dimensions and their
members like AS2000 do.
so the system load in memory information only when required.

also there is advanced options in SSAS to manage the memory (min, max values
etc...)
so you can take a look here, but its not recommanded to change these
parameters.

from what I see in my deployments, SQL Server + SSAS + SSIS on the same box
works really fine and the memory is correctly shared between the
applications regarding which one required more ressources.
so wait and see if you suffer performance issues

"Marc" <Roger_Rombooth (AT) community (DOT) nospam> wrote

thanks a lot for your thougths! I think you are right - I have to be patient.
I just was curious ;-)

Marc

Hi,

My AS (SQL 2005 9.00.2175.00 SP1 Enterprise Edition) is using huge amount of
memory ~ 2 GB. Does it have memory leak? Do you familiar with any hot fix
that might fix this?

Thanks,
Shay



"Jéjé" wrote:

Hi,

My AS (SQL 2005 9.00.2175.00 SP1 Enterprise Edition) is using huge amount of
memory ~ 2 GB. Does it have memory leak? Do you familiar with any hot fix
that might fix this?

Thanks,
Shay



"Jéjé" wrote:

no hotfix, no memory leak.

SSAS consume a lot of memory because:
* SSAS cache data
* the metadata of your cubes is large (large number of dimensions and
attributes)
* you have a lot of databases deployed
* many many fact table

you can reduce the memory used by changing the memory parameters in the SSAS
properties.

but don't become too restrictive, SSAS needs a lot of memory to works fine.

so I recommend to switch to x64 if it's not done and add memory in the
server.

"Shay" <Shay (AT) discussions (DOT) microsoft.com> wrote

no hotfix, no memory leak.

SSAS consume a lot of memory because:
* SSAS cache data
* the metadata of your cubes is large (large number of dimensions and
attributes)
* you have a lot of databases deployed
* many many fact table

you can reduce the memory used by changing the memory parameters in the SSAS
properties.

but don't become too restrictive, SSAS needs a lot of memory to works fine.

so I recommend to switch to x64 if it's not done and add memory in the
server.

"Shay" <Shay (AT) discussions (DOT) microsoft.com> wrote