If you see this message, your browser either has disabled or does not support JavaScript. To use the full features of this help system, such as searching and the table of contents, your browser must have JavaScript support enabled. If your browser supports JavaScript, it provides settings that enable or disable JavaScript. When JavaScript is disabled, you can view only the content of the help topic, which follows this message.

Comparison of Aggregate and Block Storage

Introduction

Essbase provides an aggregate storage kernel as a persistence mechanism for multidimensional databases. Aggregate storage databases enable dramatic improvements in both database aggregation time and dimensional scalability. The aggregate storage kernel is an alternative to the block storage kernel. Aggregate storage databases typically address read-only, “rack and stack” applications that have large dimensionality, such as the following applications:

Customer analysis. Data is analyzed from any dimension, and there are potentially millions of customers.

Procurement analysis. Many products are tracked across many vendors.

Logistics analysis. Near real-time updates of product shipments are provided.

A sample application (ASOsamp), a data file, and a rules file are provided to demonstrate aggregate storage functionality.

Aggregate storage applications, which differ from block storage applications in concept and design, have limitations that do not apply to block storage applications. The following sections describe the differences.

Displayed in the Application Properties window and the Database Properties window in Administration Services.

Information not supported by or relevant to aggregate storage applications is not shown. For a description of aggregate storage-specific information, see the Oracle Essbase Administration Services Online Help for the Application Properties window and Database Properties window.

Displayed in the Application Properties window and the Database Properties window in Administration Services

Configuration settings (essbase.cfg)

For a list of the settings that apply to aggregate storage databases, see the Oracle Essbase Technical Reference.

For a list of the settings that do not apply to block storage databases, see the Oracle Essbase Technical Reference.

All dimension members at the same level as the member must be label only

The parents of the member must be label only.

Note:

On dynamic hierarchies, ability to tag any member as label only

Note:

On conversion from a block storage database, attribute dimension members are tagged as Dynamic Calc. On standard dimension members Dynamic Calc tags are converted and tagged as stored members, which changes the Members Stored value on the Dimensions tab of the Database Properties window in Administration Services.

Support for all member storage types in all types of dimensions except attribute dimensions