Re: [?] MS AS: virtual memory usage

#1

Andrew,

You have two options, one of which you pursued below. Analysis Services
must load all dimension members into memory by design. If you are building
5 dimensions with 1 million products each, and if each one requires 200 MB
of memory that would represent about 1 GB of memory. That does seem to be
on the low-end of memory requirements for dimensions of that size, but it
does fit well under the 3 GB limit that Analysis Services can use provided
you've set the boot.ini file to use that much memory. If you find that your
implementation is still memory constrained, I would strongly recommend that
you investigate 64-bit as an alternative. With 64-bit the 3 GB memory
limitation is removed.

Sean

--
Sean Boon
SQL Server BI Product Unit

**This posting is provided AS IS, with no warranties, and confers no
rights.**
"Andrew Surinov" <sav (AT) tut (DOT) by> wrote

Quote:

Hello, All!

While deploying an MS AS database with relatively large dimensions (for
example "products" dimensions with 1000000 products, which makes ~ 200 MB
per product hierarchy, and we have at least 5 products hierarchies), I've
found that the OLAP Server loads all these dimensions directly into
virtual
memory. Manipulations with VLDMThreshold entry only seem to split or merge
this memory across several processes, but the total amount is still huge.
My question is: Is there a way to change this behavior and tell the OLAP
Server not to use so much virtual memory? Or this behavior is critical for
performance? Is the only solution for this to buy more RAM ?

With best regards, Andrew Surinov. E-mail: sav (AT) tut (DOT) by

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: [?] MS AS: virtual memory usage

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap

Re: [?] MS AS: virtual memory usage - 07-03-2003 , 02:37 PM