I ran Performance Monitor on my OLAP Server and during the
building of cubes the "memory available" went from "141"
in MBytes to "4" and the "memory pages/sec" went from "0"
to a range of "35 to 100". I checked the other counters
and there was no cpu or I/O bottleneck

The current values for properties in the olap server are
maximum number of threads -
minimum allocated memory - 511 M
memory conservation threshold - 2799 M
read ahead buffer size - 4 M
process buffer size - 32 M

Being new to Analysis Services, am wondering why paging is
excessive during building of cubes. Have 2 cpus and 3 gig
of memory. No users complained of response time
Any ideas/suggestions/comments?

Hi,

Your system needs indeed some tuning. I would suggest the following:

min memory I suggest to put that on 1024mb (otherwise is the cleanerthread
kicking in to fast)
memory conser treshold to 2048 (it will not take up to 2799 without /3gb
switch set)
process buffer needs probably being increased, follow this procedure to get
to the correct size:

Appendix D: How to Tune the Process Buffer Size
from:
Microsoft SQL Server 2000 Analysis Services Performance Guide
http://www.microsoft.com/technet/tre...hNet/ProdTechn
ol/SQL/Maintain/Optimize/ANSvcsPG.asp

HTH,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."

Your process buffer size is set WAY too small. I would suggest that you look
at the following two white papers.
http://www.microsoft.com/technet/pro...e/ANSvcsPG.asp
and
http://www.microsoft.com/technet/pro...e/anservog.asp

Both give excellent advise around tuning your system (the first white paper)
and what server properties to change/customize (the second white paper).

Hope that helps.
--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


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