As I get to see more Enterprise BI initiatives, it is becoming increasingly clear (atleast to me!) that when it comes to information dissemination, Hybrid Online Analytical Processing (HOLAP) is the way to go. Let me explain my position here.

As you might be aware, Relational (ROLAP), Multi-dimensional (MOLAP) and Hybrid OLAP (HOLAP) are the 3 modes of information delivery for BI systems. In an ROLAP environment, the data is stored in a relational structure and is accessed through a semantic layer (usually!). MOLAP on the other hand stores data in proprietary format providing the notion of a multi-dimensional cube to users. HOLAP combines the power of both ROLAP and MOLAP systems and with the rapid improvements made by BI tool vendors, seems to have finally arrived on the scene.

In my mind, the argument for subscribing to the HOLAP paradigm goes back to the “classic” article

by Ralph Kimball on different types of fact table grains. According to him, there are 3 types of fact tables – Transaction grained, Periodic snapshot, Accumulating snapshot and that atleast 2 of them are required to model a business situation completely. From an analytical standpoint, this means that operational data has to be analyzed along with summarized data (snapshots) for business users to take informed decisions.

Traditionally, the BI world has handled this problem in 2 ways:

1) Build everything on the ROLAP architecture. Handle the summarization either on the fly or thro’ summarized reporting tables at the database level. This is not a very elegant solution as everybody in the organization (even those analysts working with summarized information) gets penalized for the slow performance of SQL queries issued against the relational database through the semantic layer.

2) Profile users and segregate operational analysts from strategic analysts. Operational users are provided ROLAP tools while business users working primarily with summarized information are provided their “own” cubes (MOLAP) for high-performance analytics.

Both solutions are rapidly becoming passé. In many organizations now, business users wants to look at summarized information and based on what they see, needs the facility to drill down to granular level information. A good example is the case of analyzing Ledger information (Income statement & Balance Sheet) and then drilling down to Journal entries as required. All this drilling down has to happen through a common interface – either an independent BI Tool or an enterprise portal with an underlying OLAP engine.

This is the world of HOLAP and it is here to stay. The technology improvement that is making this possible is the relatively new wonder-kid, XMLA (XML for Analysis). More about XMLA in my subsequent posts.

As an example of HOLAP architecture, you can take a look at this link

to understand the integration of Essbase cubes (MOLAP at its best) with OBIEE (Siebel Analytics – ROLAP platform) to provide a common semantic model for end-user analytics.

Information Nugget: If you are interested in Oracle Business Intelligence, please do stop by at http://www.rittmanmead.com/blog/ to read his blogs. The articles are very informative and thoroughly practical.

Thanks for reading. Please do share your thoughts.

Posted by Karthikeyan Sankaran
Comments (3)
June 9th, 2008

Comments (3)

Chris Webb - July 29th, 2008

And now that MS have bought DATAllegro, there's the prospect of using SSAS in this way on a future SQL Server/DATAllegro system too. Although of course there's also the prospect of Analysis Services being able to reuse this technology too, which would be even cooler...

Karthikeyan Sankaran - June 11th, 2008

Thanks Chris for your comments. Your thoughts reinforces my belief that the BI world is going to get far more interesting across the overall BI architectural landscape - Acquisition, Integration and Dissemination. My current project is on building a HOLAP platform with SQL Services Reporting Services (SSRS) acting as the glue across Essbase cubes and granular data on SQL Server. I will write about the trials & tribulations of such an endeavor in my next few posts. Oh! By the way, Essbase is "one of the best" when it comes to MOLAP. Is that phraseology ok? :-) Thanks and Have a great day! Regards Karthik

Chris Webb - June 9th, 2008

Coming from a Microsoft Analysis Services point of view, I completely agree. I don't think any MOLAP vendor will be able to keep pace with some of the new developments in database engine technology that allow fast querying on vast data volumes, but at the same time I think existing OLAP engines will prosper as query and calculation layers on top of these databases because, frankly, SQL can't cut it in the world of BI. I talked about this a bit in the section on "Support for other RDBMSs" here: http://cwebbbi.spaces.live.com/blog/cns!7B84B0F2C239489A!1877.entry Not sure I agree with our comment on Essbase being "MOLAP at its best" though :-)

Comments are closed.