Data Warehouse Concepts & Architecture: © Principle Partners, Inc

Data Warehouse
Concepts
&
Architecture
PP I
© Principle Partners, Inc. Page 1
Info@PrinciplePartners.Com
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 COMPLETE !
CHEAPER !
PP I
Data Warehouse Development Perspective
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 Accessible
• 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 Repository
of Historic Data.
It Is Developed in an Evolutionary Process

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 Business • Designated Time Frame

Today (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
Update Replace Read
Delete Read
PP I
Data Warehouse Environment Architecture
Contains Integrated Data From Multiple Legacy Applications
Update
A/P
Insert Data
Load Mart
O/P
Integration Read
ODS
Replace
Pay Data
Criteria Mart
All Or Part Delete
Of System of
Mktg
teri a
Record Data i
d Cr
a
HR e Lo
ous Data
a reh Mart
A/R a W D/W Load Loads
t
Da
Best System of Read D/W
Record Data
PP I
Meta Data - Map of Integration
The Data That Provides the “Card Catalogue” Of
References For All Data Within The Data Warehouse
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 • Scope Definition

• Define Business Reqmts • Logical Data Model
• Define System of Record • Physical Database Data
Data Model
• Define Operational Data • Operational Data Store
Store Reqmts Model
• Map SOR to ODS • ODS Map
• Acquire / Develop • Extract Tools and
Extract Tools Software
• Extract Data & Load • Populated ODS
ODS
PP I
Building The Data Warehouse
(Continued)
Tasks Deliverables
• Define D/W Data Reqmts • Transition Data Model

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

Database Current Structure Requirements
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 Data
• Produce Reports For Long Term Trend Analysis
• Produce Reports Aggregating Enterprise Data
• Produce Reports of Multiple Dimensions

(Earned revenue by month by product by branch)
PP I
Inappropriate Uses of Data Warehouse Data
• Replace Operational Systems
• Replace Operational Systems’ Reports
• Analyze Current Operational Results
PP I
Levels of Granularity of Data Warehouse Data
•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 3 rd 4 th
Qtr Qtr Qtr Qtr
PP I
Next Steps In Data Warehouse Evolution
• 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 Repository

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 & Architecture: © 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 & Architecture: © Principle Partners, Inc

Uploaded by

Copyright:

Available Formats

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 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 Accessible

• Provide Information - For Our Businesses

• Start Managing Knowledge

• So Our Business Partners Will Gain Wisdom !

Data Warehouse Definition

It Is Developed in an Evolutionary Process

Operational System Data Warehouse

• View of The Business • Designated Time Frame

• Operational Time Frame • One Snapshot Per Cycle

• Key Need Not Have Date • Key Includes Date

Order Processing Order ID = 10

HR System Sex = M/F

Operational System Data Warehouse

• “CRUD” Actions • No Data Update

Update Replace Read

ODS Vs. Data Warehouse

Operational Data Store Data Warehouse

Characteristics: Data Focused Integration Subject Oriented

• Define Project Scope • Scope Definition

• Define D/W Data Reqmts • Transition Data Model

Relationship Among Data Warehouse Data Models

Current Data Whse

Appropriate Uses of Data Warehouse Data

• Produce Reports For Long Term Trend Analysis

• Produce Reports Aggregating Enterprise Data

• Produce Reports of Multiple Dimensions

Inappropriate Uses of Data Warehouse Data

• Replace Operational Systems

• Replace Operational Systems’ Reports

• Analyze Current Operational Results

Levels of Granularity of Data Warehouse Data

Next Steps In Data Warehouse Evolution

• Use It - Analyze Data Warehouse Data

• Determine Additional Data Requirements

• Define Sources For Additional Data

• Add New Data (Subject Areas) to

Future Trends In Data Warehouse

• Increase Competitive Advantage

• Integration into Supply Chain & e-Business

A Data Warehouse Is A Structured Repository

It Is: • Subject Oriented

Questions and Answers

You might also like