Hello,
I have written this simple MDX query and it takes more than 1 minute to execute (the timer is still running as
I am writing this and it looks like my EG 4.2 crashed).
SELECT
NON EMPTY { [Measures].[FACTSUM] } ON COLUMNS,
NON EMPTY CrossJoin
(NONEMPTYCROSSJOIN
(NONEMPTYCROSSJOIN
(NONEMPTYCROSSJOIN
(
{ descendants([DIM_KPI].[All DIM_KPI] )},
{ descendants([DIM_PERIOD].[HRH_CALENDERPERIOD].[All HRH_CALENDERPERIOD]) }),
{ [DIM_CUSTOMER].[DISCRIPTOR].AllMembers }),
{ descendants([DIM_SZENARIO].[All DIM_SZENARIO]) }),
{ descendants([DIM_SALES].[All DIM_SALES]) }
) ON ROWS
FROM
[mySmallCube]
WHERE mySmallCube.... NOT IS MISSING AND
mySmallCube.... NOT IS MISSING AND
mySmallCube.... NOT IS MISSING AND
mySmallCube.... NOT IS MISSING AND
mySmallCube.... NOT IS MISSING AND
mySmallCube.... NOT IS MISSING AND
...;
The cube is build from a fact table with 14! facts. So an ms excel spreadsheet is faster than the OLAP cube
in the moment. I wonder why this is? Have I done some big mistake in the code?
The descendants are an average of 4 Levels and are about 100 members whereas the DIM_SALES has about 3000 members in total
but are only two are important because I have an MDX filter on the cube that only gets members
from the DIM_SALES dimension where they equal my user id.
Thanks for any hints,
Bob