Updates Performed as Part of Hybrid Optimization
The conversion process consists of the following modifications:
- All the parent members where the Data Storage property is not set to Dynamic Calc are updated to Data Storage property value Dynamic Calc. This applies to all dimensions except Entity. As a best practice in hybrid mode, you have to set the Data Storage property for all parent members to Dynamic Calc.
- Level 0 members where the Data Storage property is Dynamic Calc and there is no member formula, are updated to Data Storage property value Store. This applies to all dimensions except Entity.
- Solve Order for certain out of the box dimension members will be set.
- The density of the Period and Movement dimensions will be set to Dense. The density of the Account dimension will be set to Sparse. The density of the other dimensions will remain Sparse. The dimension performance order will also be updated
- These Essbase settings are turned on in the application configuration:
- IGNORECONSTANTS - Enables dynamically calculated members of sparse
dimensions to be exported using the All Data option in Database
Management (see, All Data - Data Extract Option) in
a performant way that does not result in data explosion, that is, member
formulas with constants will only return a value if any of the intersections
used as operands are not missing.
Note:
See Performing Post-Conversion Steps After Optimizing the Application for Hybrid for impact to Database Management Integrations and Best Practices for Member Formulas. - ASODYNAMICAGGINBSO - Uses hybrid aggregation mode for queries, that is, wherever possible, block storage queries execute with efficiency similar to that of aggregate storage databases.
- IGNORECONSTANTS - Enables dynamically calculated members of sparse
dimensions to be exported using the All Data option in Database
Management (see, All Data - Data Extract Option) in
a performant way that does not result in data explosion, that is, member
formulas with constants will only return a value if any of the intersections
used as operands are not missing.
- You may notice a significant reduction in Essbase database size due to the fact that Account is now a sparse dimension which generally results in smaller block size and less sparsity within the blocks.
- After the application is successfully optimized a summary log can be found in the Make Period and Movement Dense job in the Job Console.