Inmon Vs Kimball 1
Inmon Vs Kimball 1
Data Warehouse:
The Choice of
Inmon versus Kimball
Ian Abramson
IAS Inc.
Agenda
The 2 Approaches
D Bill
Similarities
Differences
Choices
DW History
1990
D
1996
D
2002
D
Subject-oriented
The data in the database is organized so that all the data elements relating to the
same real-world event or object are linked together;
Time-variant
The changes to the data in the database are tracked and recorded so that reports
can be produced showing changes over time;
Non-volatile
Data in the database is never over-written or deleted - once committed, the data
is static, read-only, but retained for future reporting; and
Integrated
Ref: wikipedia
I AS Inc
"...the data warehouse is nothing more than the union of all the data
marts",
Kimball indicates a bottom-up data warehousing methodology in which
individual data marts providing thin views into the organizational data
could be created and later combined into a larger all-encompassing
data warehouse.
"You can catch all the minnows in the ocean and stack them together
and they still do not make a whale,"
This indicates the opposing view that the data warehouse should be
designed from the top-down to include all corporate data. In this
methodology, data marts are created only after the complete data
warehouse has been created.
IAS Inc
IAS Inc
I AS Inc
Warehouses:
DScope
independent
Centralized or Enterprise
Planned
DData
Specific
application
Decentralized by group
Organic but may be planned
DData
Historical,
detailed, summary
Some denormalization
DSubjects
Some
Multiple
subjects
DSource
Single
DSource
DOther
Few
DOther
Flexible
Restrictive
Data
Project
oriented
Long life
Single complex structure
Marts:
DScope
Application
Many
Data
oriented
Short life
Multiple simple structures that may
form a complex structure
I AS Inc
data warehouse
D Departmental
D Individual
IAS Inc
Delinquent Customers
IAS Inc
Inmon Modeling
Three levels of data modeling
D ERD
model (*DIS*)
D Physical
data model
I AS Inc
I AS Inc
I AS Inc
Staging
Data Access
Source
DB 1
Source
DB 2
Landing
Staging Area
Data Marts
File or
External Data
Cubes
14
I AS Inc
with tables
Facts
Dimensions
D Facts
contain metrics
D Dimensions contain attributes
I AS Inc
Staging
The Data
Warehouse
Data Access
Source
DB 1
Workstation Group
Source
DB 2
Landing
Staging Area
End Users
File or
External Data
Cubes
16
IAS Inc
IAS Inc
IAS Inc
IAS Inc
Kimballs Philosophy
Make data easily accessible
Present the organizations information
consistently
Be adaptive and resilient to change
Protect information
Service as the foundation for
improved decision making.
IAS Inc
Inmon
D Will
I AS Inc
Inmon:
D Subject-Oriented
D Integrated
D Non-Volatile
D Time-Variant
D Top-Down
D Integration Achieved via an Assumed Enterprise
D Characterizes Data marts as Aggregates
Kimball
D Business-Process-Oriented
D Bottom-Up and Evolutionary
D Stresses Dimensional Model, Not E-R
D Integration Achieved via Conformed Dimensions
D Star Schemas Enforce Query Semantics
22
Data Model
I AS Inc
The Comparison
(Methodology and Architecture)
Inmon
Kimball
Overall approach
Top-down
Bottom-up
Architectural structure
Enterprise-wide DW
feeds departmental DBs
Complexity of method
Quite complex
Fairly simple
Reference: http://www.bi-bestpractices.com/view-articles/4768
I AS Inc
The Comparison
(Data Modeling)
Inmon
Kimball
Data orientation
Process oriented
Tools
Dimensional modeling;
departs from traditional
relational modeling
Low
High
Reference: http://www.bi-bestpractices.com/view-articles/4768
I AS Inc
The Comparison
(Dimensions)
Inmon
Kimball
Timeframe
Slowly Changing
Methods
Timestamps
Dimension keys
Reference: http://www.bi-bestpractices.com/view-articles/4768
I AS Inc
time
time
A point in time
Snapshot
I AS Inc
D Type
II
D Type
III
I AS Inc
The Comparison
(Philosophy)
Inmon
Kimball
Primary Audience
IT
End Users
Place in the
Organization
Objective
Reference: http://www.bi-bestpractices.com/view-articles/4768
IAS Inc
How to Choose?
Characteristic Favors Kimball Favors Inmon
Nature of the
organization's
decision support
requirements
Tactical
Strategic
Data integration
requirements
Individual business
areas
Enterprise-wide integration
Structure of data
Business metrics,
performance
measures, and
scorecards
Scalability
Need to adapt to
Growing scope and changing
highly volatile needs requirements are critical
within a limited scope
IAS Inc
How to Choose?
Characteristic Favors Kimball Favors Inmon
Persistency of data
Small teams of
generalists
Time to delivery
Cost to deploy
IAS Inc
References
bestpractices.com/view-articles/4768
IAS Inc