memory usage in SQL Server Analysis Services 2005 (SSAS)

Tech-Archive recommends: Speed Up your PC by fixing your registry

Folks

I am running the enterprise edition of Analysis services 2005. I have a
cube that has 4 dimensions (including the date) and 2 years of test
data. (The data generated is pretty dense as it was generated by an
automated program. And we expect the rpoduction data to be this dense
as well.)

I was able to setup the cube and process around 43 million rows easily
(within about 20 minutes).


I am facing performance issues while querying this data. I am new to
this version of analysis services. When I say performance issues, I
mean, it is really slow. More than 15-20 seconds to retrieve data for a
single dimension and the corresponsing measures. I investigated
further and found that the CPU on the server spikes to 100% when I
issue a query. However, the memory used is only 55 MB. My server has 2
GB of RAM. Is there anyway to tune this or speed this up?. The cube
size on disk is less than 1 GB. So I am finding it very difficult to
accept that this is the best we can do with this.

Your help is highly appreciated.

Thanks
Techdummy

.

Relevant Pages

  • Analysis Services Query Log Inconsistency
    ... Analysis Services 2000 allows up to 128 dimensions per cube; ... level in each dimension a particular query uses. ...
    (microsoft.public.sqlserver.olap)
  • Spoof shared dimension for virtual cube
    ... just getting back into Analysis Services again, ... Two cubes, ... Cube1 has 10 more dimensions, ... I'm sure it's possible to get this result with MDX (which I'm still not ...
    (microsoft.public.sqlserver.olap)
  • Re: ROLAP Dimension Question
    ... The Analysis Server has its own caches -- including caches for calculations. ... So if an attribute changes in the dimension table but Analysis Services ... I have a Cube. ... If a member gets added to one of my dimensions, it will not appear in my ...
    (microsoft.public.sqlserver.olap)
  • Re: dimensions and cube aggregs
    ... You might consider looking at the Analysis Services Performance Guide. ... > I have 8 dimensions that are needed for various queries. ... > I am trying to use them all in 1 cube, ... > The problem is the aggregations get a bit out of hand even at 20%. ...
    (microsoft.public.sqlserver.olap)
  • Re: Fairly Large Cube-Performance Improvement recommendations
    ... move) if the cube has large number of dimensions. ... We have 30 dims in the cube and the storage design wizard taked about 45 ... > 1) execute a fairly long query, let's say one that runs for 20 seconds. ...
    (microsoft.public.sqlserver.olap)