0% found this document useful (0 votes)
58 views42 pages

Chapter 3 Part 1

This document discusses data warehousing and business intelligence using data warehousing. It introduces data warehouse architecture, including the extraction, transformation, and loading (ETL) process. It also discusses dimensional modeling with star schemas, snowflake schemas, and fact constellations to structure data warehouses for analysis. The purpose of data warehousing is to support business intelligence and decision making through consolidated, historical data.

Uploaded by

Rashmi Angane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
58 views42 pages

Chapter 3 Part 1

This document discusses data warehousing and business intelligence using data warehousing. It introduces data warehouse architecture, including the extraction, transformation, and loading (ETL) process. It also discusses dimensional modeling with star schemas, snowflake schemas, and fact constellations to structure data warehouses for analysis. The purpose of data warehousing is to support business intelligence and decision making through consolidated, historical data.

Uploaded by

Rashmi Angane
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 42

Chapter 3:

BI using Data Warehousing

 Introduction to DW
 DW architecture [ch7 paulraj] [ch 3.3 Han Kamber]
 ETL Process[chapt 12 paulraj]
 Top-down and bottom-up approaches, characteristics
and benefits of data mart[ch 2 paulraj]
 Difference between OLAP[ch 15 paulraj] and OLTP.
 Dimensional analysis[ch 5 paulraj]- Define cubes. Drill-
down and roll- up – slice and dice or rotation
 OLAP models- ROLAP and MOLAP[ch 15 paulraj]
 Define Schemas- Star, snowflake and fact constellations
[chapt 10&11 paulraj] [ch 3.2 Han Kamber]
Chapter 3: Data Warehousing and
OLAP Technology: An Overview

 What is a data warehouse?

 A multi-dimensional data model

 Data warehouse architecture

 Data warehouse implementation

 From data warehousing to data mining

February 23, 2018 Data Mining: Concepts and Techniques 2


A producer wants to know….
Which are our
lowest/highest margin
customers ?
Who are my customers
What is the most and what products
effective distribution are they buying?
channel?

What product prom- Which customers


-otions have the biggest are most likely to go
impact on revenue? to the competition ?
What impact will
new products/services
have on revenue
and margins? 3
What is Data Warehouse?
 Defined in many different ways, but not rigorously.
 A decision support database that is maintained separately from the organization’s
operational database
 Support information processing by providing a solid platform of consolidated,
historical data for analysis.
 They are static with infrequent updates, mostly read only data.
 Integrated from several heterogeneous operational databases DW is a standalone
repository.
 Data warehousing:
 the process of constructing and using data warehouses

4
 “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile
collection of data in support of management’s decision-making process.”—W. H. Inmon

February 23, 2018 Data Mining: Concepts and Techniques 5


Data Warehouse—Subject-Oriented
 Organized around major subjects, such as customer, product, sales
 Focusing on the modeling and analysis of data for decision makers, not on
daily operations or transaction processing
 Provide a simple and concise view around particular subject issues by
excluding data that are not useful in the decision support process

February 23, 2018 Data Mining: Concepts and Techniques 6


Data Warehouse—Integrated
 Constructed by integrating multiple, heterogeneous data sources
 relational databases, flat files, on-line transaction records

 Data cleaning and data integration techniques are applied.


 Ensure consistency in naming conventions, encoding structures,

attribute measures, etc. among different data sources


 E.g., Hotel price: currency, tax, breakfast covered, etc.

 When data is moved to the warehouse, it is converted.

February 23, 2018 Data Mining: Concepts and Techniques 7


February 23, 2018 Data Mining: Concepts and Techniques 8
Data Warehouse—Time Variant
 The time horizon for the data warehouse is significantly longer than that of
operational systems
 Operational database: current value data
 Data warehouse data: provide information from a historical perspective
(e.g., past 5-10 years)
 Every key structure in the data warehouse
 Contains an element of time, explicitly or implicitly
 But the key of operational data may or may not contain “time element”

February 23, 2018 Data Mining: Concepts and Techniques 9


February 23, 2018 Data Mining: Concepts and Techniques 10
Data Warehouse—Nonvolatile
 A physically separate store of data transformed from the operational
environment
 Operational update of data does not occur in the data warehouse
environment
 Does not require transaction processing, recovery, and
concurrency control mechanisms
 Requires only two operations in data accessing:
 initial loading of data and access of data

February 23, 2018 Data Mining: Concepts and Techniques 11


February 23, 2018 Data Mining: Concepts and Techniques 12
The goals of a Data Warehouse
 We have mountains of data in this company, but we can't
access it."
 "We need to slice and dice the data every which way."
 "You've got to make it easy for business people to get at
the data directly."
 "Just let me know what is important."
 "It drives me crazy to have two people present the same
business metrics at a meeting, but with different
numbers."
 "We want people to use information to support more fact-
based decision making."

13
The goals of a Data Warehouse
 The data warehouse must make an organization's
information easily accessible.
 The data warehouse must present the organization's
information consistently.
 The data warehouse must be adaptive and resilient to
change.
 The data warehouse must be a secure bastion that
protects our information assets.
 The data warehouse must serve as the foundation for
improved decision making.
 The business community must accept the data warehouse
if it is to be deemed successful.

14
 Data warehouse is not a single software or
hardware product you purchase to provide
strategic information.
 it is a computing environment where users can
find strategic information to make strategic
decisions.

February 23, 2018 Data Mining: Concepts and Techniques 15


Data Warehouse Architecture

Create

Metadata Queries

Database
Data Mining

Extract
Clean
Transform
Load Data Staging
Operational & other User
The data warehouse
External data sources
16
Data Warehouse Architecture

The major elements of a data warehouse and the major


external entities with which a data warehouse interacts
include:-
 The transaction or other operational databases from which
the data warehouse is populated. External data is also fed
into some data warehouse.
 A process to extract data from this database and bring it into
the data warehouse.
 A process to transform the data into the database structure
& internal formats of the warehouse
 A process to cleanse the data, to make sure it is of sufficient
quality for the decision making purposes for which it will be
used.
 A process to load the cleansed data into the data warehouse
database.
17
Data Staging Area
• A storage area where extracted data is
cleaned, transformed and deduplicated.
• Initial storage for data
• Need not be based on Relational model
• Mainly sorting and Sequential processing
• Does not provide data access to users
• Analogy – kitchen of a restaurant
Data Warehouse Architecture

Relational
Databases
Optimized Loader
Extraction
ERP
Systems Cleansing

Data Warehouse
Engine Analyze
Purchased Query
Data

Legacy
Data Metadata Repository

20
Data Warehouse Architecture

21
February 23, 2018 Data Mining: Concepts and Techniques 22
The benefits of data warehousing
 The potential benefits of data warehousing are
high returns on investment.
 substantial competitive advantage.
 increased productivity of corporate decision-
makers.

26
Conceptual Modeling of Data Warehouses
 Modeling data warehouses: dimensions & measures
 Star schema: A fact table in the middle connected to a
set of dimension tables
 Snowflake schema: A refinement of star schema
where some dimensional hierarchy is normalized into a
set of smaller dimension tables, forming a shape
similar to snowflake
 Fact constellations: Multiple fact tables share
dimension tables, viewed as a collection of stars,
therefore called galaxy schema or fact constellation

February 23, 2018 Data Mining: Concepts and Techniques 27


February 23, 2018 Data Mining: Concepts and Techniques 28
Example of Star Schema
time
time_key item
day item_key
day_of_the_week Sales Fact Table item_name
month brand
quarter time_key type
year supplier_type
item_key
branch_key
branch location
location_key
branch_key location_key
branch_name units_sold street
branch_type city
dollars_sold state_or_province
country
avg_sales
Measures

February 23, 2018 Data Mining: Concepts and Techniques 29


Example of Snowflake Schema
time
time_key item
day item_key supplier
day_of_the_week Sales Fact Table item_name supplier_key
month brand supplier_type
quarter time_key type
year item_key supplier_key

branch_key
branch location
location_key
location_key
branch_key
units_sold street
branch_name
city_key
branch_type
dollars_sold city
city_key
avg_sales city
state_or_province
Measures country

February 23, 2018 Data Mining: Concepts and Techniques 30


Example of Fact Constellation
time
time_key item Shipping Fact Table
day item_key
day_of_the_week Sales Fact Table item_name time_key
month brand
quarter time_key type item_key
year supplier_type shipper_key
item_key
branch_key from_location

branch location_key location to_location


branch_key location_key dollars_cost
branch_name
units_sold
street
branch_type dollars_sold city units_shipped
province_or_state
avg_sales country shipper
Measures shipper_key
shipper_name
location_key
February 23, 2018 Data Mining: Concepts and Techniques shipper_type 31
Metadata

Relational
Databases
Optimized Loader
Extraction
ERP
Systems Cleansing

Data Warehouse
Engine Analyze
Purchased Query
Data

Legacy
Data Metadata Repository

32
Metadata Repository
 Meta data is the data defining warehouse objects. It stores:
 Description of the structure of the data warehouse
 schema, view, dimensions, hierarchies, derived data defn, data
mart locations and contents
 Operational meta-data
 data lineage (history of migrated data and transformation path),
currency of data (active, archived, or purged), monitoring
information (warehouse usage statistics, error reports, audit trails)
 The algorithms used for summarization
 The mapping from operational environment to the data warehouse
 Data related to system performance
 warehouse schema, view and derived data definitions

 Business data
 business terms and definitions, ownership of data, charging policies
February 23, 2018 Data Mining: Concepts and Techniques 33
Metadata
 Data about data, data dictionary, data catalog
 Keeps info about the logical data structures, files and addresses , indexes,
etc.
 Types are:
 Operational Metadata:
 data from various operational sources are combined, records are split, combine parts
of records, multiple coding schemes and different fields lengths and data types.
 To deliver info you need to tie them back together
 Extraction & transformation metadata:
 Extraction frequencies, Extraction methods and Extraction business rules need to be
recorded. source system info,
 Contains info about all transformations taking place in staging area.
 End User Metadata:
 Navigation map of DW for the end user
 Allows end user to use its own business terminology and look for info
February 23, 2018 Paulraj pg. No. 42 34
Metadata

Helps:
•As a glue to connect all parts of DW.
•Provide info to the developer about content and
structure (IT personnel need to know data sources and targets;
database, table and column names; refresh schedules; data usage measures;
etc.)
•Content recognizable in end users terms (Users need to
know entity/attribute definitions; reports/query tools available; report
distribution information; help desk contact information, etc. )
•It is useful to have a central information repository
to tell users what’s in the data warehouse, where it
came from, who is in charge of it etc.
•The metadata can also tell query tools what’s in
the data warehouse, where to find it, who is
authorized to access it etc. 35
February 23, 2018 Data Mining: Concepts and Techniques 36
Data Staging Area: ETL
• A storage area where extracted data is
cleaned, transformed and deduplicated.
• Initial storage for data
• Need not be based on Relational model
• Mainly sorting and Sequential processing
• Does not provide data access to users
• Analogy – kitchen of a restaurant
ETL

Create

Metadata Queries

Database
Data Mining

Extract
Clean
Transform
Load Data Staging
Operational & other User
The data warehouse
External data sources
38
 Dimensional analysis[ch 5 paulraj]
 Define cubes.
 Drill- down and roll- up – slice and dice or
rotation
 OLAP models- ROLAP and MOLAP[ch 15 paulraj]
 Define Schemas- Star, snowflake and fact
constellations [chapt 10&11 paulraj] [ch 3.2
Han Kamber]

February 23, 2018 Data Mining: Concepts and Techniques 39


Data Warehouse vs. Heterogeneous DBMS

 Traditional heterogeneous DB integration: A query driven approach

 Build wrappers/mediators on top of heterogeneous databases

 When a query is posed to a client site, a meta-dictionary is used


to translate the query into queries appropriate for individual
heterogeneous sites involved, and the results are integrated into
a global answer set

 Complex information filtering, compete for resources

 Data warehouse: update-driven, high performance

 Information from heterogeneous sources is integrated in advance


and stored in warehouses for direct query and analysis
February 23, 2018 Data Mining: Concepts and Techniques 40
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
 Distinct features (OLTP vs. OLAP):
 User and system orientation: customer vs. market
 Data contents: current, detailed vs. historical, consolidated
 Database design: ER + application vs. star + subject
 View: current, local vs. evolutionary, integrated
 Access patterns: update vs. read-only but complex queries
February 23, 2018 Data Mining: Concepts and Techniques 41
OLTP vs. OLAP
OLTP OLAP
users clerk, IT professional knowledge worker
function day to day operations decision support
DB design application-oriented subject-oriented
data current, up-to-date historical,
detailed, flat relational summarized, multidimensional
isolated integrated, consolidated
usage repetitive ad-hoc
access read/write lots of scans
index/hash on prim. key
unit of work short, simple transaction complex query
# records accessed tens millions
#users thousands hundreds
DB size 100MB-GB 100GB-TB
metric transaction throughput query throughput, response

February 23, 2018 Data Mining: Concepts and Techniques 42


Why Separate Data Warehouse?
 High performance for both systems
 DBMS— tuned for OLTP: access methods, indexing, concurrency
control, recovery
 Warehouse—tuned for OLAP: complex OLAP queries,
multidimensional view, consolidation
 Different functions and different data:
 missing data: Decision support requires historical data which
operational DBs do not typically maintain
 data consolidation: DS requires consolidation (aggregation,
summarization) of data from heterogeneous sources
 data quality: different sources typically use inconsistent data
representations, codes and formats which have to be reconciled
 Note: There are more and more systems which perform OLAP
analysis directly on relational databases
February 23, 2018 Data Mining: Concepts and Techniques 43
From Tables and Spreadsheets to Data Cubes
 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_sold) and keys to
each of the related dimension tables
 In data warehousing literature, an n-D base cube is called a base
cuboid. The top most 0-D cuboid, which holds the highest-level of
summarization, is called the apex cuboid. The lattice of cuboids
forms a data cube.
February 23, 2018 Data Mining: Concepts and Techniques 44
1. Short note on:
1. Data Mart(DM)
2. Data Quality -----2015-KT
2. Differentiate between
1. DW Vs DM -----2015-KT, 2014-KT, 2016-KT
2. Operational system Vs informational system -----2016-KT
3.

4. Compare and contrast OLTP & DW.


5. What is a data warehouse and a data mart. What are characteristics of a DW? How DW and DM are different from
each other.
6. What is DW? Why it is needed? Explain ETL in detail.-----2015, 2014, 2016
7. Explain ETL in DW? ---2015-Rev
8. Explain the architecture of DW with neat diagram. ----2016-KT
9. What is data staging? Explain ETL process in detail. Write detailed architecture of DW. -----2015-KT
10. Define data warehouse. Explain any 3 architectural types of DW. ---2014
11. Explain the top down and bottom up approach in DW and suggest which is better. Explain the practical approach to
construct a data warehouse.
12. What is metadata of DW? How it is different from metadata of OLTP systems.
13. Describe steps of DW implementation. (Rob C. 652, Rob C pg-488 2010 print) ---2014 –KT
14. Explain performance improvement techniques of DW.
15. What are the success factors for DW project?
16. Explain functional components of DW project development

45
 Short note on:
 Roll up and drill down -----2015
 Dimensional modeling ---2014
 MOLAP ----2016-KT , 2016-KT
 ROLAP
 Start schema ----2015-Rev
 Snow flake schema ----2014-Rev-KT
 Compare following:
 ROLAP and MOLAP -----2015,2015-KT, 2014-Rev-KT
 OLTP & OLAP -----2015-KT, 2014, 2016-KT
 Data mining Vs OLAP ----2016
 What is fact and dimension data? Differentiate between fact and dimension table. What are the components of fact
and dimension table? (Paulraj- 212, Mallach- 496)
 What is multidimensional data cube of hypercube? How slice and dice technique fits into this model? ---2014,
2015-Rev, 2014-Rev-KT
 What is factless fact table? (Paulraj- 249)
 Write short note on information package diagram.
 What is dimensional analysis and modeling? Explain development phases of dimensional modeling. (Paulraj -204)
 What is dimension modeling? Discuss different dimension modeling techniques in detail. ---2014 –KT
 Explain snowflake schema, star schema and fact constellation schema with suitable example. Mention advantages &
disadvantages. (Paulraj -220, 238, 249) -----2015-KT
 What is family of stars/ fact constellation schema? (Paulraj -249) -----2015-KT
 Explain fact constellation schema for inventory management system assuming appropriate information.
----2016-KT
 Explain OLAP architecture with a neat diagram. -----2016-KT
 Explain major functions of OLAP. -----2015-KT
 Define OLAP. Explain MOLAP and ROLAP with suitable diagram. -----2014-KT, 2014
 What is Fundamental difference between MOLAP and ROLAP? -----2016
 Explain OLAP operations on multidimensional cubes with examples .-----2015, 2016
 Explain various OLAP implementation techniques.

February 23, 2018 Data Mining: Concepts and Techniques 46

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy