Data warehouseconceptsandarchitecture

Data Warehouse

Concepts
&
Architecture

© Principle Partners, Inc.
Info@PrinciplePartners.Com
Page 1
PP I

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.

Page 2
PP I


Why Do We Need A Data Warehouse ?

We Can Only
See - What We
Can See !

Page 3
PP I


Why Do We Need A Data Warehouse ?

BETTER !
FASTER ! FUNCTIONALLY COMPLETE !
CHEAPER !

Page 4
PP I

Data Warehouse Development Perspective

Data Driven Vs. Function Driven

A/P
O/P
Order
Processing
Data
EIS
Data
DSS

Page 5
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!

Page 6
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 !

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

Page 8
PP I


Subject Oriented
Data is Integrated and Loaded by Subject

Cust 2001

2003
Prod D/W
Data
2002

O/P
2002

A/R

Page 9
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

Page 10
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

Page 11
PP I


Non-Volatile

Operational System Data Warehouse

• “CRUD” Actions • No Data Update

Insert
Read
Load
Create
Read Read

Update Replace Read

Delete Read

Page 12
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 ria
Record Data
C rite
d
L oa
HR e
o us Data
a reh Mart
A/R W D/W Load Loads
a ta
D
Best System of Read D/W
Record Data

Page 13
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

Page 14
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
Tim Variant
e
Age Of The Data: Current, Near Term Historic
(Today, Last W eek’s) (Last M onth, Qtrly, Five
Years)
Prim Use:
ary Day-To-Day Decisions Long-Term Decisions
Tactical Reporting Strategic Reporting
Current Operational Results Trend Detection
Frequency Of Load: Twice Daily , Daily, W eekly W eekly, M onthly, Quarterly

Page 15
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 ODS • Populated ODS

Page 16
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

Page 17
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
Model Requirements
Data

Operational
Data Store
Physical Tactical Business
Data Model Reqmts & Structures
Load

Current Data Whse
Database Requirements
Current Structure
Physical Transition
Model Model

Page 18
PP I

Sources of Data Warehouse Data

Archives
(Historic Data)

Current Systems
of Record
(Recent History)

Enterprise
Data Warehouse
Operational
Transactions
(Future Data Source)

Page 19
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)

Page 20
PP I


Inappropriate Uses of Data Warehouse Data

• Replace Operational Systems

• Replace Operational Systems’ Reports

• Analyze Current Operational Results

Page 21
PP I


Levels of Granularity of Data Warehouse Data

•Atomic (Transaction)

•Lightly Summarized

•Highly Summarized

Page 22
PP I


Options for Viewing Data

• Text

9 0
8 0
7 0
6 0
5 0

• 4
3
2
1
0
0
0
0
0
1 s t 2 n d 3 rd 4 th
Q tr Q tr Q tr Q tr

•

Page 23
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

Page 24
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

Page 25
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

Page 26
PP I


Questions and Answers

Page 27
PP I

Data warehouseconceptsandarchitecture

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (19)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie Data warehouseconceptsandarchitecture

Ähnlich wie Data warehouseconceptsandarchitecture (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Data warehouseconceptsandarchitecture