Best Practices to implement alternate hierarchies in AS 2K -
12-10-2005
, 12:20 PM
Hi all,
From your experiences what are the pro and cons of this three methods to
design alternate hierarchies in AS2k?
1 - Regular AS2K Hierarchies for the same dimensions (mydimension.hierarchy1
and mydimension.hierarchy2 in the same cube)
2 - Create two root nodes within the same dimension and disable the [(All)]
level.
3 - Create two different cubes one for each hierarchy and build a virtual
cube.
Some early comments:
- Are there any other solutions?
- Solutions 1 and 3 imply that the number of alternate hierarchies
is known and fixed by default.
- Solution 2 implies that member keys and names are not unique.
What is the impact?
- What about Calculated Cells when solution 1 is used? Is it
possible to create Calculated Cells taking into account both hierarchies?
- Solution 1: What about the cross join of these hierarchies, how
does AS2K handle this when building aggregations?
Subsidiary question:
In AS 2005 is there one good way to handle this?
Thx
Lionel |