7023T - S9 - R0

Course: 7023T - Advanced Database Systems
Dimensional Design (Cont’d)

Session 9
Learning Outcomes
Understand the purpose of the development life
cycle and how this cycles relates to the database
ware house development lifecycle. To describe
the activities associates with each stage of the
database ware house lifecycle. To introduce the
dimensional modelling, a high-level conceptual
data model, and to discuss the usefulness of this
modelling technique in the data warehouse
design.
Bina Nusantara University 3
Acknowledgements
These slides have been adapted from Kimball,
Ralph & Ross, Margy. (1998). The Data
Warehouse Life Cycle Toolkit: Expert Methods
for Designing, Developing, and Deploying Data
Warehouse. Second edition. John Wiley & Sons.
New York
Bina Nusantara
Outline Materi
Dimensional Design
• Degenerate Transaction Number
Dimension
• Schema in Action
• Schema Extensibility
• Dimension Normalization (Snowflaking)
• Surrogate Keys
5
Bina Nusantara
Extended Dimension Table Designs
• Many-to-Many Dimensions
6
Bina Nusantara
schema with a diagnosis dimension that can take only one value at a time
Bina Nusantara University

7
Solving the multiple diagnosis problem with a diagnosis group bridge table

8
Solving the multiple customers per account problem
with an account- to-customer bridge table
9
• Many-to-One-to-Many Traps
10
Bina Nusantara
A many-to-one-to-many schema that should not be queried with one
SELECT statement
11
• Role-Playing Dimensions
– A role in a data warehouse is a situation where a
single dimension appears several times in the same
fact table. This can happen in a number of ways. For
instance, in certain kinds of fact tables, time can
appear repeatedly.
12
Bina Nusantara
• Organization and Parts Hierarchies
13
Bina Nusantara
Organization and Parts Hierarchies
A schematic diagram of a set of parent companies and subsidiaries,

all of whom may be customers
14
A commercial customer dimension with

a recursive parent customer key link
15
A commercial customer dimension with a navigation bridge table

that allows natural SQL reporting at all levels of the tree
16
This different configuration of joins between the navigation bridge

table and the other tables is used to climb up the tree
17
• Unpredictably Deep Hierarchies
18
Bina Nusantara
A manufacturing profile subdimension is used to model an

unpredictably deep hierarchy
19
• Time Stamping the Changes in a Large
Dimension
20
Bina Nusantara
A model for a human resources environment with an employee

transaction dimension time stamped with current and next
transaction dates and times
21
Dimension
• Building an Audit Dimension
22
Bina Nusantara
An audit dimension can be used to accurately track the lineage of

individual records in the fact table
23
Dimension
• Building an Audit Dimension
• Too Few Dimensions and Too Many
Dimensions 24
Bina Nusantara
Extended Fact Table Designs
• Facts of Differing Granularity and
Allocating
25
Bina Nusantara
A shipment invoices fact table showing how a full view of profitability

can be expressed at the invoice line item level by allocating costs to
26
the lowest level
When an aggregate table and a plan table share exactly the same
Bina Nusantara University dimensions, it may be reasonable to combine them into a single 27
physical table
A plan table with an extra dimension (plan version) that makes it

impossible to combine with an aggregate table 28
A fact table with facts at the wrong grain

29
Allocating
• Time of Day
30
Bina Nusantara
A sales fact table with transaction time recorded to the minute and
split off from the transaction date 31
A sales fact table spanning multiple time zones where comparing

comparable telesales across time zones is required 32
Allocating
• Time of Day
• Multiple Units of Measure
33
Bina Nusantara
The wrong design when fact table quantities need to be expressed

in several units of measure
34
The recommended design for multiple units of measure places the

Bina Nusantara University conversion factors directly in the fact table record to eliminate the 35
possibility of choosing the wrong factors
Allocating
• Time of Day
• Multinational Currency Tracking
36
Bina Nusantara
Tracking transactions in multiple currencies requires a daily

currency exchange conversion fact table 37
Allocating
• Time of Day
• Multinational Currency Tracking
• Value Band Reporting
38
Bina Nusantara
Arbitrary value band reporting can be done with a band definition

Bina Nusantara University table and a pair of nonequijoins 39
Advanced ROLAP Querying and Reporting
• Drill-Across Queries with Multiple
Technologies
40
Bina Nusantara
The query architecture for disparate conformed data sources

41
• Drill-Across Queries with Multiple Technologies
• Self Referencing Queries, Behavior Tracking, and
Sequential Subsetting
1. Simple constraints
2. Simple subqueries
3. Correlated subqueries
4. Simple behavioral queries
5. Derived behavioral queries
6. Progressive subsetting queries.
7. Classification queries
42
Bina Nusantara
A special behavior dimension consisting only of keys of some

selected dimension can be attached directly to any fact table
containing that dimension’s keys
43
• Drill-Across Queries with Multiple Technologies
• Self Referencing Queries, Behavior Tracking, and
Sequential Subsetting
• Market Basket Analysis
44
Bina Nusantara
A market basket fact table populated from a sales fact table,

showing the product keys that must be generalized to handle either
base-level products or aggregate-level products, in any mixture
45
Acknowledgements
These slides have been adapted from Kimball,
Ralph & Ross, Margy. (1998). The Data
Warehouse Life Cycle Toolkit: Expert Methods
for Designing, Developing, and Deploying Data
Warehouse. Second edition. John Wiley & Sons.
New York
Bina Nusantara
Outline Materi
Dimensional Design
• Degenerate Transaction Number
Dimension
• Schema in Action
• Schema Extensibility
• Dimension Normalization (Snowflaking)
• Surrogate Keys
47
Bina Nusantara
Matrix Method for Getting Started
• Build the Matrix
– Do the Necessary Homework
– List the Data Marts
– List the Dimensions
– Mark the Intersections
48
Bina Nusantara
The Data Warehouse Bus Architecture matrix
for a telephone company
49
Use the Four-Step Method to Design Each
Fact Table
• Step 1. Choose the Data Mart
• Step 2. Declare the Grain
• Step 3. Choose the Dimensions
• Step 4. Choose the Facts
50
Bina Nusantara
Managing the Dimensional Modeling Project
• Data Warehouse Bus Architecture Matrix

• Fact Table Diagram
51
Bina Nusantara
The telephone billing fact table diagram.
Disconnected dimensions are shown on both sides of the diagram
52

• Fact Table Diagram: serves multiple
communications purposes
– Link between IS and users
– Help with data access tool selection
– End user training
53
Bina Nusantara

• Fact Table Detail
54
Bina Nusantara
Fact table detail diagram showing dimension keys,
basic facts, and derived facts (with asterisks)
55

• Dimension Table Detail
56
Bina Nusantara
Dimension table detail diagram
(relative cardinalities shown in parentheses)
57
– Attribute name
– Attribute definition
– Cardinality
– Sample data
– Slowly changing policy
– Many-to-many relationships
– Slowly changing dimensions
– Artificial attributes 58
Bina Nusantara
Many-to-many and slowly changing dimension attributes

59
A dimension with a correlated attribute

60
• Steps for the Dimensional Modeling Team
– Create the Initial Draft
– Track Base Facts and Derived Facts
– Get IS Team Input
– Work with Core Business Users
– Present to Business Users
61
Bina Nusantara
• Identifying the Sources for Each Fact Table and
Dimension Table
62
Bina Nusantara
• ….
Dimension Table
– Understanding Candidate Data Sources
– Source Data Ownership
– Data Providers
– Detailed Criteria for Selecting the Data Sources
– Customer Matching and Householding
– Browsing the Data Content
– Mapping Data from Source to Target
63
Bina Nusantara
• …….
• Using a Data Modeling Tool
– Estimating the Number of Rows
– Designing for Aggregation
– Deciding What to Aggregate
64
Bina Nusantara
Dimension Table
• When Are You Done?
• Using a Data Modeling Tool
65
Bina Nusantara

7023T - S9 - R0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7023T - S9 - R0

Uploaded by

Copyright:

Available Formats

Course: 7023T - Advanced Database Systems

Dimensional Design (Cont’d)

Bina Nusantara University

Bina Nusantara University

A schematic diagram of a set of parent companies and subsidiaries,

A commercial customer dimension with

A commercial customer dimension with a navigation bridge table

This different configuration of joins between the navigation bridge

A manufacturing profile subdimension is used to model an

A model for a human resources environment with an employee

An audit dimension can be used to accurately track the lineage of

A shipment invoices fact table showing how a full view of profitability

A plan table with an extra dimension (plan version) that makes it

A fact table with facts at the wrong grain

A sales fact table spanning multiple time zones where comparing

The wrong design when fact table quantities need to be expressed

The recommended design for multiple units of measure places the

Tracking transactions in multiple currencies requires a daily

Arbitrary value band reporting can be done with a band definition

The query architecture for disparate conformed data sources

Bina Nusantara University

A special behavior dimension consisting only of keys of some

A market basket fact table populated from a sales fact table,

• Data Warehouse Bus Architecture Matrix

• Data Warehouse Bus Architecture Matrix

• Data Warehouse Bus Architecture Matrix

• Data Warehouse Bus Architecture Matrix

Bina Nusantara University

Bina Nusantara University

You might also like