This content has been marked as final. Show 5 replies
If you really have the case that Lvl4 jumps to LvlDetail, then it's ragged.
If Lvl4 can jump to Lvl19 and then Lvl20 and then Detail, then it's skip-level.
If you have both cases, then you have to tick both and have fun with the perf ;-)
thanks I know the theory of skip level / ragged but I have not used it in practise...
Given that my data source is a DB table, not Essbase or any other OLAP style source, is it literally all I have to do is 'tick the box' given that the data will be null for any levels other than 1?
Yeap. It will change the way the SQL against the dim is written...and quite heavily re-written hence my performance statement. If you have ragged + skip-level and as many levels as you're talking about, the SQL interesting to say the least!
Update: found Venkats post from way-back-when again: http://www.rittmanmead.com/2010/10/oracle-bi-ee-11g-skipped-ragged-hierarchies-grouping-sets-grouping-ids/
(saves me a lengthy explanation)
Edited by: Christian Berg on Jan 31, 2013 2:37 PM
Many thanks, for the detail and the warning re: performance...