Data Load Differences between ASO & BSO

Data Load Functionality	Aggregate Storage	Block Storage
Cells loaded through data loads	Only level 0 cells whose values do not depend on formulas in the outline are loaded	Cells at all levels can be loaded(except Dynamic Calc members)
Update of database values	At the end of a data load, if an aggregation exists, the values in the aggregation are recalculated	No automatic update of values. To update data values, you must execute all necessary calculations scripts
Data load buffers	The loading of multiple data sources into aggregation storage database is managed through temporary data buffers	Not Supported
Atomic replacement of the contents of a database	When loading data into an aggregate storage database, you can replace the contents of the database or the contents of all incremental data slices in the database	Not Supported
Data Slices	Aggregation storage database can contain multiple slices of data. Data slices can be merged	Not Supported
Dimension build for shared members	Full support for parent-child build method. Duplicate generation (DUPGEN) build method limited to building alternate hierarchies up to generation 2(DUPGEN2).	Support for all build methods
Loading data mapped to dates	In a date-time dimension, you can load data into level 0 members using supported date-format strings instead of member names	Date-time dimension type is not supported

Difference between Essbase 7.x, Hyperion 9.x and EPM 11.X

Essbase ASO Limitations in 7.x

Ø  Level 0 Data Loads only

Ø  Data Load Performance

Ø  No Time Balancing

Ø  No Write Back

Ø  No Complexity Calculations

New ASO Features 9.3/9.0/9.2

  

Ø  Improved Restructuring

Ø  Data base outline can be changed

Ø  Ability to export level 0 data

Ø  Kernel Improvements(Data base compression &De hierarchy)

Ø  Support for duplicate member names

Ø  Extended Substitutional variable support

   Essbase 9.3 Release

Ø  New ASO Features 9.3

Ø  Time Intelligence

Time Balance

Ø  Intelligent aggregations

Ø  Dynamic ranking

Essbase 9.3.1

Ø  New ASO Features 9.3.1

Ø  -Concurrent Loads(multiple load buffers on ASO Cube)

Ø  -Incremental Loads(Streams /tickled feeds)

Ø  -Query Cancellation

Ø  -Write Back to level zero(Not documented on 11.1.1)

EPM 11

Ø  Partial Data clear

Ø  ASO Partial Data Clear is a new option  that enables you to clear  a well defined  region of the ASO Cube

Ø  Two types of clear region are available-
                1. Physical clear of cells in region
                2. Logical Clear of cells in a region

Ø  Can be achieved by MDX Script.

 

Syntax.

1.alter database <appname>.<dbname> clear data in region '{MDX Set Expression}' [physical]

2.alter database ASOSamp.Sample clear data in region '{[Jan]}';

ASO PARTIAL DATA CLEAR BENEFITS

Ø   A portion of cube  can be erased with out affecting other data areas.

Ø  Data can be cleared by setting the values to 0 can be removed with a logical clear ,which is faster.

Ø  Data that must bepermanently erased can be fully removed with a physical clear which is slow.

 

Target of Partition

Previously in version 9.3.1 

Ø  Full support only for  BSO Partioning

Ø  ASO Could only be the source of a transparent partition

NEW FEATURE IN 11.1.1

Ø    ASO Can be the source of a transparent partition

Ø  BSO Can be used for complex calculations

Ø  ASO Can be used for aggregation performance benefits.

                         New Calculation Scripts

           New MDX Functions

                          Write back to level zero (Fully Documented)

ASO TARGET PARTITION BENEFITS

Ø  Vertical portioning

Ø  Consolidate
        Multiple cubes into target.

Ø  Target provides unified view into multiple source cubes.

Ø  Measures with different granularity
        Overcomes limitation of write back to upper levels.
        Cell can be a level 0

Ø  Member in the source,but an upper level member in the Target

Ø    New Calc script functions

Ø    New Functions list

Ø    New MDX Functions

Ø  Julian date(Date)

                                    Converts a given  unix  date to Julian equivalent

Ø  UnixDate(date)

                                    Converts a given julian date to its Unix Equivalent

Ø  GetNextDay(Date)

                         converts a given date to the next weekday date