Database Reference
In-Depth Information
other types of cost include:
• Fact data Enrichment: When an Attribute dimension must be converted to a
standard dimension, thus requiring the addition of the former Attribute data to
the fact data in a preload step.
• Fact data Additions: Sometimes it makes sense to precalculate and load
upper-level data (7.6.2.1) or convert “Balance data” to “Flow Data” (7.6.2.4).
• metadata Enrichment: to support Compound Attributes (7.6.2.5) or “natural
Sign” processing (7.6.2.1).
While these costs involve development effort for your external processes, these are
one-time costs. Similarly, the cost of executing the newly developed process is a one-
time-per-load cost and does not pose any repetitive penalty on query performance.
7.6.2 Alternative Design Options: Designing to Maximize Use of Stored Hierarchies
7.6.2.1 Time Spans (YTD, QTD) Using Stored Hierarchies
timeSpans can be written in
mDx or constructed using Stored hierarchies. By now, you will be able to guess which
approach I recommend.
The mtD hierarchy remains unchanged. two new Stored hierarchies are
added: [Internal Calculation ytDs] and [Internal Calculation QtDs]. They are named
this way to discourage users from opening them (although that will not hurt) because
they do not have the familiar look of the ytD and QtD hierarchies that appear below
them, which look as they did in the original ASosamp (Figure 7.13).
Figure 7.13
Alternative YTD and QTD design for ASOsamp. (From Oracle Essbase Administration Services. With permission.)
