Introduction to Data Mining and

Data Warehousing
Muhammad Ali Yousuf
DSC ITM
Friday, 9
th
May 2003
2
Data Warehousing and OLAP
Technology for Data Mining - I
What is a data warehouse?
A multi-dimensional data model
Data warehouse architecture
Data warehouse implementation
3
Data Warehousing and OLAP
Technology for Data Mining - II
From data warehousing to data mining
Motivation: Why data mining?
What is data mining?
Data Mining: On what kind of data?
4
Data Warehousing and OLAP
Technology for Data Mining - III
Data mining functionality
Are all the patterns interesting?
Classification of data mining systems
Major issues in data mining
5
What Is Data Warehouse?
Defined in many different ways, but not
rigorously.
A decision support database that is
maintained separately from the organizations
operational database.
Support information processing by providing a
solid platform of consolidated, historical data
for analysis.
6
What Is Data Warehouse?
A data warehouse is a subject-oriented,
integrated, time-variant, and nonvolatile
collection of data in support of
managements decision-making process.
- W. H. Inmon.
7
What Is Data Warehouse?
Data warehousing:
The process of constructing and using data
warehouses.
8
Data Warehouse - subject-oriented
Organized around major subjects, such as
customer, product, sales.
9
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.
Data Warehouse - subject-oriented
10
Data Warehouseintegrated
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.
11
Data WarehouseTime 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).
12
Data WarehouseTime Variant
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.

13
Data WarehouseNon-Volatile
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.
14
Data Warehouse vs. Heterogeneous
DBMS
Traditional heterogeneous DB integration:
Build wrappers/mediators on top of heterogeneous
databases
Query driven approach
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
15
Data Warehouse vs. Heterogeneous
DBMS
Data warehouse: update-driven, high
performance
Information from heterogeneous sources is integrated
in advance and stored in warehouses for direct query
and analysis
16
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.
17
Data Warehouse vs. Operational
DBMS
OLAP (on-line analytical processing)
Major task of data warehouse system
Data analysis and decision making
18
Data Warehouse vs. Operational
DBMS
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
19
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
detailed, flat relational
isolated
historical,
summarized, multidimensional
integrated, consolidated
usage repetitive ad-hoc
access read/write
index/hash on prim. key
lots of scans
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


20
Why Separate Data Warehouse?
High performance for both systems
DBMS tuned for OLTP: access methods,
indexing, concurrency control, recovery
Warehousetuned for OLAP: complex OLAP
queries, multidimensional view, consolidation.
21
Why Separate Data Warehouse?
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
22
A Multi-dimensional Data Model
23
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
24
From Tables and
Spreadsheets to Data Cubes
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
25
From Tables and
Spreadsheets to Data Cubes
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.
26
Cube: A Lattice of Cuboids
all
time item location supplier
time,item time,location
time,supplier
item,location
item,supplier
location,supplier
time,item,location
time,item,supplier
time,location,supplier
item,location,supplier
time, item, location, supplier
0-D(apex) cuboid
1-D cuboids
2-D cuboids
3-D cuboids
4-D(base) cuboid
27
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
28
Example of Star Schema

time_key
day
day_of_the_week
month
quarter
year
time
location_key
street
city
province_or_street
country
location
Sales Fact Table
time_key
item_key
branch_key
location_key
units_sold
dollars_sold
avg_sales
Measures
item_key
item_name
brand
type
supplier_type
item
branch_key
branch_name
branch_type
branch
29
Conceptual Modeling
of Data Warehouses
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
30
Example of Snowflake Schema
time_key
day
day_of_the_week
month
quarter
year
time
location_key
street
city_key
location
Sales Fact Table
time_key
item_key
branch_key
location_key
units_sold
dollars_sold
avg_sales
Measures
item_key
item_name
brand
type
supplier_key
item
branch_key
branch_name
branch_type
branch
supplier_key
supplier_type
supplier
city_key
city
province_or_street
country
city
31
Conceptual Modeling
of Data Warehouses
Fact constellations: Multiple fact tables share
dimension tables, viewed as a collection of
stars, therefore called galaxy schema or fact
constellation
32
Example of Fact Constellation
time_key
day
day_of_the_week
month
quarter
year
time
location_key
street
city
province_or_street
country
location
Sales Fact Table
time_key
item_key
branch_key
location_key
units_sold
dollars_sold
avg_sales
Measures
item_key
item_name
brand
type
supplier_type
item
branch_key
branch_name
branch_type
branch
Shipping Fact Table
time_key
item_key
shipper_key
from_location
to_location
dollars_cost
units_shipped
shipper_key
shipper_name
location_key
shipper_type
shipper
33
A Data Mining Query Language -
DMQL
34
Language Primitives
Cube Definition (Fact Table)
define cube <cube_name> [<dimension_list>]:
<measure_list>
Dimension Definition ( Dimension Table )
define dimension <dimension_name> as
(<attribute_or_subdimension_list>)
35
Language Primitives
Special Case (Shared Dimension Tables)
First time as cube definition
define dimension <dimension_name> as
<dimension_name_first_time> in cube
<cube_name_first_time>

36
Defining a Star Schema in
DMQL
define cube sales_star [time, item, branch,
location]:
dollars_sold = sum(sales_in_dollars),
avg_sales = avg(sales_in_dollars),
units_sold = count(*)
define dimension time as (time_key, day,
day_of_week, month, quarter, year)
37
Defining a Star Schema in
DMQL
define dimension item as (item_key,
item_name, brand, type, supplier_type)
define dimension branch as (branch_key,
branch_name, branch_type)
define dimension location as (location_key,
street, city, province_or_state, country)
38
Defining a Snowflake Schema in
DMQL
define cube sales_snowflake [time, item,
branch, location]:
dollars_sold = sum(sales_in_dollars), avg_sales
= avg(sales_in_dollars), units_sold = count(*)
define dimension time as (time_key, day,
day_of_week, month, quarter, year)
39
Defining a Snowflake Schema in
DMQL
define dimension item as (item_key,
item_name, brand, type,
supplier(supplier_key, supplier_type))
define dimension branch as (branch_key,
branch_name, branch_type)
define dimension location as (location_key,
street, city(city_key, province_or_state,
country))
40
Defining a Fact Constellation in
DMQL
define cube sales [time, item, branch, location]:
dollars_sold = sum(sales_in_dollars), avg_sales =
avg(sales_in_dollars), units_sold = count(*)
define dimension time as (time_key, day, day_of_week,
month, quarter, year)
define dimension item as (item_key, item_name, brand,
type, supplier_type)
define dimension branch as (branch_key, branch_name,
branch_type)
define dimension location as (location_key, street, city,
province_or_state, country)
41
Defining a Fact Constellation in
DMQL
define cube shipping [time, item, shipper, from_location,
to_location]:
dollar_cost = sum(cost_in_dollars), unit_shipped =
count(*)
define dimension time as time in cube sales
define dimension item as item in cube sales
define dimension shipper as (shipper_key, shipper_name,
location as location in cube sales, shipper_type)
define dimension from_location as location in cube sales
define dimension to_location as location in cube sales
42
Measures: Three Categories
distributive: if the result derived by applying
the function to n aggregate values is the
same as that derived by applying the
function on all the data without partitioning.
E.g., count(), sum(), min(), max().
43
Measures: Three Categories
algebraic: if it can be computed by an
algebraic function with M arguments (where
M is a bounded integer), each of which is
obtained by applying a distributive
aggregate function.
E.g., avg(), min_N(), standard_deviation().
44
Measures: Three Categories
holistic: if there is no constant bound on the
storage size needed to describe a
subaggregate.
E.g., median(), mode(), rank().
45
Multidimensional Data
Sales volume as a function of product,
month, and region
P
r
o
d
u
c
t

Month
Dimensions: Product, Location, Time
Hierarchical summarization paths
Industry Region Year

Category Country Quarter

Product City Month Week

Office Day
46
A Sample Data Cube
Total annual sales
of TV in U.S.A.
Date
C
o
u
n
t
r
y

sum
sum

TV
VCR
PC
1Qtr
2Qtr
3Qtr
4Qtr
U.S.A
Canada
Mexico
sum
47
Cuboids Corresponding to the
Cube
all
product
date
country
product,date product,country date, country
product, date, country
0-D(apex) cuboid
1-D cuboids
2-D cuboids
3-D(base) cuboid
48
Browsing a Data Cube
Visualization
OLAP capabilities
Interactive manipulation
49
Typical OLAP Operations
Roll up (drill-up): summarize data
by climbing up hierarchy or by dimension reduction
Drill down (roll down): reverse of roll-up
from higher level summary to lower level summary
or detailed data, or introducing new dimensions
50
Typical OLAP Operations
Slice and dice:
project and select
Pivot (rotate):
reorient the cube, visualization, 3D to series of 2D
planes.
Other operations
drill across: involving (across) more than one fact
table
drill through: through the bottom level of the cube to
its back-end relational tables (using SQL)
51
Data Warehouse Architecture
52
Design of a Data Warehouse: A
Business Analysis Framework
Four views regarding the design of a data
warehouse
Top-down view
allows selection of the relevant information
necessary for the data warehouse
Data source view
exposes the information being captured, stored,
and managed by operational systems
53
Design of a Data Warehouse: A
Business Analysis Framework
Data warehouse view
consists of fact tables and dimension tables
Business query view
sees the perspectives of data in the warehouse
from the view of end-user
54
Data Warehouse Design Process
Top-down, bottom-up approaches or a
combination of both
Top-down: Starts with overall design and planning
(mature)
Bottom-up: Starts with experiments and prototypes
(rapid)
55
Data Warehouse Design Process
From software engineering point of view
Waterfall: structured and systematic analysis at each
step before proceeding to the next
Spiral: rapid generation of increasingly functional
systems, short turn around time, quick turn around
56
Data Warehouse Design Process
Typical data warehouse design process
Choose a business process to model, e.g., orders,
invoices, etc.
Choose the grain (atomic level of data) of the
business process
Choose the dimensions that will apply to each fact
table record
Choose the measure that will populate each fact table
record
57
Multi-Tiered Architecture
Data
Warehouse
Extract
Transform
Load
Refresh
OLAP Engine
Analysis
Query
Reports
Data mining
Monitor
&
Integrator
Metadata
Data Sources
Front-End Tools
Serve
Data Marts
Operational
DBs
other
sources
Data Storage
OLAP Server
58
Three Data Warehouse Models
Enterprise warehouse
collects all of the information about subjects
spanning the entire organization
59
Three Data Warehouse Models
Data Mart
a subset of corporate-wide data that is of value
to a specific groups of users. Its scope is
confined to specific, selected groups, such as
marketing data mart
Independent vs. dependent (directly from warehouse)
data mart
60
Three Data Warehouse Models
Virtual warehouse
A set of views over operational databases
Only some of the possible summary views may
be materialized
61
Data Warehouse Development: A
Recommended Approach
Define a high-level corporate data model
Data
Mart
Data
Mart
Distributed
Data Marts
Multi-Tier Data
Warehouse
Enterprise
Data
Warehouse
Model refinement Model refinement
62
OLAP Server Architectures
Relational OLAP (ROLAP)
Use relational or extended-relational DBMS to store
and manage warehouse data and OLAP middle ware
to support missing pieces
Include optimization of DBMS backend,
implementation of aggregation navigation logic, and
additional tools and services
greater scalability
Multidimensional OLAP (MOLAP)
Array-based multidimensional storage engine (sparse
matrix techniques)
fast indexing to pre-computed summarized data
63
OLAP Server Architectures
Hybrid OLAP (HOLAP)
User flexibility, e.g., low level: relational, high-level:
array
Specialized SQL servers
specialized support for SQL queries over
star/snowflake schemas
64
Data Warehouse Implementation
65
Efficient Data Cube Computation
Data cube can be viewed as a lattice of
cuboids
The bottom-most cuboid is the base cuboid
The top-most cuboid (apex) contains only one
cell
How many cuboids in an n-dimensional cube
with L levels?

) 1
1
(

n
i
i
L T
66
Efficient Data Cube Computation
Materialization of data cube
Materialize every (cuboid) (full materialization),
none (no materialization), or some (partial
materialization)
Selection of which cuboids to materialize
Based on size, sharing, access frequency, etc.
67
Cube Operation
Cube definition and computation in DMQL
define cube sales[item, city, year]:
sum(sales_in_dollars)
compute cube sales
(item) (city)
()
(year)
(city, item) (city, year) (item, year)
(city, item, year)
68
Cube Operation
Transform it into a SQL-like language (with a new
operator cube by, introduced by Gray et al.96)
SELECT item, city, year, SUM (amount)
FROM SALES
CUBE BY item, city, year
(item) (city)
()
(year)
(city, item) (city, year) (item, year)
(city, item, year)
69
Cube Operation
Need compute the following Group-Bys
(date, product, customer),
(date,product),(date, customer), (product, customer),
(date), (product), (customer)
()
(item) (city)
()
(year)
(city, item) (city, year) (item, year)
(city, item, year)
70
Cube Computation: ROLAP-Based
Method
Efficient cube computation methods
ROLAP-based cubing algorithms (Agarwal et al96)
Array-based cubing algorithm (Zhao et al97)
Bottom-up computation method (Bayer &
Ramarkrishnan99)
71
Cube Computation: ROLAP-Based
Method
ROLAP-based cubing algorithms
Sorting, hashing, and grouping operations are
applied to the dimension attributes in order to
reorder and cluster related tuples
Grouping is performed on some subaggregates as a
partial grouping step
Aggregates may be computed from previously
computed aggregates, rather than from the base
fact table
72
Multi-way Array Aggregation
for Cube Computation
Partition arrays into chunks (a small subcube which fits in
memory).
Compressed sparse array addressing: (chunk_id, offset)
Compute aggregates in multiway by visiting cube cells in
the order which minimizes the # of times to visit each cell,
and reduces memory access and storage cost.
73
Multi-way Array Aggregation for
Cube Computation
A
B
29 30 31 32
1 2 3 4
5
9
13 14 15 16
64 63 62 61
48 47 46 45
a1 a0
c3
c2
c1
c 0
b3
b2
b1
b0
a2 a3
C
B
44
28
56
40
24
52
36
20
60
What is the best
traversing order
to do multi-way
aggregation?
74
Multi-way Array Aggregation
for Cube Computation
A
B
29 30 31 32
1 2 3 4
5
9
13 14 15 16
64 63 62 61
48 47 46 45
a1 a0
c3
c2
c1
c 0
b3
b2
b1
b0
a2 a3
C
44
28
56
40
24
52
36
20
60
B
75
Multi-way Array
Aggregation for Cube
Computation
A
B
29 30 31 32
1 2 3 4
5
9
13 14 15 16
64 63 62 61
48 47 46 45
a1 a0
c3
c2
c1
c 0
b3
b2
b1
b0
a2 a3
C
44
28
56
40
24
52
36
20
60
B
76
Multi-Way Array Aggregation
for Cube Computation (Cont.)
Method: the planes should be sorted and
computed according to their size in
ascending order.
See the details of Example 2.12 (pp. 75-78)
Idea: keep the smallest plane in the main
memory, fetch and compute only one chunk
at a time for the largest plane
77
Multi-Way Array Aggregation
for Cube Computation (Cont.)
Limitation of the method: computing well
only for a small number of dimensions
If there are a large number of dimensions,
bottom-up computation and iceberg cube
computation methods can be explored
78
Indexing OLAP Data: Bitmap
Index
Index on a particular column
Each value in the column has a bit vector: bit-
op is fast
The length of the bit vector: # of records in the
base table
The i-th bit is set if the i-th row of the base
table has the value for the indexed column
not suitable for high cardinality domains
79
Indexing OLAP Data: Bitmap
Index
Cust Region Type
C1 Asia Retail
C2 Europe Dealer
C3 Asia Dealer
C4 America Retail
C5 Europe Dealer
RecID Retail Dealer
1 1 0
2 0 1
3 0 1
4 1 0
5 0 1
RecIDAsia Europe America
1 1 0 0
2 0 1 0
3 1 0 0
4 0 0 1
5 0 1 0
Base table
Index on Region Index on Type
80
Efficient Processing OLAP
Queries
Determine which operations should be
performed on the available cuboids:
transform drill, roll, etc. into corresponding SQL
and/or OLAP operations, e.g, dice = selection +
projection
81
Efficient Processing OLAP
Queries
Determine to which materialized cuboid(s)
the relevant operations should be applied.
Exploring indexing structures and
compressed vs. dense array structures in
MOLAP
82
Metadata Repository
Meta data is the data defining warehouse objects.
It has the following kinds
Description of the structure of the 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)
83
Metadata Repository
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
84
Data Warehouse Back-End Tools
and Utilities
Data extraction:
get data from multiple, heterogeneous, and
external sources
Data cleaning:
detect errors in the data and rectify them when
possible
85
Data Warehouse Back-End Tools
and Utilities
Data transformation:
convert data from legacy or host format to
warehouse format
Load:
sort, summarize, consolidate, compute views,
check integrity, and build indicies and partitions
Refresh
propagate the updates from the data sources
to the warehouse
86
Further Development of Data
Cube Technology
87
Discovery-Driven Exploration of
Data Cubes
Hypothesis-driven: exploration by user, huge
search space
Discovery-driven (Sarawagi et al.98)
pre-compute measures indicating exceptions, guide
user in the data analysis, at all levels of aggregation
Exception: significantly different from the value
anticipated, based on a statistical model
88
From Data Warehousing to
Data Mining
89
Data Warehouse Usage
Three kinds of data warehouse applications
Information processing
supports querying, basic statistical analysis, and
reporting using crosstabs, tables, charts and
graphs
Analytical processing
multidimensional analysis of data warehouse data
supports basic OLAP operations, slice-dice,
drilling, pivoting
90
Data Warehouse Usage
Data mining
knowledge discovery from hidden patterns
supports associations, constructing analytical
models, performing classification and prediction,
and presenting the mining results using
visualization tools.
Differences among the three tasks
91
From On-Line Analytical Processing to
On Line Analytical Mining (OLAM)
Why online analytical mining?
High quality of data in data warehouses
DW contains integrated, consistent, cleaned data
Available information processing structure surrounding data
warehouses
ODBC, OLEDB, Web accessing, service facilities, reporting
and OLAP tools
OLAP-based exploratory data analysis
mining with drilling, dicing, pivoting, etc.
On-line selection of data mining functions
integration and swapping of multiple mining functions,
algorithms, and tasks.
Architecture of OLAM
92
An OLAM Architecture
Data
Warehouse
Meta Data
MDDB
OLAM
Engine
OLAP
Engine
User GUI API
Data Cube API
Database API
Data cleaning
Data integration
Layer3
OLAP/OLAM
Layer2
MDDB
Layer1
Data
Repository
Layer4
User Interface
Filtering&Integration Filtering
Databases
Mining query Mining result
93
Data Mining
94
Why Data Mining? Potential
Applications
Database analysis and decision support
Market analysis and management
target marketing, customer relation management,
market basket analysis, cross selling, market
segmentation
Risk analysis and management
Forecasting, customer retention, improved
underwriting, quality control, competitive analysis
Fraud detection and management
95
Why Data Mining? Potential
Applications
Other Applications
Text mining (news group, email, documents) and
Web analysis.
Intelligent query answering
96
Material taken from http://www.cs.sfu.ca/~han
Tiempo para descansar !!!