← New search

Other meanings of Online analytical processing

Data management

Online analytical processing

Online analytical processing (OLAP) is data-analysis technology for interactively examining multidimensional information. It lets users compare measures such as revenue or units across dimensions such as product, geography, and time, while rapidly changing levels of detail without writing a separate query for every view.

1993
term formalized
Codd, Codd and Salley described OLAP in a widely cited industry paper
3 core actions
slice, dice, drill
Common ways to navigate multidimensional data
2 main models
MOLAP and ROLAP
Multidimensional and relational implementation families
1

Definition and purpose

OLAP is designed for interactive analysis rather than routine transaction processing. It organizes numerical measures against descriptive dimensions, allowing a user to ask questions such as how quarterly sales vary by region and product category. The defining idea is not merely a dashboard or a database, but rapid examination of many possible aggregations and perspectives. The term became prominent in the early 1990s, when relational databases and data warehouses were increasingly separated from operational systems.1

An OLAP environment commonly supports a business vocabulary, governed calculations, and precomputed or efficiently generated summaries. Analysts can move from an annual total to quarters, months, or individual days, then return to a higher-level view. This makes OLAP useful for budgeting, forecasting, supply-chain analysis, financial reporting, and other tasks in which the question changes during investigation.

2

Cubes, dimensions, and operations

OLAP represents analysis as a multidimensional cube, even when the underlying implementation is not literally a cube. A cube may contain measures such as sales amount, margin, and inventory, with dimensions including time, location, customer, and product. Dimensions usually contain hierarchies—for example, day–month–quarter–year or city–state–country—that provide controlled paths through the data.2

Core operations include slice, which selects one dimension value; dice, which selects ranges or sets across dimensions; drill-down, which reveals finer detail; and roll-up, which aggregates to a coarser level. Pivoting changes the arrangement of dimensions in a report. These operations are conceptually simple, but totals can become misleading when dimensions contain duplicate, incomplete, or non-additive facts such as percentages and inventory balances.

3

Architectures and analytical workflow

OLAP systems differ mainly in where they store data and how they produce aggregations. MOLAP stores multidimensional structures or specialized summaries and can provide fast navigation over a modeled cube. ROLAP retains data in relational tables and translates analytical requests into SQL, benefiting from relational scalability and existing warehouse infrastructure. Hybrid approaches combine these strategies, while modern columnar and in-memory engines often blur the older boundaries.

A typical workflow extracts and cleans data, loads a data warehouse or lakehouse, defines dimensions and measures, builds aggregates or indexes, and presents results through a reporting client. Performance depends on more than storage: dimensional design, query pruning, caching, partitioning, concurrency, and the freshness of loads all matter. OLAP therefore complements, rather than replaces, transactional systems, which are optimized for frequent updates and narrowly defined records.

4

Lesser-known aspects

OLAP’s less visible difficulties arise from semantics, not from the cube metaphor. The classic data-cube literature showed that aggregating across several dimensions can generate a large family of subtotals, including cuboids and the complete data cube lattice.3 Materializing every summary is often impractical, so systems select useful aggregates or compute some results at query time.

Not every measure is additive: revenue can usually be summed across products and periods, whereas a ratio, percentage, or average may require its underlying components. Slowly changing dimensions, late-arriving facts, multiple currencies, fiscal calendars, and ragged organizational hierarchies create further edge cases. Security can also operate at the dimensional level, restricting a user to particular regions or business units. These details explain why a visually simple pivot table depends on careful metadata, data governance, and validation.24

Glossary

Measure
A numeric value analyzed in an OLAP model, such as revenue, quantity, cost, or margin.
Dimension
A category used to organize and filter measures, such as time, product, customer, or geography.
Hierarchy
An ordered set of levels within a dimension, such as day, month, quarter, and year.
MOLAP
Multidimensional OLAP, in which specialized multidimensional storage or aggregates support analysis.
ROLAP
Relational OLAP, in which analytical requests operate on relational warehouse tables, commonly through SQL.
Data cube
A conceptual structure containing measures summarized across combinations of dimensions and their levels.

OLAP is a family of analytical techniques and implementations, not a single database product or file format.