BSO or ASO essbase

最新推荐文章于 2025-07-16 12:26:48 发布

转载最新推荐文章于 2025-07-16 12:26:48 发布 · 444 阅读

本文探讨了ASO（聚合存储）和BSO（块存储）立方体在报表立方体应用中的优缺点。ASO因其速度快和占用空间小而受到青睐，但在时间平衡集等特定场景下存在限制，此时BSO成为更好的选择。文章详细对比了两者在成员数据存储、层级信息及公式使用等方面的差异。

ASO is good due to its speed, less space, etc. but it has many limitations.
for a reporting cube, the first choice should be ASO.

Now if a reporting cube has time-balance set, which require TIME dimension
to be stored, which mean no formula allowed in TIME dimension, this make
YTD, QTD almost impossible, in this scenario, BSO is better choice

a few points about ASO/BSO cube:

1) for ASO cube, account and attribute dimension don't have hierarchy info
hierarchy include stored, dynamic, and multiple hierarchies
2) for ASO cube, formula only allowed on account and dynamic hierarchy
3) for BSO member, member dataStorage can have all types,including "dynamic calc" and "dynamic calc and store"
for ASO member, only "store data" "never share" "label only" "shared member"
4) Aggregate storage outlines require non level-0 members in accounts dimension to be either non-stored members or have internal/external formula
( have to use LabelOnly for Subscriber_Metrics, never share not working)
Ensure that all non level-0
members in the accounts
dimension and in dynamic
hierarchies are tagged as
label only, have a child that
rolls up, or have a member
formula.
5) labelonly member can not have a formula with it
6) level 0 member can not be defined label only

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/8583032/viewspace-715158/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/8583032/viewspace-715158/