Академический Документы
Профессиональный Документы
Культура Документы
1
Definition of terms
Reasons for information gap between
information needs and availability
Reasons for need of data warehousing
Describe three levels of data warehouse
architectures
List four steps of data reconciliation
Describe two components of star schema
Estimate fact table size
Design a data mart
Chapter 11
2
Data Warehouse:
A subject-oriented, integrated, time-variant, non-
updatable collection of data used in support of
management decision-making processes
Subject-oriented: e.g. customers, patients, students,
products
Integrated: Consistent naming conventions, formats,
encoding structures; from multiple data sources
Time-variant: Can study trends and changes
Nonupdatable: Read-only, periodically refreshed
Data Mart:
A data warehouse that is limited in scope
Chapter 11
3
Integrated, company-wide view of high-quality
information (from disparate databases)
Separation of operational and informational
systems and data (for improved performance)
Chapter 11
4
Source: adapted from Strange (1997).
5
Generic Two-Level Architecture
Independent Data Mart
Dependent Data Mart and
Operational Data Store
Logical Data Mart and @ctive
Warehouse
Three-Layer architecture
Chapter 11
6
Figure 11-2: Generic two-level architecture
L
One,
company-
wide
T warehouse
7
Figure 11-3: Independent data mart
Data marts:
Mini-warehouses, limited in scope
T
E
8
Figure 11-4: ODS provides option for
Dependent data mart with operational data store obtaining current data
T
E Simpler data access
Single ETL for
enterprise data warehouse Dependent data marts
(EDW) loaded from EDW
9
ODS and data warehouse
are one and the same
T
E
Near real-time ETL for Data marts are NOT separate databases,
@active Data Warehouse but logical views of the data warehouse
Easier to create new data marts
10
Figure 11-6: Three-layer data architecture
11
Status
Status
Chapter 11
12
Data Characteristics
Transient vs. Periodic Data
Changes to existing
records are written
over previous
records, thus
destroying the
previous data content
Chapter 11
13
Typical operational data is:
Transient – not historical
Not normalized (perhaps due to denormalization for
performance)
Restricted in scope – not comprehensive
Sometimes poor quality – inconsistencies and errors
After ETL, data should be:
Detailed – not summarized yet
Historical – periodic
Normalized – 3rd normal form or higher
Comprehensive – enterprise-wide perspective
Timely – data should be current enough to assist decision-
making
Quality controlled – accurate with full integrity
Chapter 11
14
Capture/Extract
Scrub or data cleansing
Transform
Load and Index
Chapter 11
15
Capture/Extract…obtaining a
snapshot of a chosen subset of
the source data for loading
into the data warehouse
Record-level: Field-level:
Selection – data partitioning single-field – from one field to one field
Joining – data combining multi-field – from many fields to one, or
Aggregation – data summarization one field to many
18
Load/Index= place transformed data
into the warehouse and create indexes
19
Figure 11-11: Single-field transformation
Chapter 11
20
Figure 11-12: Multifield transformation
Chapter 11
21
Objectives
Ease of use for decision support applications
Fast response to predefined user queries
Customized data for particular target audiences
Ad-hoc query support
Data mining capabilities
Characteristics
Detailed (mostly periodic) data
Aggregate (for summary)
Distributed (to departmental servers)
24
25
Dimension table keys must be surrogate (non-
intelligent and non-business related), because:
Keys may change over time
Length/format consistency
Granularity of Fact Table – what level of detail
do you want?
Transactional grain – finest level
Aggregated grain – more summarized
Finer grains better market basket analysis capability
Finer grain more dimension tables, more rows in fact table
Duration of the database – how much history
should be kept?
Natural duration – 13 months or 5 quarters
Financial institutions may need longer duration
Older data is more difficult to source and cleanse
Chapter 11
26
Figure 11-16: Modeling dates
Chapter 11
28
Identify subjects of the data mart
Identify dimensions and facts
Indicate how data is derived from enterprise data
warehouses, including derivation rules
Indicate how data is derived from operational
data store, including derivation rules
Identify available reports and predefined queries
Identify data analysis techniques (e.g. drill-down)
Identify responsible people
Chapter 11
29
The use of a set of graphical tools that provides
users with multidimensional views of their data
and allows them to analyze the data using simple
windowing techniques
Relational OLAP (ROLAP)
Traditional relational representation
Multidimensional OLAP (MOLAP)
Cube structure
OLAP Operations
Cube slicing – come up with 2-D view of data
Drill-down – going from summary to more detailed
views
Chapter 11
30
Figure 11-22: Slicing a data cube
31
Summary report
Figure 11-23:
Example of drill-down
Starting with
summary data, Drill-down with
users can obtain color added
details for particular
cells
Chapter 11
32
Knowledge discovery using a blend of statistical, AI, and computer
graphics techniques
Goals:
Explain observed events or conditions
Confirm hypotheses
Explore data for new or unexpected relationships
Techniques
Statistical regression
Decision tree induction
Clustering and signal processing
Affinity
Sequence association
Case-based reasoning
Rule discovery
Neural nets
Fractals
Data visualization – representing data in graphical/multimedia formats for
analysis
Chapter 11
33
OLTP: On Line Transaction Processing
Describes processing at operational sites
OLAP: On Line Analytical Processing
Describes processing at warehouse
Chapter 11
34
Standard DB (OLTP) Warehouse (OLAP)
Mostly updates Mostly reads
Many small Queries are long and
transactions
Mb - Gb of data
complex
Current snapshot Gb - Tb of data
Index/hash on p.k. History
Raw data Lots of scans
Thousands of users
Summarized, reconciled
(e.g., clerical users)
data
Hundreds of users (e.g.,
Chapter 11
decision-makers, analysts)
35