OLAP Cube Design
Online Analytical Processing Cube Design · Also known as: OLAP, multidimensional cubes
OLAP (Online Analytical Processing) cube design is the practice of structuring multidimensional data for interactive analysis. Formalized by Codd and colleagues in 1993, OLAP cubes organize facts (measurements) along multiple dimensions (attributes) enabling rapid pivoting, drilling, and aggregation for business analysis.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Design OLAP cubes when analytical queries require flexible navigation across multiple dimensions, when users need rapid response times for ad-hoc analysis, or when queries are characterized by aggregation along multiple paths. Assumptions include stable dimensions and the ability to identify key hierarchies upfront.
Strengths & limitations
- Enables interactive analysis with rapid response times for multi-dimensional queries
- Pre-computed aggregations eliminate need to recalculate sums across many rows
- Intuitive metaphor (rotating and slicing) matches how business users think about data
- Cube size grows exponentially with number of dimensions and granularity levels
- Sparse cubes with many empty cells waste storage and computation
- Adding new dimensions or changing hierarchies requires expensive cube rebuilds
Frequently asked
What is the difference between OLAP and ROLAP?
OLAP typically refers to specialized multidimensional databases (MOLAP) with optimized storage. ROLAP (Relational OLAP) uses standard relational databases with dimensional schemas, storing raw data and computing aggregations on demand. ROLAP is more flexible but typically slower.
How do I decide which aggregations to pre-compute?
Focus on high-level summaries frequently queried (e.g., sales by country and month). Use tools to analyze query patterns and storage constraints. Pre-compute aggregations that significantly improve response time; compute others on demand.
What is a dimension hierarchy and why is it important?
A hierarchy defines rollup relationships (e.g., Product > Category > Brand). Hierarchies enable drilling (down to detail) and rolling up (to summary). Properly designed hierarchies make cube navigation intuitive for business users.
How do I handle slowly changing dimensions in a cube?
Track dimension changes using effective dating (valid from/to) or surrogate keys. This allows historical queries to show the correct dimension attributes at each point in time, avoiding misleading rollups across time.
Sources
- Codd, E. F., Codd, S. B., & Salley, C. T. (1993). Providing OLAP to user-analysts: An IT mandate. Arbor Software. link ↗
- Pedersen, T. B., Jensen, C. S., & Dyreson, C. E. (1999). A foundation for capturing the semantics of temporal multidimensional databases. Proceedings of the 5th ACM SIGMOD Workshop on Research Issues in Data Mining and Knowledge Discovery. link ↗
- Kimball, R. (1996). The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses. New York: John Wiley & Sons. link ↗
How to cite this page
ScholarGate. (2026, June 3). Online Analytical Processing Cube Design. ScholarGate. https://scholargate.app/en/information-systems/olap-cube-design
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Data WarehousingInformation Systems↔ compare