Data Warehouse Concepts & Architectur E: © Principle Partners, Inc

Data
Warehouse
Concepts
&
Architectur
e
PP I
© Principle Partners, Inc.
Info@PrinciplePartners.Com Page 1
Data Warehouse Concepts
Topics To Be Discussed:
• Why Do We Need A Data Warehouse ?
• The Goal Of A Data Warehouse ?
• What Exactly Is A Data Warehouse ?
• Comparison Of A Data Warehouse And

An Operational Data Store.
• Data Warehouse Trends.
PP I
Why Do We Need A Data Warehouse ?
We Can Only
See - What We
Can See !
PP I
Why Do We Need A Data Warehouse ?
BETTER !
FASTER ! FUNCTIONALLY COMP
CHEAPER !
PP I
Data Warehouse Development Perspect
Data Driven Vs. Function Driven
A/P
O/P
Order
Processing
Data
EIS
Data
DSS
PP I
What Do We Need To Do ?
Use Operational Legacy Systems’ Data:

To Build Operational Data Store,
That Integrate Into Corporate Data
Warehouse,
That Spin-off Data Marts.
Some May Tell You To Develop These In Reverse!
PP I
Our Goal for A Data Warehouse ?
• Collect Data-Scrub, Integrate & Make It Acc
• Provide Information - For Our Businesses
• Start Managing Knowledge
• So Our Business Partners Will Gain Wisdom
PP I
Data Warehouse Definition
A Data Warehouse Is A Structured Repos

of Historic Data.
It Is Developed in an Evolutionary Proces

By Integrating Data From Non-integrated
Legacy Systems.
It Is Usually:
• Subject
Oriented
• Integrated
• Time Variant
• Non-volatile
PP I
Subject Oriented
Data is Integrated and Loaded by Subject
Cust
1996
1996
Prod D/W
Data
1997
O/P
1998
A/R
PP I
Time Variant
Operational System Data Warehouse
• View of The • Designated Time

Business Today Frame (3 - 10
Years)
• Operational Time
Frame • One Snapshot Per
Cycle
• Key Need Not

Have Date • Key Includes Date
PP I
Integrated
Operational Systems
Order Processing Order ID = 10

D/W
Accounts Receivable Order ID = 12
Order ID = 16
Product Management Order ID = 8
HR System Sex = M/F

D/W
Payroll Sex = 1/2
Sex = M/F
Product Management Sex = 0/1
PP I
Non-Volatile
Operational System Data Warehouse
• “CRUD” Actions • No Data Update
Insert
Read
Load
Create
Read Read
Replace Read
Update
Delete Read
PP I
Data Warehouse Environment Architectu

Contains Integrated Data From Multiple Legacy Applic
Update
A/P
Insert
Data
Load Mart
O/P
Integration Read
ODS
Replace
Pay Criteria Data
Mart
Delete
All Or Part
Of System of
Mktg Record Data
ter ia
C ri
HR oad
e L
ous Data
areh Mart
W Loads
A/R ta D/W Load
Da
Best System of D/W

Record Data Read
PP I
Meta Data - Map of Integration

The Data That Provides the “Card Catalogue” Of
References For All Data Within The Data Warehou
System of Record
Data Source
D/W Structure
Source Data Structure
Definition
Allowable
Domains
Aliases
Data Relationships
PP I
ODS Vs. Data Warehouse
Operational Data Store Data Warehouse
Characteristics: Data Focused Integration Subject Oriented

From Transaction Processing Integrated
Focused Systems Non-Volatile
Time Variant
Age Of The Data: Current, Near Term Historic
(Today, Last Week’s) (Last Month, Qtrly, Five
Years)
Primary Use: Day-To-Day Decisions Long-Term Decisions
Tactical Reporting Strategic Reporting
Current Operational Results Trend Detection
Frequency Of Load: Twice Daily , Daily, Weekly Weekly, Monthly, Quarterly
PP I
Building The Data Warehouse
Tasks Deliverables
• Define Project • Scope Definition

Scope • Logical Data
• Define Business Model
Reqmts • Physical Database
• Define System of Data Model
Record Data • Operational Data
• Define Store Model
Operational Data • ODS Map
Store Reqmts
• Extract Tools and
• Map SOR to ODS Software
• Acquire / Develop • Populated ODS
Extract Tools
• Extract Data &
Load ODS
PP I
Building The Data Warehouse

(Continued)
Tasks Deliverables
• Define D/W Data • Transition Data

Reqmts Model
• Map ODS to D/W • D/W Data
• Document Integration Map
Missing Data • To Do Project List
• Develop D/W DB • D/W Database
Design Design
• Extract and • Integrated D/W
Integrate D/W Data Extracts
Data • Initial Data Load
• Load Data • On-going Data
Warehouse Access and
• Maintain Data Subsequent Loads
Warehouse
PP I
Relationship Among Data Warehouse Data Models
Business Business
Partner Business Requirements Requirements
Knowledge Logical
& Wisdom Model
Data
Warehouse Strategic
Validation Business
of Current
Physical RequirementsStructured
Model Requirements
Data
Operational
Data Store
Physical
Model Tactical Business
Data Reqmts & Structures
Load
Current Data Whse

Database Requirements
Current Structure
Physical Transition
Model Model
PP I
Sources of Data Warehouse Data
Archives
(Historic Data)
Current Systems
of Record
(Recent History)
Enterprise
Data Warehouse
Operational
Transactions
(Future Data Source)
PP I
Appropriate Uses of Data Warehouse D
• Produce Reports For Long Term Trend Analy
• Produce Reports Aggregating Enterprise Da
• Produce Reports of Multiple Dimensions

(Earned revenue by month by product by br
PP I
Data Warehouse
Concepts
Inappropriate Uses of Data Warehouse
• Replace Operational Systems
• Replace Operational Systems’ Rep
• Analyze Current Operational Resu
PP I
Levels of Granularity of Data Warehouse
•Atomic (Transaction)
•Lightly Summarized
•Highly Summarized
PP I
Options for Viewing Data
• Text
90
80
70
60
• 50
40
30
20
10
0
1s t 2nd 3rd 4th
Qtr Qtr Qtr Qtr
PP I
Next Steps In Data Warehouse Evolutio
• Use It - Analyze Data

Warehouse Data
• Determine Additional Data

Requirements
• Define Sources For Additional

Data
• Add New Data (Subject Areas)

to
Data Warehouse
PP I
Future Trends In Data Warehouse
• Increased Data Mining

Exploration
Prove Hypothesis
• Increase Competitive Advantage

(i.e., Identify Cross-selling
Opportunities)
• Integration into Supply Chain & e-

Business
PP I
Summary
A Data Warehouse Is A Structured Repos

of Historic Data.
It Is:
• Subject
Oriented
• Integrated
• Time Variant
• Non-volatile
It
Contains:
• Business Specified Data,
To Answer Business Questions
PP I
Questions and Answers
PP I

Data Warehouse Concepts & Architectur E: © Principle Partners, Inc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Warehouse Concepts & Architectur E: © Principle Partners, Inc

Uploaded by

Copyright:

Available Formats

Data

• Why Do We Need A Data Warehouse ?

• The Goal Of A Data Warehouse ?

• What Exactly Is A Data Warehouse ?

• Comparison Of A Data Warehouse And

• Data Warehouse Trends.

Why Do We Need A Data Warehouse ?

Why Do We Need A Data Warehouse ?

Data Warehouse Development Perspect

Data Driven Vs. Function Driven

Use Operational Legacy Systems’ Data:

Some May Tell You To Develop These In Reverse!

Our Goal for A Data Warehouse ?

• Collect Data-Scrub, Integrate & Make It Acc

• Provide Information - For Our Businesses

• Start Managing Knowledge

• So Our Business Partners Will Gain Wisdom

Data Warehouse Definition

A Data Warehouse Is A Structured Repos

It Is Developed in an Evolutionary Proces

Data is Integrated and Loaded by Subject

Operational System Data Warehouse

• View of The • Designated Time

• Key Need Not

Order Processing Order ID = 10

HR System Sex = M/F

Operational System Data Warehouse

• “CRUD” Actions • No Data Update

Data Warehouse Environment Architectu

Best System of D/W

Meta Data - Map of Integration

ODS Vs. Data Warehouse

Operational Data Store Data Warehouse

Characteristics: Data Focused Integration Subject Oriented

Building The Data Warehouse

• Define Project • Scope Definition

Building The Data Warehouse

• Define D/W Data • Transition Data

Relationship Among Data Warehouse Data Models

Current Data Whse

Sources of Data Warehouse Data

Appropriate Uses of Data Warehouse D

• Produce Reports For Long Term Trend Analy

• Produce Reports Aggregating Enterprise Da

• Produce Reports of Multiple Dimensions

Inappropriate Uses of Data Warehouse

• Replace Operational Systems

• Replace Operational Systems’ Rep

• Analyze Current Operational Resu

Levels of Granularity of Data Warehouse

Options for Viewing Data

Next Steps In Data Warehouse Evolutio

• Use It - Analyze Data

• Determine Additional Data

• Define Sources For Additional

• Add New Data (Subject Areas)

Future Trends In Data Warehouse

• Increased Data Mining

• Increase Competitive Advantage

• Integration into Supply Chain & e-

A Data Warehouse Is A Structured Repos

Questions and Answers

You might also like