Basics

Datawarehouse
“A data warehouse is a
Time-variant,
Integrated,
Nonvolatile , &
Subject-oriented
collection of data in support of
management’s decision-making
process
”William.H.Inmon - Father of Data
Warehousing
 Data Mart

• Data Marts are stand-alone small data warehouses

limited to a subject area (Ex:- Sales Analysis).

• We have Dependent and Independent data marts.

• Dependent Data Marts are extracted views of a corporate

data warehouse.

• Independent Data Marts are those which are built directly

against transaction systems.
 Operational Data Store
• The operational data store is a central data repository that
consists of very detailed level transaction data.

• * * Data warehouses and Data Marts are built by fetching data

from ODS instead of transaction systems.

• Moreover , ODS is a Data Consolidation and integration point for

several transaction systems.

• More detailed Data may not necessarily needed by data

warehousing for analytical purpose.

• ODS Becomes hub for both Data Warehouses & Transaction

Systems.
 Data Warehouse vs Operational DBMS

• OLTP (on-line transaction processing)

– Major task of traditional relational DBMS
– Day-to-day operations: purchasing, inventory,
banking, manufacturing, payroll, registration,
accounting, etc.
• OLAP (on-line analytical processing)
– Major task of data warehouse system
– Data analysis and decision making
 OLPT vs OLAP
OLTP - Operational (ECC) OLAP - Analytical (EDW)

Forms Yes No

Level of Detail (in Detailed (Reveals a snapshot of ongoing business processes) Summary (Multi-dimensional views of various kinds of business
report) activities)

Timeframe Current Trended

Staged data No Heavily

Database Design Highly normalized with many tables, Application Typically de-normalized with fewer tables - use of star
oriented schemas, Subject oriented

Data Access Read/Write Read Only (except for planning applications)

Layout Banded, listing Cross-tab, grid/matrix, graphical, dashboard

Format Formal, banded, pixel-perfect Intuitive, navigable, grid

Interaction Drill down Parameter, ad hoc, OLAP

Delivery Scheduled, pushed Pulled, event-driven

Queries Relatively standardized and simple queries Returning Often complex queries involving aggregations
relatively few records

# records accessed Tens, Hundreds, Thousands Millions

# of users Thousands Hundreds

Metric Transaction Throughput Query Throughput, Response

 DW Process
Classical data warehouses copy data into OLAP Cubes in a 3-step process
called Extract-Transform-Load (ETL)
Report
Data Warehouse, e.g. SAP Business Warehouse
OLAP Cube, also: Info Cube
Fact Table Dimension 1 Dimension 2 Dimension ...
Primary Key Dimension Key Dimension Key Dimension Key
Fact 1 Attribute 1 Attribute 1 Attribute 1
Fact 2 Attribute 2 Attribute 2 Attribute 2
Fact ... Attribute ... Attribute ... Attribute ...

3. Load
Facts Dim 1 Dim 2 Dim ...
010010110 010010110 010010110 010010110
110101110 110101110 110101110 110101110
100101011 100101011 100101011 100101011
10101110... 10101110... 10101110... 10101110...

2. Transform
Table 1 Table 2 Table ...
010010110 010010110 010010110
110101110 110101110 110101110
10101110... 10101110... 10101110...

1. Extract
ERP
Table 1 Table 2 Table ...
Primary Key Primary Key Primary Key
Field 1 Field 1 Field 1
Field 2 Field 2 Field 2
Field ... Field ... Field ...
Architecture of a Data Warehouse
Business Intelligence - What are we talking about?

Non-ECC

Orders
Reporting

GL Entries
Aggregate

Customer Info Summarize

SAP ECC SAP BW
Conform
Purchasing
Transform
Parts

Mfg Shop Floor

DATA INFORMATION
 What is BI ?
BI Applications
Balanced Scorecard

Decision
Budgeting

Dash Board

Forecast Data Entry

Management
Simulation

Multi-Dimensional Analysis

Data Mining

Analysts
Report & Listing

• Business Intelligence recovers also a link

between People Profile and Information to
Operational use
 Data Models
• The two Data Models relevant in Data Warehousing are:
– ERM (Entity Relationship Model)
– MDM (Multi-Dimensional Model)

• ERM produces a data model of the specific area of

interest, using two basic concepts:
– Entities and
– Relationships between entities

• In MDM information model consists of:

– Numerical facts (or key figures in BW terminology) and
– Dimension attributes, meaning the business terms that
describe these facts
ER Model
ER Model

The strong entities cover the whole

model. All other entities are
dependent on these strong entities.
 Multidimensional Data Model

• A Data Warehouse is based on a

Multidimensional Data Model which views data
in the form of a Data Cube
• A data cube, such as Sales, allows data to be
modeled and viewed in multiple dimensions
– Dimension Tables, such as Item (Item Name, Brand,
Type), or Time (Day, Week, Month, Quarter, Year)
– Fact Table contains measures (such as Dollars) and
keys to each of the related dimension tables
 Multidimensional Data
• Sales volume as a function of product, month, and region

Dimensions: Product, Location, Time

Hierarchical summarization paths

Industry Region Year

Category Country Quarter

Product

Product City Month Week

Office Day

Month
 A Sample Data Cube

Date Total annual sales

2Qtr of TV in U.S.A.
1Qtr 3Qtr 4Qtr sum
TV
PC U.S.A
VCR
sum
Canada

Country
Mexico

sum
 Dimension tables
 Dimension tables are grouping of related data Items.
 Master Data is Referred as Characteristics
 A Dimension Table Consists of Dimensional Id (Primary Key
) & Characteristics
 Fact Table
 Fact tables Consists Dimensional Ids & Measures.
 When Transaction data Loaded Fact table is
Maintained.
 Star Schema
“ A Fact Table in the middle connected to a set of
dimension tables.”

dimension

dimension dimension
fact

dimension dimension
• In a star schema, the ways in which we
characterize all transaction are collected together
in dimensions.
• The facts are the statistics and key figures (KPIs -
key performance indicators) that
customers use to understand their business
processes.
• The dimensions provide answers to questions
about “who? what? and when?".
 Example of Star Schema

time
item
time_key
day item_key
day_of_the_week Sales Fact Table item_name
month brand
time_key
quarter type
year item_key supplier_type
branch_key
branch location
location_key
branch_key location_key
branch_name units_sold street
branch_type city
dollars_sold
province_or_stre
avg_sales et
Measures country
Example of Star Schema
Thanks