NAME:SHRITEJ V SALVI

CASE STUDY:
DATA WAREHOUSE
WHAT IS DATA WAREHOUSE?

WHERE IS IT USE?

EXPLOITING THE DEFINATION

ARCHITECTURE OF DATA WAREHOUSE

EXAMPLE

INDEX
Accordi ng to W. H. I nmon: A data warehouse i s a subject-
ori ented, i ntegrated, ti me-variant, and non-volatile col l ecti on
of data i n support of management s deci si on maki ng process.
Dat a warehousi ng i s a process, not a product , f or assembl i ng and
managi ng dat a f rom vari ous sources f or t he purpose of gai ni ng a si ngl e
det ai l ed vi ew of part or al l of a busi ness .

The i nf ormat i on i n a DW must be compl et e, t i mel y, accurat e and
underst andabl e f or deci si on maki ng . Thi s requi res dat a t o be cl eaned,
f i l t ered, and t ransf ormed.

WHAT IS DATA WAREHOUSE?
Data warehouses are designed to help you analyze
data.
For example:
To learn more about your company's sales data, you can build a
warehouse that concentrates on sales.
Using this warehouse, you can answer questions like "Who was our best
customer for this item last year?" This ability to define a data warehouse
by subject matter, sales in this case, makes the data warehouse subject
oriented.
DATA WAREHOUSE: SUBJECT-ORIENTED
Integrati on i s cl osel y rel ated to subj ect ori entati on.
Data warehouses must put data from di sparate sources i nto
a consi stent format .
They must resol ve such probl ems as nami ng confl i cts and
i nconsi stenci es among uni ts of measure.
When they achi eve thi s, they are sai d to be i ntegrated.
EXAMPLE:
Mul ti pl e OLTP databases are used to i ntegrate and form
a data warehouse.

DATA WAREHOUSE : INTEGRATED
NON-VOLATLE means the data shoul d not be changed by
any one.
Thi s i s because i t i s a systemati c hi stori c representati on of
the data .
EXAMPLE:
suppose t he dat a i s changed by any one who i s anal yzi ng t he
dat a may cause a bi g probl em i n t he syst em as t he count erf ei t dat a can
be added i n dat a warehouse.
DATA WAREHOUSE : NON-VOLATILE
A DW usual l y has l ong t i me hori zon, si gni f i cant l y l onger t han t hat of
operat i onal syst ems.
Operational database: current value data.
DW data: provide information from a historical perspective (e.g. past 5-
10 years)
Every key st ruct ure i n t he Dat a Warehouse cont ai ns an el ement of
t i me, expl i ci t l y or i mpl i ci t l y
Operat i onal dat a may or may not cont ai n t i me el ement .
A dat a warehouse' s f ocus on change over t i me i s what i s meant by t he
t erm t i me vari ant .
EXAMPLE:
The dat a warehouse i s updat ed i n t i mel y manner.
DATA WAREHOUSE: TIME VARIANT
Data Warehouse, a col l ecti on of data desi gned to support
management deci si on maki ng.
Data warehouse i s a rel ati onal database desi gn for query and
anal ysi s rather then transacti on.
I t usual l y contai ns hi stori cal data deri ved from transacti on data,
but i t can i ncl ude data from other sources.
I t separates anal ysi s workl oad from transacti on workl oad and
enabl es an organi zati on to consol i date data from several
sources.
REALWORLD EXAMPLE: I t s l i ke the smal l handbook i n whi ch
person j ot down hi s experi ence.
WHERE IT IS USE?
There are three types of data warehouse archi tecture desi gn
as fol l ow:
Data warehouse archi tecture (BASIC)
Data Warehouse Architecture (with a Staging Area)
Data Warehouse Architecture (with a Staging Area and Data
Marts).

ARCHITECTURE OF DATA WAREHOUSE
DATA WAREHOUSE ARCHITECTURE
(BASIC)

The metadata and raw data of a traditional OLTP system is present, as is an additional type of
data, summary data. Summaries are very valuable in data warehouses because they pre-
compute long operations in advance.
For Example : A typical data warehouse query is to retrieve something like August sales. A
summary in Oracle is called a materialized view.
DATA WAREHOUSE ARCHITECTURE
(WITH A STAGING AREA)
You need to clean and process your operational data before putting it into the
warehouse.
You can do this programmatically, although most data warehouses use a staging
area instead.
A staging area simplifies building summaries and general warehouse management .
Data Warehouse Architecture
(with a Staging Area and Data Marts).
You may want to customize your warehouse's architecture for different groups within
your organization. You can do this by adding data marts, which are systems designed
for a particular line of business
An Example :
Where purchasing, sales, and inventories are separated. In this example, a
financial analyst might want to analyze historical data for purchases and sales.
I n or der t o st or e dat a, over t he year s, many appl i cat i on desi gner s i n each
br anch have made t hei r i ndi vi dual deci si ons as t o how an appl i cat i on and
dat abase shoul d be bui l t .
So sour ce syst ems wi l l be di f f er ent i n nami ng convent i ons, var i abl e
measur ement s, encodi ng st r uct ur es, and physi cal at t r i but es of dat a.
EXAMPLE:
Consi der a bank t hat has got sever al br anches i n sever al count r i es,
has mi l l i ons of cust omer s and t he l i nes of busi ness of t he ent er pr i se ar e
savi ngs, and l oans.
The f ol l owi ng exampl e expl ai ns how t he dat a i s i nt egr at ed f r om sour ce syst ems
t o t ar get syst ems.
EXAMPLE :
System Name Attribute Name Column Name Datatype Values
Source System 1
Customer Application
Date
CUSTOMER_APPLICATION
_DATE
NUMERIC(8,0) 11012005
Source System 2
Customer Application
Date
CUST_APPLICATION_DATE DATE 11012005
Source System 3 Application Date APPLICATION_DATE DATE 01NOV2005
EXAMPLE OF SOURCE DATA

In the aforementioned example, attribute name, column name, datatype and values are
entirely different from one source system to another. This inconsistency in data can be
avoided by integrating the data into a data warehouse with good standards.
Target System Attribute Name Column Name Datatype Values
Record #1 Customer Application Date
CUSTOMER_APPLICATION_
DATE
DATE 01112005
Record #2 Customer Application Date
CUSTOMER_APPLICATION_
DATE
DATE 01112005
Record #3 Customer Application Date
CUSTOMER_APPLICATION_
DATE
DATE 01112005
EXAMPLE OF TARGET DATA
(DATA WAREHOUSE)
In the above example of target data, attribute names, column names, and datatypes are
consistent throughout the target system. This is how data from various source systems
is integrated and accurately stored into the data warehouse.