Overview and Fundamentals

Slides:



Advertisements
Similar presentations
Data Warehousing Design Transparencies
Advertisements

Dimensional Modeling.
Tips and Tricks for Dimensional Modeling
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Cognos 8 Training Session
IS 4420 Database Fundamentals Chapter 11: Data Warehousing Leon Chen
Copyright © Starsoft Inc, Data Warehouse Architecture By Slavko Stemberger.
Technical BI Project Lifecycle
Dimensional Modeling Business Intelligence Solutions.
Dimensional Modeling CS 543 – Data Warehousing. CS Data Warehousing (Sp ) - Asim LUMS2 From Requirements to Data Models.
Data Warehouse IMS5024 – presented by Eder Tsang.
Chapter 13 The Data Warehouse
1 © Prentice Hall, 2002 Chapter 11: Data Warehousing.
Data Warehousing DSCI 4103 Dr. Mennecke Introduction and Chapter 1.
Agenda Common terms used in the software of data warehousing and what they mean. Difference between a database and a data warehouse - the difference in.
Business Intelligence
Best Practices for Data Warehousing. 2 Agenda – Best Practices for DW-BI Best Practices in Data Modeling Best Practices in ETL Best Practices in Reporting.
Data Warehouse Architecture. Inmon’s Corporate Information Factory The enterprise data warehouse is not intended to be queried directly by analytic applications,
Dimensional model. What do we know so far about … FACTS? “What is the process measuring?” Fact types:  Numeric Additive Semi-additive Non-additive (avg,
Program Pelatihan Tenaga Infromasi dan Informatika Sistem Informasi Kesehatan Ari Cahyono.
Data Warehousing Concepts, by Dr. Khalil 1 Data Warehousing Design Dr. Awad Khalil Computer Science Department AUC.
Data Warehouse and Business Intelligence Dr. Minder Chen Fall 2009.
DIMENSIONAL MODELLING. Overview Clearly understand how the requirements definition determines data design Introduce dimensional modeling and contrast.
Chapter 1 Adamson & Venerable Spring Dimensional Modeling Dimensional Model Basics Fact & Dimension Tables Star Schema Granularity Facts and Measures.
Data Warehouse. Design DataWarehouse Key Design Considerations it is important to consider the intended purpose of the data warehouse or business intelligence.
1 Data Warehouses BUAD/American University Data Warehouses.
Data Warehousing.
BI Terminologies.
INVENTORY CASE STUDY. Introduction Optimized inventory levels in stores can have a major impact on chain profitability: minimize out-of-stocks reduce.
MIS2502: Data Analytics The Information Architecture of an Organization.
Normalized model vs dimensional model
Designing a Data Warehousing System. Overview Business Analysis Process Data Warehousing System Modeling a Data Warehouse Choosing the Grain Establishing.
More Dimensional Modeling. Facts Types of Fact Design Transactional Periodic Snapshot –Predictable time period –Ex. Monthly, yearly, etc. Accumulating.
UNIT-II Principles of dimensional modeling
Chapter 5 DATA WAREHOUSING Study Sections 5.2, 5.3, 5.5, Pages: & Snowflake schema.
Business Intelligence Transparencies 1. ©Pearson Education 2009 Objectives What business intelligence (BI) represents. The technologies associated with.
June 08, 2011 How to design a DATA WAREHOUSE Linh Nguyen (Elly)
1 Copyright © 2009, Oracle. All rights reserved. Oracle Business Intelligence Enterprise Edition: Overview.
Data Warehousing DSCI 4103 Dr. Mennecke Chapter 2.
Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 9: DATA WAREHOUSING.
Data Warehouse/Data Mart It’s all about the data.
Jaclyn Hansberry MIS2502: Data Analytics The Things You Can Do With Data The Information Architecture of an Organization Jaclyn.
Operation Data Analysis Hints and Guidelines
Advanced Applied IT for Business 2
Chapter 13 Business Intelligence and Data Warehouses
Chapter 13 The Data Warehouse
Data Warehouse—Subject‐Oriented
Summarized from various resources Modern Database Management
Data Warehousing Business Intelligence
Star Schema.
Applying Data Warehouse Techniques
Competing on Analytics II
Dimensional Model January 14, 2003
Inventory is used to illustrate:
Retail Sales is used to illustrate a first dimensional model
Applying Data Warehouse Techniques
Typically data is extracted from multiple sources
Retail Sales is used to illustrate a first dimensional model
Applying Data Warehouse Techniques
Warehouse Architecture
Data warehouse architecture CIF, DM Bus Matrix Star schema
Dimensional Modeling.
Retail Sales is used to illustrate a first dimensional model
Dimensional Model January 16, 2003
Applying Data Warehouse Techniques
Chapter 13 The Data Warehouse
Examines blended and separate transaction schemas
Review of Major Points Star schema Slowly changing dimensions Keys
Technical Architecture
Applying Data Warehouse Techniques
Presentation transcript:

Overview and Fundamentals Dimensional Modeling Overview and Fundamentals

What Is Dimensional Modeling?

Dimensional Modeling An Overview The Fundamentals Structure Terminology Benefits The Fundamentals Facts and Dimensions The 4 Step Design Process

What does Data Warehouse look like Kimball Data Warehouse Back Room Staging Area (The kitchen) Data Presentation Area (The Dinning Room) Star Schema Corporate Information Factory (CIF) Normalized Dimensions Dual ETL Loading, Warehouse and Data Marts Operational Data Store (ODS) Hybrid Data Warehouse

Kimball Data Warehouse

Corporate Information Factory

Terminology Dimensions The time independent, textual and descriptive attributes by which users describe objects. Combining all the attributes including hierarchies, rollups and sub-references into a single dimension is denormalization. Often the “by” word in a query or report Not time dependent Facts Business Measurements Most Facts are Numeric Additive, Semi-Additive, Non-Additive Built from the lowest level of detail (grain) Very Efficient Time dependent

Star Schema Singe data (fact) table surrounded by multiple descriptive (dimension) tables

Benefits Performance (Integer relationships, natural partitioning, Single joins benefit SQL optimizer) Source system independence and multiple integration Supports Change management Usability/Simplicity (easy to read, interpret, join, calculate) Presentation (Consistency, Taxonomy, Labeling) Reuse (Conformed dimensions reduce redundancy, Role-plays)

Dimension Change Strategy Type 1: Is used when the old value of the attribute has no significance or can be discarded. Easy and Fast Type2: Partitions history so that fact tables properly reflect original values. Requires use of Surrogate Keys Causes table growth due to additional history rows Users must be aware of the added complexity Effective Dates used secondary to cleaner fact joins

Dimension Change Strategy Type 3: Additional attribute used to capture changes. Used less frequently then Type 1 or 2. Simultaneously supports two views of the world. Does not trend changes over time. Current and Prior or Current and Original Attributes Hybrid Type: Combination 1, 2 & 3 changes New attribute for predictable series (such as yearly changes) Type 2 changes with prior or original attributes included Expanded dimension table for durable key inclusion in fact Added complexity to users

Dimension Role Playing A single table that plays multiple roles (using views) to create synonym dimension attributes. Most common role playing dimension is the Date Dimension. i.e. separate role playing dimensions for order date and ship date.

Fact Table Types Characteristic Transaction Periodic Snapshot Accumulating Snapshot Time period Point in time Regular, predictable intervals Indeterminate time span, typically short-lived. Grain One row per transaction event One row per period One row per life Fact table loads Insert Insert and Update Fact row updates Not revisited Revisited whenever activity Date dimension Transaction date End-of-period date Multiple dates for multiple milestones Facts Transaction activity Performance for a predefined time interval. Performance over finite lifetime

Modeling Design Process Identify the Business Process Source of “measurements” Identify the Grain What does 1 row in the fact table represent or mean? Identify the Dimensions Descriptive context, true to the grain Identify the Facts Numeric additive measurements, true to the grain

Step 1 - Identify the Business Process This is a business activity typically tied to a source system. Not to be confused with a business department or function. An Orders dimensional model should support the activities of both Sales and Marketing. “If we establish departmentally bound dimensional models, we’ll inevitably duplicate data with different labels and terminology.”

Step 2 - Identify the Grain The level of detail associated with the fact table measurements. A critical step necessary before steps 3 and 4. Preferably it should be at the most atomic level possible. “How do you describe a single row in the fact table?”

Step 3 - Identify the Dimensions The list of all the discrete, text-like attributes that emanate from the fact table. They are the “by” words used to describe the requirements. Each dimension could be though of as an analytical “entry point” to the facts. “How do business people describe the data that results from the business process?”

Step 4 - Identify the Facts Must be true to the grain defined in step 2. Typical facts are numeric additive figures. Facts that belong to a different grain belong in a separate fact table. Facts are determined by answering the question, “What are we measuring?” Percentages and ratios, such as gross margin, are non-additive. The numerator and denominator should be stored in the fact table.

For More Information Articles, Design Tips and Newsletters http://www.kimballgroup.com Designing A Scalable DW/BI System http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032297070&EventCategory=4&culture=en-US&CountryCode=US Microsoft BI Using the Kimball Method http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032297084&EventCategory=4&culture=en-US&CountryCode=US Using SSIS to Populate a Kimball Method Data Warehouse http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032297072&EventCategory=5&culture=en-US&CountryCode=US