Mastering Hybrid Essbase: Fundamentals, Tips & Best Practices

Table of Contents

1. Introduction
2. What is Hybrid S Space?
3. The Different Types of Cubes
   • Block Storage Option (BSO)
   • Aggregate Storage Option (ASO)
4. Hybrid: The Love Child of BSO and ASO
5. How Hybrid Works
6. Enabling Hybrid in Different Versions of Essbase
   • On-Premise Essbase
   • EPM Cloud and Essbase 19c
7. Optimizing Hybrid Performance
   • Choosing Sparse and Dense Dimensions
   • Setting Dynamic Calc and Stored Members
   • Understanding Calculation Order
   • Managing Attribute Dimensions
   • Odometer and Solve Order
8. Best Practices for Formulas
   • Calculating Ratios and Computations
   • Dealing with Large Block Calculations
9. Additional Tips and Considerations
   • Reducing Fragmentation and Empty Blocks
   • Cache Settings and XREF Usage
10. Hybrid BSO vs ASO
11. Migrating from BSO to Hybrid
12. Conclusion

Hybrid S Space: Combining the Power of BSO and ASO

In the world of Essbase, there are two main types of cubes: Block Storage Option (BSO) and Aggregate Storage Option (ASO). Each has its strengths and limitations. But what if You could have the best of both worlds? Enter Hybrid S Space, the love child of BSO and ASO.

What is Hybrid S Space?

Hybrid S Space is a hybrid solution that combines the extensive calculation capabilities of BSO with the performance advantages of ASO. It allows for larger dimensions, reduces database size, and improves refresh performance. With Hybrid S Space, you can utilize the powerful calculation engine of BSO while benefiting from the increased dimensionality and faster retrievals of ASO.

The Different Types of Cubes

Before diving deeper into Hybrid S Space, let's briefly discuss the two main types of cubes: BSO and ASO.

Block Storage Option (BSO)

BSO is the original Essbase database Type. It utilizes a powerful calculation engine and pre-stores all information. However, due to the way it pre-aggregates data, BSO is limited in the number of dimensions it can handle. Aggregations and calculations can be slow, especially with large sparse dimensions. BSO uses a proprietary calculation language called CalcScript and requires careful management of dense and sparse dimensions.

Aggregate Storage Option (ASO)

ASO, on the other HAND, is a more freewheeling option. It allows for larger dimensions and does not require aggregations. ASO cubes store data at level zero members and utilize the Multi-Dimensional Expression (MDX) language. While ASO is faster for certain operations, it lacks the extensive calculation capabilities of BSO.

Hybrid: The Love Child of BSO and ASO

Hybrid S Space combines the best features of BSO and ASO. It inherits BSO's calculation engine and allows for larger dimensions like ASO. With Hybrid cubes, you can set upper levels of sparse dimensions to dynamic calculation, resulting in faster retrievals. The calculation order follows the behavior of BSO cubes, but you also have the option to use solve order for more precise calculations.

How Hybrid Works

Hybrid cubes have two calculator engines: one for BSO and one for ASO. Depending on the configuration, the cube will either optimize calculations using the ASO engine or fall back to regular BSO mode. By enabling Hybrid in Essbase, you can take AdVantage of the ASO query processor and improve overall performance. However, it requires careful configuration and testing to fine-tune the hybrid functionality.

Enabling Hybrid in Different Versions of Essbase

Enabling Hybrid depends on the version of Essbase you're using. In on-premise Essbase, you need to modify the Essbase configuration file. However, be aware that Hybrid is not officially supported for on-premise planning. In EPM Cloud and Essbase 19c, Hybrid is enabled by default, with additional configuration options for optimal performance.

Optimizing Hybrid Performance

To ensure the best performance with Hybrid S Space, there are several optimization techniques to consider. These include choosing the right mix of dynamic and stored members, setting the solve order of dimensions, managing attribute dimensions, and understanding asymmetrical queries. Additionally, reducing fragmentation, removing empty blocks, and optimizing cache settings can further improve performance.

Best Practices for Formulas

When creating formulas for Hybrid cubes, it's essential to consider the order of calculation and the location of computations. Formulas that can be calculated after aggregations should have a higher solve order, while computations that need to be computed before aggregations can be set as stored members. Following best practices for formulas helps ensure accurate results and efficient calculations.

Additional Tips and Considerations

Some additional tips for optimizing Hybrid cubes include reducing fragmentation, adjusting cache settings, and minimizing the use of cross-dimensional references (XREFs). It's essential to test and iterate on the configuration to find the best balance between performance and functionality.

Hybrid BSO vs ASO

While Hybrid BSO provides significant advantages over regular BSO, it's important to note that ASO still has its use cases. There are certain scenarios where ASO is more suitable, particularly in terms of speed and simplicity. Hybrid BSO doesn't replace ASO but rather offers an optimized middle ground.

Migrating from BSO to Hybrid

If you're currently using BSO cubes, migrating to Hybrid S Space can bring significant performance improvements. However, it's not a simple "turn it on and expect it to work" process. Thorough testing and tuning are necessary to ensure a seamless transition and optimal performance.

Conclusion

Hybrid S Space offers the best of both BSO and ASO, combining powerful calculations with improved performance. By understanding the capabilities and configurations of Hybrid cubes, you can take full advantage of this hybrid solution. Remember to test and fine-tune your configuration to achieve the best results and leverage the power of Hybrid S Space to enhance your Essbase experience.

Highlights

• Hybrid S Space is the hybrid solution that combines the power of BSO and the performance advantages of ASO.
• Hybrid cubes have two calculator engines: BSO and ASO, providing extensive calculation capabilities and the ability to handle larger dimensions.
• Enabling Hybrid in Essbase varies depending on the version, with on-premise, EPM Cloud, and Essbase 19c offering different configuration options.
• Optimizing Hybrid performance involves choosing the right mix of dynamic and stored members, setting solve order, managing attribute dimensions, and understanding asymmetrical queries.
• Best practices for formulas in Hybrid cubes include considering the order of calculation and using stored members for computations that need to be computed before aggregations.
• It's important to test and fine-tune configurations to optimize Hybrid cube performance, reduce fragmentation, and adjust cache settings.

FAQ

Q: Can I use Hybrid S Space in on-premise planning? A: While it's possible to enable Hybrid in on-premise Essbase, it's not officially supported for on-premise planning. It's recommended to consult with Oracle and thoroughly test the configuration before implementing it.

Q: Can I migrate from regular BSO to Hybrid S Space? A: Yes, it's possible to migrate from regular BSO to Hybrid S Space. However, it requires careful testing and tuning to ensure a smooth transition and optimal performance.