The Minds Behind Data Warehousing and OLAP – 7 People Redefining Software
Seven influential architects and researchers shaped enterprise data warehousing, dimensional modeling, multidimensional analysis, data cubes, and OLAP practice.
TL;DR
Data warehousing separated operational data capture from analytical decision support, while OLAP made large collections explorable across business dimensions. Inmon emphasized integrated enterprise warehouses; Kimball systematized dimensional modeling; Devlin published an early warehouse architecture; Gray formalized the data cube; Codd helped popularize OLAP terminology; Thomsen and Pendse clarified multidimensional design and evaluation.[1][4][5]
Why you should read it anyway
Operational databases answer questions such as “what is the customer’s current balance?” Analytical systems answer “how did revenue change by product, geography, customer segment, and quarter?” Those are different workloads. Warehousing and OLAP became important because organizations needed to preserve history, integrate data from many systems, and let people analyze it without crippling transaction-processing databases.
Imagine where Data Warehousing and OLAP would be without them
Without warehouses and OLAP, organizations would have relied longer on periodic reports, spreadsheets, extracts, and direct queries against operational systems. Executive and analytical decision-making would still exist, but consolidating years of heterogeneous data and exploring it interactively would require much more manual work and custom software.
Time Estimate of how many years we would be hindered without them for human progress
Editorial counterfactual estimate: 5–10 years. Businesses already demanded management information, so analytical databases were inevitable. The acceleration came from shared architectures, dimensional vocabulary, cube operations, and evaluation frameworks that let an industry form around repeatable data-warehouse and OLAP practices rather than isolated reporting projects.
The 7 people behind Data Warehousing and OLAP
1. Bill Inmon
Why they matter: Inmon became one of the principal architects and evangelists of enterprise data warehousing, defining the warehouse as integrated, subject-oriented, time-variant, and nonvolatile data built for decision support. The EIM Institute describes him as a foundational figure in the data-warehouse concept.[1] His approach emphasized an integrated enterprise repository from which analytical structures could be derived.
2. Ralph Kimball
Why they matter: Kimball popularized a different but complementary design discipline centered on dimensional modeling, fact tables, dimension tables, star schemas, and business-process-oriented data marts.[2] His work made analytical schemas understandable to business users and performant for reporting. The Inmon-versus-Kimball debate shaped generations of warehouse architecture because it forced organizations to think explicitly about integration versus dimensional delivery.
3. Edgar F. Codd
Why they matter: Codd’s role in OLAP is later and more contested than his foundational relational work. In 1993, a vendor-sponsored paper associated his name with rules for online analytical processing and a multidimensional conceptual view.[3] Nigel Pendse later criticized those rules as overly vendor-linked.[7] Codd therefore belongs here as an influential naming and framing figure, not as the uncontested inventor of multidimensional analytics.
4. Jim Gray
Why they matter: Gray and collaborators formalized the relational data cube operator as a generalization of GROUP BY, cross-tabulation, drill-down, and subtotals across multiple dimensions.[4] That work gave multidimensional analytics a clean relational expression. Gray’s contribution connected large-scale database engineering with the mathematical operations analysts needed for warehouses and OLAP.
5. Barry Devlin
Why they matter: Devlin and colleagues at IBM Europe developed an early data-warehouse architecture in the mid-1980s and published it in 1988. Devlin’s retrospective describes that architecture as a foundation whose major components remain recognizable in later systems.[5] His importance is architectural: separating operational systems from integrated information structures for decision support.
6. Erik Thomsen
Why they matter: Thomsen wrote one of the major practitioner texts on OLAP, OLAP Solutions, covering multidimensional modeling, storage, calculation, decision support, and implementation methods.[6] His contribution was to turn a fragmented product category into a teachable engineering discipline for people designing multidimensional analytical systems.
7. Nigel Pendse
Why they matter: Pendse challenged vague or vendor-driven definitions of OLAP and proposed the FASMI test—Fast Analysis of Shared Multidimensional Information.[7] His work was partly analytical and evaluative rather than a database engine invention. He gave buyers and practitioners a concise framework for asking whether a system actually delivered the interactive multidimensional experience promised by OLAP marketing.
How they each differ from one another
Inmon and Devlin emphasized enterprise information architecture. Kimball emphasized dimensional models optimized for analytics. Gray contributed a formal multidimensional aggregation operator. Codd influenced OLAP terminology but his sponsored rules were controversial. Thomsen organized OLAP engineering practice, while Pendse created a product-independent evaluation definition. Their work spans architecture, schema design, algebra, terminology, and practice.
Final Take
Data warehousing changed the role of a database from recording the present to explaining the past. OLAP then made that history navigable by dimensions meaningful to people. Modern cloud warehouses, lakehouses, semantic layers, and BI tools look radically different in implementation, but they still inherit the same central ambition: integrate data once, then let many people ask new questions of it.
Works Cited
- 01EIM Institute — Bill Inmon eiminstitute.org
- 02Kimball Group — Dimensional Modeling Techniques kimballgroup.com
- 03OLAP.com — Codd's OLAP Rules olap.com
- 04
- 05
- 06Google Books — Erik Thomsen, OLAP Solutions books.google.com
- 07Nigel Pendse — What is OLAP? dssresources.com
CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.
Submit a research lead