Databases Reference
In-Depth Information
• Accounts dimension does not support time balance members and association
of attribute dimensions.
• On non-account dimensions, there are restrictions on label only members and
dynamic time series members. Members tagged as dynamic hierarchies have
no restrictions on the consolidation settings. Stored hierarchy members can
only be tagged as label only or (+) addition.
• Non-account dimensions support only consolidation operator (+) addition
• Calculation scripts are not supported.
• Formulas are allowed only on account dimension members and allowed
with certain restrictions.
• Only
Level 0
cells whose values do not depend on formulas in the outline
are loaded.
• Data values are cleared each time the outline is structurally changed.
Therefore, incremental data loads are only supported for outlines that
do not change.
• Currency conversion is not supported without the use of special MDX
queries. This method can have a negative effect on performance.
As you can see, there are some substantial differences and some very good reasons to
use one type of database over another. To give you our idea of the ideal application of
ASO and BSO, read below:
• ASO Database: The ASO database is ideal for dynamically built Essbase
cubes that are usually
Read Only
and used for reporting, presentation, and
analysis. This type of database would also tend to have a rather large outline
where at least one dimension has a significant amount of members. A parts
dimension or product dimension comes to mind.
Behind this ASO database would be a large BSO parent Essbase database,
from which the dynamic ASO databases are built on the fly.
• BSO Database: The BSO database is ideal for virtually any size cube, but
where performance is not necessarily the number one priority. Accuracy
and completeness of data would be the main consideration.
The BSO database is ideal as the large parent database where users from
many different departments can trigger jobs which will dynamically build
ASO reporting cubes on an as needed basis. The typical BSO database is
ideally suited for financial analysis applications.
