Agenda
- When ASO and BSO Cubes are useful
- How ASO Cubes offer new data base types
- Performance of ASO Cubes versus BSO Cubes
- Differences between ASO and BSO Cubes
- When to use ASO Cubes and how users see ASO Cubes
BSO Cubes
- Useful for systems that involve complex calculations
- BSO Engine cannot handle much sparse data
ASO Cubes
- Different method for storage and calculations
- Different storage kernel
- Useful for databases which are read only
- Useful for cases where dimensions are large in number
Eg. Customer analysis, procurement analysis
ASO vs BSO
- Load time in ASO is 20% faster than BSO
- Calculation time is 20 times faster
- Storage space is 10 times smaller
- ASO Cubes becomes slower than BSO Cubes for Queries
- ASO Cubes can have many more dimensions
End Users
- No difference for end users during use with Smart View, Add in, FR Reports
- Database is sparse and has many dimensions. Aggregation is much faster
- Calculation of the database is frequent
- Multidimensional Index
- Indexes the index to facilitate faster aggregation
- Unlike BSO Storage is not in Blocks but in optimized aggregation nodes
- Loads data at only Level 0
- Algorithm selects and stores queries and increased speed
- These queries will pre calculate data values and store pre calculate data results in aggregations
No comments:
Post a Comment