Databases Reference
In-Depth Information
Pros and cons of ASO
The ASO is fast becoming the standard for extra large Essbase databases. Where
the need for high speed data retrieval for reporting and analysis can eclipse the
need for full-featured functionality, ASO fills in nicely. Here we will describe
what we feel are some of the positive features of the ASO as well as some of the
not so positive features for you.
Pros
Listed below are just a few high-level features that we feel makes the Essbase ASO
a good choice:
• Easy optimization, massive data scalability, reduced disk space, and
upto 100 times faster.
• Database creation is accomplished by either migrating a BSO outline or
defined as new after application creation.
• Outline dimensions will not need to be designated as dense or sparse.
• Outline is validated every time a database is started.
• Database calculation or aggregation of the database can be predeined
by defining aggregate views.
• Calculation order is not relevant for database calculation, but is relevant
for dynamic calculation formulas.
• Limited write back ability.
• At the end of a data load, if aggregation exists, the values in aggregation
are recalculated and updated automatically.
• Aggregate storage database outlines are page-able. This feature signiicantly
reduces memory usage for very large database outlines.
Cons
Listed below are a few high-level features that we feel you may need to be wary
of when using the Essbase ASO:
• Aggregate storage applications have some limitations that do not apply to
block storage applications with regard to consolidations, calculations, and
overall robust functionality.
• Can store only one database per application.
• Names reserved for table spaces cannot be used as application
or database names.
