Vous êtes sur la page 1sur 17

DATA WAREHOUSING

ARCHITECTURE

DATA WAREHOUSING ARCHITECTURE

Oracle

SQL Server

Heterogeneous
Transactional
databases

Cleanse, Integrate
and Transform the
incoming data

Excel Sheet
Staging Area

XML Files

Data Warehouse

DATA WAREHOUSING ARCHITECTURE

Business Intelligence
Engines

Data Warehouse

Decision Makers

DATA WAREHOUSING
APPROACHES

APPROACH #1

Cleanse, Integrate
and Transform the
incoming data

Staging Area
OLTP
Databases

Data Warehouse

DATA WAREHOUSE

Periodical BULK
Inserts
Fewer Tables &
Fewer Joins

Read-only,
Exclusive for Selects

Data Warehouse

Sales

Subject
Oriented

1998

2005

Historical
Information

DATA WAREHOUSE

Subject Oriented

Integrated

Non Volatile

Time Variant

Consistent

Data Warehouse

CHARACTERISTIC OF DWH

Subject Oriented

Data that gives information about a particular subject


instead of about a company's ongoing operations should be
stored in Data Warehouse i.e., information is presented
according to specific subjects or areas of interest, not
simply as computer files. Data is manipulated to provide
information about a particular subject.

Integrated

Data when loaded into Data Warehouse from heterogeneous


sources it should be in unique format i.e., integrated.

CHARACTERISTIC OF DWH cont.

Non Volatile

Time Variant

Data is stable in a data warehouse i.e., stable information that doesnt


change each time an operational process is executed. Information is
consistent regardless of when the warehouse is accessed. Once data
is loaded into the Data Warehouse that data is never removed. This
enables management to gain a consistent picture of the business.

It is mandatory that all data in the data warehouse should be identified


with a particular time period. Containing a history of the subject, as
well as current information. Historical information is an important
component of a data warehouse.

Consistent

Data should be consistent in Data Warehouse whenever in future it is


updated.

DATA WAREHOUSE - ARCHITECTURE

Oracle

Heterogeneous
Transactional
databases

SQL Server
Cleanse, Integrate
and Transform the
incoming data
Excel Sheet
Staging Area

XML Files

Data Warehouse

APPROACH #2

Data Mart

Data Warehouse

Data Mart

DATA MART
Data Mart is a subset of a Warehouse
Data Mart contains Departmental
Data Mart

Corporate Data where as the Warehouse


holds Enterprise Level data
Summation of ALL Data Marts need
NOT necessarily be a Warehouse

Data Warehouse

Marts enhance Reporting Performance when


looking at part of the corporate data

Data Mart

DATA WAREHOUSE v/s DATA MART

Subject Oriented
Integrated
Non Volatile
Time Variant
Data Warehouse

Consistent

W
A
R
E
H
O
U
S
E

Department Oriented
Data Mart

D
A
T
A
M
A
R
T

APPROACH #2

Centralized as well
as Decentralized Data

High volumes of data,


Huge maintenance

Complex ETL

Departmental data
is easily accessible

More clear insight of


Business

APPROACH #3
NO
Warehouse !!!

Staging
Area

Data Mart

Data Mart
OLTP
Databases

APPROACH #3

Centralized as well
as Decentralized Data

Complex ETL

Departmental data
is easily accessible

Suitable
Suitablefor
for
Entry
EntryLevel
LevelBI
BI
Less volumes of data,
Less maintenance

NO Enterprise level
Business insight

Thank you

Vous aimerez peut-être aussi