Types of OLAP Systems

What Are The Types of OLAP Systems?

OLAP systems vary quite a lot, and they have generally been distinguished by a letter tagged onto the front of the acronym “OLAP,” for On-Line Analytical Processing. MOLAP and ROLAP have classically been the most established types, and the other distinctions represent little more than the marketing programs on the part of the vendors to distinguish themselves, for example, SOLAP and DOLAP. Here, we aim to give you an idea of what these distinctions have meant.


The New Direction in OLAP Technology:

The newest software in the OLAP and Business Intelligence world combines, in real-time, the benefits of both relational tables and multidimensional business data modeling.  The latest technology removes the proprietary format of its MOLAP predecessors by living/saving in source relational tables, like SQL Server.  Lastly, new OLAP technology maintains a constant connection with existing back-end systems and delivers immediately responsive reports/analytics in Excel and other front-end tools (dashboards, query tools, etc.)

If you like the sound of that, check out Olation® from PARIS Tech, the sponsor of OLAP.com


Major OLAP Technology Types:

 Hybrid Transaction / Analytical Processing (HTAP)

Gartner coined the term HTAP in a paper in the beginning of 2014 to describe new in-memory data systems that do both online transaction processing (OLTP)  and online analytical processing (OLAP).

HTAP relies on newer and much more powerful, often distributed, processing: sometimes it involves a new hardware “appliance”, and it almost always requires a new software platform. Beyond this, the key point seems to be that all the technology is sited in the relational database.  And so, there’s no more data replication, and new transactional information becomes part of an analytical model in as fast a time as is technologically possible.

HTAP represents a new way to tie data together in a way that hasn’t been possible before– a real uniting of relational data stored in tables with the data models that are used for decision making by the business leaders.

For an example of an HTAP product, check out Olation® from PARIS Tech, the sponsor of OLAP.com. Olation can be categorized as an HTAP product — even the name Olation implies the combination of “OLAP” and “relational” technologies.

Multidimensional OLAP (MOLAP) – Cube based

MOLAP products enable end-users to model data in a multidimensional environment, rather than providing a multidimensional view of relational data, as ROLAP products do (see next tab).

The structure of a multidimensional model is not a series of tables (as exists in a relational database) but what is generally referred to as a cube. Cubes modeled in a multidimensional database extend the concept associated with spreadsheets: just as a cell in a spreadsheet represents the intersection of two dimensions (sales of product by region), a cell in a cube represents the intersection of an infinite number of dimension members (e.g., Products, Customers, Regions, Months …nth dimension). As in a spreadsheet, a cell might be calculated by formulas involving other cells.

In short, multidimensional databases allow users to add extra dimensions, rather than additional tables, as in a relational model. And the MOLAP cube structure allows for particularly fast, flexible data-modeling and calculations. For one, locating cells is vastly simplified—an application can identify a cell location by name (at the intersection of dimension members) rather than by searching an index or the entire model (via SQL SELECT statements), as in a relational database.  Further, multidimensional models incorporate advanced array-processing techniques and algorithms for managing data and calculations. As a result, multidimensional databases can store data very efficiently and process calculations in a fraction of the time required of relational-based products.

What are the perceived drawbacks of MOLAP tools?

For one, relevant data must be transferred from relational systems,which is aa potentially “redundant” re-creation of data in another (multidimensional) database. Once data has been transferred, there may be no simple means for updating the MOLAP “engine” as individual transactions are recorded by the RDBMS. Also, MOLAP products are typically proprietary systems. For some IT departments, introducing a new database system is an anathema, even if it means significantly greater productivity for the type of planning, analysis and reporting that end-users rely on the (MOLAP) solution to perform.

For a good example of a fast, scalable MOLAP product, check out PowerOLAP® from PARIS Tech, the sponsor of OLAP.com.

Relational OLAP (ROLAP) –Star Schema based

ROLAP products (for Relational OLAP) are credited with being able to directly access data stored in relational databases. The notion is that they can readily retrieve transactional data, although this becomes suspect when very large data sets are in play, or if more complex calculations are to be delivered, based on the transactional data. ROLAP products enable organizations to leverage their existing investments in RDBMS (relational database management system) software.

ROLAP products access a relational database by using SQL (structured query language), which is the standard language that is used to define and manipulate data in an RDBMS. Subsequent processing may occur in the RDBMS or within a mid-tier server, which accepts requests from clients, translates them into SQL statements, and passes them on to the RDBMS.

ROLAP products provide GUIs and generate SQL execution plans that typically remove end-users from the SQL writing process. However, this over-reliance on processing via SQL statements—including processing for multidimensional analysis—is a drawback. Whether it is generated “transparently” or not, SQL is the language of relational tables: SQL’s vocabulary is limited and its grammar often inflexible, at least to accommodate the most sophisticated modeling required for multidimensional analyses.

There are further drawbacks to structuring a multidimensional model solely within relational tables: Before end-users can submit requests, the relevant dimension data must be extracted and reformatted in de-normalized structures known as star schema or snowflakes (so-called because of the way the tables are conjoined). These tabular structures are necessary to provide acceptable analytical performance. Sophisticated ROLAP applications also require that aggregate tables be pre-built and maintained, eliminating the need to process summary data at runtime

One advantage of ROLAP over the other styles of OLAP analytic tools is that it is deemed to be more scalable in handling huge amounts of data. ROLAP sits on top of relational databases therefore enabling it to leverage several functionalities that a relational database is capable of.


HOLAP is the product of the attempt to incorporate the best features of MOLAP and ROLAP into a single architecture. This kind of tool tries to bridge the technology gap of both products by enabling access to or use of both multidimensional database (MDDB) and Relational Database Management System (RDBMS) data stores. HOLAP systems store larger quantities of detailed data in the relational tables while the aggregations are stored in the pre-calculated cubes. HOLAP also has the capacity to “drill through” from the cube down to the relational tables for delineated data.Some of the advantages of this system are better scalability, quick data processing and flexibility in accessing of data sources. The issue with HOLAP systems lies precisely in the fact that they are hybrids: at best they partake of the strengths of other systems…but they also evince the weaknesses of each, in an attempted mashup of two distinct technologies.

Other Types:

There are also less popular kinds of OLAP technology that one might encounter every so often, listed below. Some of these self-designated product types do not really exist any longer. (An example is WOLAP, since nearly all products provide a Web interface, to meet market demand.) But they are included, to help provide a backgrounder in how vendors have tried to set themselves apart, and also how the OLAP market developed over time.

Desktop OLAP (DOLAP)

Desktop OLAP, or “DOLAP,” is based on the idea that user can download a section of an OLAP model from another source, and work with that dataset locally, on their desktop. DOLAP is purportedly easier to deploy, with a potential lower cost, but almost by definition comes with a limited functionality in comparison with other OLAP applications.


Simply put, a WOLAP signifies a Web browser – based OLAP technology. And it suggests a technology that is Web-based only, without any kind of option for a local install or local client to access data.  The most appealing features of this style of OLAP was (past tense intended, since few products categorize themselves this way) the considerably lower investment involved on the client side (“all that’s needed is a browser”) and enhanced accessibility to connect to the data. The fact is that by now most OLAP products provide an option for Web-only connectivity, while still allowing other client options for more robust data modeling and other functionality than a Web client can provide.

Mobile OLAP

Mobile OLAP is merely refers to OLAP functionalities on a wireless or mobile device. This enables users to access and work on OLAP data and applications remotely thorough the use of their mobile devices.

Spatial OLAP (SOLAP)

The aim of Spatial OLAP (thus, SOLAP) is to integrate the capabilities of both Geographic Information Systems (GIS) and OLAP into a unified solution, thus facilitating the management of both spatial and non-spatial data. The driving idea is to provide quick exploration of data that can point to trends and analysis in a geographic context, whether place-names sourced from a GIS or overlaying maps that show, for example, customer purchase behavior.


More Articles on OLAP & Business Intelligence

BIG Data Road Blocks to Tackle

As I think most of us would agree, Big Data has made big leaps in providing the business world with a large advantage. Luc Burgelman does a great job of identifying the three hurdles that he believes are holding businesses back from reaping the most benefit from their Big Data, in his article. The first hurdle Burgelman refers to is the ability to evolve. He brings up a great point, companies are looking for different things than they were just two years ago. They need to take technology further than before to accomplish what they need as a final result. Also, companies need to be able to engage different/more departments in the analytical process. It is no longer just about the IT team. Other departments have valuable assets to add to the equation of data anaylsis, and we have to be open to sharing the data across the departments and company, taking a more well-rounded approach to tackling large analytical processes. Which leads smoothly into Burgelman’s second point… Not only is it important to be involving more of the company’s departments, but we need to make sure that the C-level Executives are equally “on-board.” Let’s face it, without their their final “blessing,” no data technology plan will hit the ground running and be successful. Executives need to be equally passionate about the technology and understand the great benefit and ROI of the analytics behind the data. The third hurdle that Burgelman talks about is changing the mindset of not only the C-level executives but of all who work directly with the data such as the data users and data scientists. Big...

Human Resources, Making BIG Strides in Business Analytics

One thing is certain, if you want to run a successful business, you need to hire the right people to help you get there. Who is in charge of recruiting and hiring your team members? “DING, DING, DING!” you guessed it, Human Resources. Human Resources is beginning to pull ahead in the Business Analytics world. In a “Big Data” world, HR can use “People Data” to their advantage and help businesses develop strategy when it comes to hiring the best candidates. As David Klobucher writes in his article, “Data-driven confidence will help HR professionals identify behaviors and interview styles that attract better employees, as well as qualities that make effective workers – and lead to faster promotions.” I agree with Klobucher, this is a great time to be in HR. There are big opportunities that may be presented to anyone working in HR. Executives within businesses are looking to their Human Resources department to help build the strategy to success. Of course this all depends on if HR professionals “welcome” the technology with warm arms. As stated in the article, many individuals working with Human Resources are not completely comfortable using data just yet. In today’s world, Big Data surrounds all of us, but for HR, this can lead to big success from analyzing data of past successes and past failures. In some HR departments, to take on this scope of technology could be intimidating, however like one of my favorite sayings goes, “I never said it would be easy, I only said it would be worth it.” Read original article here....

Big Data & Using The Right Analytics For The Business Problem

  Do you agree with the phrase, “less is more?” We hear that phrase a lot, but what does it actually mean in the Business Intelligence/Big Data world? In the article, Big Data Breakdown: Use the Right Analytics for the Business Problem, the author gives a great example of how that phrase, “less is more,” stands true.  Meta (great name!) S. Brown points out that in today’s business world, many are wrapped up in the thought of, “the more data the better.” But in actuality, to gain the most return on your investment, the key is to have just the “right” amount of data to solve your problem.  Interesting that Brown states that many businesses actually need only between 1%-10% of the amount of data they are currently collecting. Maybe this is something that businesses need to start taking a closer look at, namely, “can collecting too much data be doing more harm than good?” Check out the original article...

27 Opinions and the Future of Excel 

 “Excel is one of those applications that the business world cannot live without.” So says one of 27 Excel experts commenting on Microsoft’s Power BI Suite and its effect on the great wide world of spreadsheet users. As Excel lovers, we couldn’t agree more! There’s a wealth of wisdom in the observations made by these 27 pros. Along with the main topic of what’s new in Power BI Suite, there’s excellent insight on the use of Excel and BI generally. (For a good post about what one expert calls a “running joke in BI communities—‘What is the most used feature in any business intelligence solution?’”, see But, Does It Export to Excel?, from PARIS Technologies.) About what’s new with Power BI Suite, the experts agree that it delivers significantly powerful new capabilities: from connecting to enterprise data (Power Query) to aggregating differently sourced data (Power Pivot) to creating exciting visualizations (Power View and Power Map—watch out, “Visual Analytics” products!), this suite of tools signifies a whole new era of “self-service BI” for Excel users. Smart guys and gals that they are, the experts point up some caveats. How will these new capabilities affect a company’s “B.I. workflow[s]”? And, mightn’t Power BI, by empowering Excel user(s), propagate more—and more complex—silos of data among disconnected groups of users? Will IT lose total control, if users feel it’s their Excel-given birthright to reach back to underlying data sets for BI solutions?  And as to collaborative work—will SharePoint be the answer, finally? All the caveats and concerns are certainly worth considering … That said, from our standpoint: we begin with the premise that...

The Problem and Solution in the BI Market

A recent post on the PARIS Tech Blog, The Problem in the BI Market, highlights a few key facts/issues in the BI market.  Some of these include disconnected applications, disconnected IT and front-end users, and slow processing times. Most interesting is the emphasis on connectivity between applications becoming important in the BI market.  Presently, most firms struggle to move data collected in one system into another for reporting or delivering to upper management. PARIS suggests that software products will begin to prioritize more and more the ability to collaborate across platforms—sharing data smoothly from one place to another. The PARIS Tech post discusses IT and end-users being able to use their preferred applications and a shared data set, which leads to the next interesting bit, their emphasis on collaboration and productivity.  The software products that will succeed in the future BI market will be those that allow people to easily collaborate because their applications will be connected.  They will also automate manual processes and calculations that are performed in Excel today. Improved collaboration and productivity influence peoples’ lives for the better and makes them enjoy their work more, while they also drive the business towards profitability. Read the full post on the PARIS Tech blog Read about using your preferred application and a shared data set with Olation....

Advice for CFOs: Invest in New Technology

“Top Technology Trends for Today’s CFO’s” is another insightful post from a blogger we frequently feature, Timo Elliott. In it he admits that the CFO relationship with the CEO and other business executives leaves something to be desired.  He recommends that CFOs invest in the latest technology, which will increase productivity with real-time updates and continuous forecasting. Elliott mentions a combination of new technology including: in-memory computing, big data, the cloud, and mobile. He homes in on a key point—that finance staff at large companies are extremely bogged down with just the basics of maintaining their financial reports. As Elliott puts it, “Staff have to spend too much time on basic duties and have no time to improve their understanding of the operational measures that drive and impact financial measures.” This lack of insight or understanding of how the operational measures drive and impact financial measures is the root of the relationship problem between CFOs and other business executives. Elliott suggests new in-memory computing technology because, “they reduce complexity by combining real-time actuals with budgeting and analysis in a single, integrated system. Financial data is stored just once, making almost every aspect of financial operations faster, simpler, cheaper, and more effective.” We couldn’t agree more, as developers of a new in-memory technology ourselves. The result of improved systems, improved speed, and better data is ultimately a better working relationship between business executives, and a more productive, effective workplace. Read Timo Elliott’s post here...
Skip to toolbar