Differences between ASO and BSO in Hyperion essbase

Sno	Characteristics	ASO(aggregate storage option)	BSO(block storage option)
1	Definition	ASO cubes are designed to provide rapid aggregation capabilities for much larger Essbase outlines, Typically supports large flat dimensions	BSO cubes typically contain fewer dimensions than ASO cubes, and perform numerous &  complex calculations on smaller outlines
2	Storage	In BSO, it uses 2 types of internal storage structures to store and access data 1.data block 2.index	In ASO, data will be stored in aggregate views, only level 0 blocks exist
3	calculations	ASO supports MDX formulas	BSO supports calculation scripts
4	Loading data	We can load data at level0 members only	We can load data at any level
5	Dimensionality	High	Low
6	Dimensionality	It supports >10 dimensions	It supports  >4 & <8 dimensions
7	Write back functionality	Not supported	Supported
8	Attribute dimension calculations	It supports only sum	It supports all attribute calculations sum, count, min, max, avg
9	Consolidation properties	ASO supports addition(+), ignore(~) only	BSO supports all consolidation properties for members
10	Performance	In ASO, loading data takes less time	In BSO, calculating data takes less time
11	Query logging	Not supported	Supported
12	Partitions	It supports transparent and linked partitions	It supports all partitions
13	Properties	It doesn’t support DTS(dynamic time series), Time balance properties	It supports both
14	Storage properties	It supports data store, never share, label only	It supports all storage properties
15	Attribute dimension types	It doesn’t support  Boolean tag	It supports all attribute dimension types, text, Boolean, numeric, date
16	Density	There is no concept of dense and sparse dimensions	Existence of dense and sparse dimensions
17	Data	data will be stored in .dat file	Data will be stored in .pag file