Could someone please let me know:
1. How much RAM is automatically allocated to OLAP Server
by default?
2. How do you configure the server to allocate more RAM
to OLAP Server? (My DBA & Server guy does not know how to
do this!)

We have WIN 2000 Advanced Server & SQL Enterprise with 6
GB of RAM. However, 5 GB of RAM is allocated to SQL
Server using the A.W.E. configuration. Since Analysis
Services is running quite slow on numerous virtual cubes,
and due to potential "memory leak" in Analysis Services, I
thought of allocating more RAM...1 GB to start out with.

Please provide some insight. Thanks!

Check out the recent MSDN Article on tuning for Analysis Services.

It covers the available memory configurations. I think the Memory
Conservation Threshold setting might be something for you to check
out.

http://www.microsoft.com/technet/tre...e/ANSvcsPG.asp

Greg

"Steven Wong" <spwong (AT) netscape (DOT) net> wrote

Analysis Services only support max 3 GB of memory allocation

Regards
PAblo
"Greg" <gregcarder (AT) hotmail (DOT) com> wrote

ol/SQL/Maintain/Optimize/ANSvcsPG.asp

Unless you use the 64-bit Edition, which supports much much more.

Sean


--
Sean Boon
SQL Server BI Product Unit

**This posting is provided AS IS, with no warranties, and confers no
rights.**
"Pablo Guzman" <pguzman (AT) bco (DOT) pichincha.com> wrote

Please follow the links to the MSDN whitepapers listed further down on this
thread.
Note however that memory is optimized separately for cube processing and
cube queries. This is covered (lightly) in BOL for AS.
The optimization rules for a box running only AS (and a nominal installation
of SQLServer running only the AS repository) look like: (from my memory
here):
Minimum Allocated Memory = 0.5 * physical memory
Memory Conservation Threshold = 1.0 * physical memory
Processing Buffer= 200+ MB
These are set in the server property pages in AM. There are additional
optimizations (see the MSDN link)
Of course the problem gets more complex if you are running more than AS on
the box...

If your SQL Server is the datawhare house for AS AND you are hitting heavily
on SQL Server for direct reporting (or worse OLTP): YOU PROBABLY NEED TO
SPLIT SQL SERVER AND AS TO DIFFERENT MACHINES.

Are your problems in query response or in build times. These are very
different problems. Query response time
is influenced by network topologies, client tools, and cube design (numbers
and sizes of dimensions) and MDX complexity. As such, they are really
design issues, not simple memory allocation issues. See Spoffords book for
examples.

What memory leak?

Hope This Helps.


dlr
"Steven Wong" <spwong (AT) netscape (DOT) net> wrote