I'm new to MDX and CUBES and I'm wondering if anyone can provide some insight to the following:
In SQL: We can write a sub-query that can suppress records from being selected twice using the "exists" function.
a) INSERT INTO TEMP_A SELECT * FROM TABLEA, TABLEB WHERE A.JOIN=B.JOIN AND <SOME_CRITERIA IS TRUE>
b) INSERT INTO TEMP_B SELECT * FROM TABLEA, TABLEB WHERE A.JOIN=B.JOIN AND <SOME_OTHER_CRITERIA IS TRUE> AND NOT EXISTS (SELECT * FROM TEMP_A WHERE A.JOIN=TEMP.JOIN)
c) INSERT INTO TEMP_C SELECT * FROM TABLEA, TABLEB WHERE A.JOIN=B.JOIN AND <SOME_OTHER_CRITERIA IS TRUE> AND NOT EXISTS (SELECT * FROM TEMP_B WHERE A.JOIN=TEMP.JOIN)
Using Cubes:
I understand that TABLEA and TABLEB would constitute a cube and become facts or dimensions.
Questions:
1) How would I create temporary data stores? Should I create a local cube?
2) How would I create a MDX query that would reference a cube and a temporary result set as in (b) and (c)?
3) How would I handle such requirement using ReportPortal?
Any examples using the foodmart database or additional information related to such requirement is greatly appreciated.
1) No, you don’t have to create a local cubes. Most of joins you described can be preformed in MDX: Using NonEmptyCrossjoin if your tables represent dimensions or Virtual cubes if your tables represent fact tables.
Report Portal
How to create/reference temporary results in MDX
Posted - 08/17/2005 : 08:43:24
