The document discusses the purpose and history of data warehousing. It defines a data warehouse as a centralized, well-managed environment for storing high-value data from various sources. The data warehouse processes this data into a format optimized for analysis and information processing. The data warehouse has evolved from mainframe-based systems in the 1970s to today's cost-effective solutions embedded in software. A data warehouse is not defined by its size but by its functionality and ability to meet business objectives through consolidated, consistent data.

1. The Data Warehouse:
Home for Your Submitted
by:
DataLOGO
Assets Rishabh
Dogra
1/26/2012 1
R3-

2. Outline
Expectations
Data
Warehouse /
Data Dump
The
Historical
Perspective
Is Bigger
the Better
History
About
Data
wareho
use
1/26/2012 2

3. What Is A Data Warehouse?
“It is a home for high-value data, or data assets, that
originates in corporate applications”
1/26/2012 3

4. What Is Data Warehousing?
“Data warehousing is the coordinated, architected, and periodic
copying of data from
various sources, both inside and outside the enterprise, into
an environment optimized for analytical and informational
processing despite platform, application, organizational, and
other barriers.”
 A Data Warehouse Is
 Centralized
 Well-managed Environment
 Consistent And Redundant Processes
 Open And Scalable Architecture
 Process The Data Into Information
1/26/2012 4

5. History
2000’s
The Adult
1990’s
The Adolescent
1980’s
The Birth
1970’s
The
Preparation
•Dominated by •PCs PCs & •Computing •Cost Effective
Mainframe. More PC’s went Solutions
•Continually •Islands of Data. Mainstream •Data
bothering the •Concept of •Client/ warehouse
Data-processing DDMS & RDMS server solutions
Department. •Birth Place for technology embedded in
•Concept of data warehouse software suits
Tera Data Innovations •Plug
1/26/2012 5
Compatible

6. Is a Bigger Data Warehouse a Better
Data Warehouse?
The size of a data warehouse is a characteristic — “almost a
by-product”
— of a data warehouse; it’s not an objective.
The
Function Contents
ality
Business
Volume
Objective
1/26/2012 6

7. Historical Perspective
TIME LAG
1/26/2012 7

8. It’s Data Warehouse, Not Data
Dump
1/26/2012 8

9. Expectations from Data
Warehouse
Tool To Make Better Business Decisions
Who are our lowest or
highest margin customers ?
Who are my customers
What is the most and what products
effective distribution are they buying?
channel?
What promotions Which customers
have the biggest impact are most likely to go
on revenue? to the competition ?
What impact will new
products/services have on
revenue and margins?
1/26/2012 9

10. Expectations from Data
Warehouse
Finding data at your Finger
Tips
1/26/2012 10

11. Expectations from Data
Warehouse
Facilitating Better Communications Among
Different Business Units
•IT - BUSINESS ORGANIZATION COMMUNICATION
IT Side Business Users
Issues Complaints
 Unrealistic  Developers have no
idea about business
request
 Unnecessary
 No participation
during features
development and  IT is too slow in
testing responding to
 Technology- requests for support.
challenged
1/26/2012 11

12. Expectations from Data
Warehouse
Facilitating Better Communications Among
Different Business Units
•COMMUNICATION ACROSS BUSINESS
ORGANIZATION
1/26/2012 12

13. Expectations from Data
Warehouse
Facilitates Business Change
Act as an early-warning
system.
Provide insight into key
areas that
can help to make
Strategic decisions
 Facilitates decision
making
eg: which products
you want to
keep in stock.
 Facilitates to make
data-based
decisions
1/26/2012 13

14. May I help you with
any clarifications?
1/26/2012 14