Re: Sudden drop in speed after adding some records. Why?

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Polly (Polly_at_discussions.microsoft.com)
Date: 09/07/04 

Date: Mon, 6 Sep 2004 19:59:03 -0700

Jéjé,

First of all, thanks for your suggestion.

Before adding these 200,000 records, my fact table has over 10,000,000
reocrds.
I have done a full process in both dimensions and cubes.
How to setup the targeted number of rows in your cube?
I am using Excel 2003. Therefore, it can show about 65000 rows I think.
My calculated members are only "Net amount (Gross Amount - Discount Amount)"
and "Unit Price (Net Amount / Quantity)". They only involve simple
calculation and measures in the cube. Therefore, I don't think slow speed is
due to complexity of my calculated measures.
Also, I discovered that when I drap the result in cube editor and OWC. The
speeds are extremely slower (it hasn't finished job more than one hour) than
I expected.

What happen to my cube?

Polly

Relevant Pages

  • Re: Performance - Best Practices
    ... with hyperthreading with SQL Server. ... AS think there is 8 CPUs and optimize himself to use these 8 CPU ... I mean floating calculation and integer ... and the cube in front of this fact provide standard SUMS and DCount!) ...
    (microsoft.public.sqlserver.olap)
  • Re: Scorecard accelerator. How the score value is calculated?
    ... The calculation doesn't work correctly... ... >> Normalized Values, Actual Values, and Cube Measurements ... >> data to determine which band range includes the data value. ... >> into where it falls on an evenly distributed scale. ...
    (microsoft.public.sqlserver.olap)
  • Re: visual rank calculated member on server is very very slow
    ... Because the calculation is kind of neat.) ... - ranks every tuple on the axis. ... the identical level as the corresponding member in the other tuple. ... cube that would give the relative row and column number in an arbitrary cell ...
    (microsoft.public.sqlserver.olap)
  • Re: MDX non-leaf level aggregation performance issues
    ... How come when I use NonEmptyCrossJoin in my write-enabled cube, ... If I update a cell and then issue ... You may want to carefully examine your calculation design to ensure the safe ... use of NonEmptyCrossjoin, or consider migrating to SQL AS 2005. ...
    (microsoft.public.sqlserver.olap)
  • Re: MDX non-leaf level aggregation performance issues
    ... receiving are quite strong because if I use the same cube and remove the ... calculated cells involving NonEmptyCrossJoin my error goes away during ... If I update a cell and then ... You may want to carefully examine your calculation design to ensure the ...
    (microsoft.public.sqlserver.olap)