Differences between ASO and BSO

A very fundamental and frequent question which appears in all Essbase interviews is what is
the difference between ASO and BSO applications
Here are few differences between ASO and BSO
Essbase system has two distinct storage options Aggregate Storage Option
(ASO) and Block Storage Option (BSO) each one has its own unique significance.


Characteristics of ASO:

• High dimensionality.
• During the retrieval Essbase automatically consolidates the date even then if business requires to perform some calculations then you can use MDX formulae.
• Only one database can be created under one application.
• Mandate to fallow the naming conventions for Application name as Applications names should not be metadata, temp, log, default, replay.
• Dynamic time series and Time balance properties are not available.
• During the restructure Essbase prompts you to choose how to proceed restructure either by keeping the exiting data as it is or by clearing the complete data.
• Only one type of partition techniques available (Transparent)
• There is no concept of Sparse and Dense dimensions.
• No Boolean attribute tag.
• Only store data, never share, label only data storage properties are available.
• Data stored in the .dat files
• Few businesses use ASO as a reporting application that holds Actual and Forecast data.

Characteristics of BSO:

• Less number of dimensions but shows the business model.
• Special functionality for Accounts and Time dimensions like Dynamic time series, Timebalance, Variance reporting.
• 3 types of partitions Replicated, Transparent, Linked.
• Currency conversion is possible.
• There is no restriction of the number of databases under one application but performance costs.
• Complex calculations can be achieved using calc scripts.
• Data store in Page files and addresses being pointed out by Index files.
• It acts as database for the planning applications so apparently you can see it for forecast purpose.