Modeling the Data Warehouse Chapter 7. Data Warehouse Database Design Phases zDefining the business model (conceptual model) zCreating the dimensional.

Slides:



Advertisements
Similar presentations
The Organisation As A System An information management framework The Performance Organiser Data Warehousing.
Advertisements

Dimensional Modeling.
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
An overview of Data Warehousing and OLAP Technology Presented By Manish Desai.
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
Copyright © Starsoft Inc, Data Warehouse Architecture By Slavko Stemberger.
Data Warehousing M R BRAHMAM.
Dimensional Modeling Business Intelligence Solutions.
Dimensional Modeling CS 543 – Data Warehousing. CS Data Warehousing (Sp ) - Asim LUMS2 From Requirements to Data Models.
© Copyright 2011 John Wiley & Sons, Inc.
Designing the data warehouse / data marts Methodologies and Techniques.
Dimensional Modeling – Part 2
Exploiting the DW data DW is a platform for creating a wide array of reports It solves data feed problems, but does not lead to specific decision support.
Designing the data warehouse / data mart Methodologies and Techniques.
Data Warehousing - 3 ISYS 650. Snowflake Schema one or more dimension tables do not join directly to the fact table but must join through other dimension.
MIS 451 Building Business Intelligence Systems Logical Design (3) – Design Multiple-fact Dimensional Model.
5 Creating the Physical Model. Designing the Physical Model Phase IV: Defining the physical model.
CSE6011 Warehouse Models & Operators  Data Models  relations  stars & snowflakes  cubes  Operators  slice & dice  roll-up, drill down  pivoting.
Chapter 13 The Data Warehouse
Leaving a Metadata Trail Chapter 14. Defining Warehouse Metadata Data about warehouse data and processing Vital to the warehouse Used by everyone Metadata.
1 Sharif University Data Warehouse. 2 Sharif University Objectives Need for Data Warehouse. What is Data Warehouse? Data Warehouse Properties. Data Warehouse.
Data Warehouse Chapter 11. Multiple Files Problem Added complexity of multiple source files Start simple Multiple Source files Extracted data Logic to.
Multi-Dimensional Databases & Online Analytical Processing This presentation uses some materials from: “ An Introduction to Multidimensional Database Technology,
OnLine Analytical Processing (OLAP)
Data Warehouse and Business Intelligence Dr. Minder Chen Fall 2009.
ISQS 3358, Business Intelligence Dimensional Modeling Zhangxi Lin Texas Tech University 1 1.
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 models in higher education courses Patrizia Poščić, Associate Professor Danijela Subotić, Teaching Assistant.
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.
Module 1: Introduction to Data Warehousing and OLAP
BI Terminologies.
Decision Support and Date Warehouse Jingyi Lu. Outline Decision Support System OLAP vs. OLTP What is Date Warehouse? Dimensional Modeling Extract, Transform,
DIMENSIONAL MODELING MIS2502 Data Analytics. So we know… Relational databases are good for storing transactional data But bad for analytical data What.
MIS2502: Data Analytics Dimensional Data Modeling
3 Defining the Business and Logical Models. Designing the Conceptual Model Phase I: Functional and Nonfunctional Requirements.
Designing a Data Warehousing System. Overview Business Analysis Process Data Warehousing System Modeling a Data Warehouse Choosing the Grain Establishing.
UNIT-II Principles of dimensional modeling
Creating the Dimensional Model
7 Strategies for Extracting, Transforming, and Loading.
Pooja Sharma Shanti Ragathi Vaishnavi Kasala. BUSINESS BACKGROUND Lowe's started as a single hardware store in North Carolina in 1946 and since then has.
Chapter 4 Logical & Physical Database Design
ISAM 5931: Data Warehousing & Data Mining Group Project submitted by : Mudassar Hakim & Gaurav Wadhwani.
1 Copyright © 2009, Oracle. All rights reserved. Oracle Business Intelligence Enterprise Edition: Overview.
Copyright © Archer Decision Sciences, Inc. Our Model Store DimensionProduct Dimension District Region Total Brand Manufacturer Total StoresProducts.
Analyzing User Query Needs Chapter 6. Types of Users zExecutives zManagers zBusiness analysts.
Last Updated : 26th may 2003 Center of Excellence Data Warehousing Introductionto Data Modeling.
The Need for Data Analysis 2 Managers track daily transactions to evaluate how the business is performing Strategies should be developed to meet organizational.
4 Copyright © Oracle Corporation, All rights reserved. Modeling the Data Warehouse.
1 Copyright © 2006, Oracle. All rights reserved. Defining OLAP Concepts.
3 Copyright © 2006, Oracle. All rights reserved. Business, Logical, and Dimensional Modeling.
Introduction to OLAP and Data Warehouse Assoc. Professor Bela Stantic September 2014 Database Systems.
Data Warehouses and OLAP 1.  Review Questions ◦ Question 1: OLAP ◦ Question 2: Data Warehouses ◦ Question 3: Various Terms and Definitions ◦ Question.
7 Copyright © 2006, Oracle. All rights reserved. Defining a Relational Dimensional Model.
9 Copyright © 2006, Oracle. All rights reserved. Summary Management.
CSE6011 Implementing a Warehouse  Monitoring: Sending data from sources  Integrating: Loading, cleansing,...  Processing: Query processing, indexing,...
Defining Data Warehouse Structures Data Warehouse Data Access End User Data Access Data Sources Staging Area Data Marts Data Extract, Transform, and Load.
Advanced Applied IT for Business 2
ISQS 3358, Business Intelligence Dimensional Modeling
Data warehouse and OLAP
Chapter 13 The Data Warehouse
Data Warehouse.
MIS2502: Data Analytics Dimensional Data Modeling
ISQS 3358, Business Intelligence Dimensional Modeling
MIS2502: Data Analytics Dimensional Data Modeling
Retail Sales is used to illustrate a first dimensional model
MIS2502: Data Analytics Dimensional Data Modeling
Dimensional Model January 16, 2003
Data Warehousing.
Presentation transcript:

Modeling the Data Warehouse Chapter 7

Data Warehouse Database Design Phases zDefining the business model (conceptual model) zCreating the dimensional model (logical model) zModeling summaries zCreating the physical model Select a business process Physical model 2,3

Performing Strategic Analysis Phase 1: Defining the Business Model Select a business process Performing strategic analysis Creating the business (conceptual) model

Creating the Business Model Phase 1: Defining the Business Model Performing strategic analysis ’ Creating the business (conceptual)model - Defining business requirements - Identifying the business measures - Identifying the dimensions - Identifying the grain - Identifying the business definitions and rules - Verifying data sources

Phase 1: Defining the Business Model Creating the Business Model Performing strategic analysis Creating the business (conceptual) model - Defining business requirements - Identifying the business measures - Identifying the dimensions - Identifying the grain - Identifying the business definitions and rules - Verifying data sources

Business Requirements Drive the Design Process Primary input Other inputs Business requirements Existing metadata Production ERD model ResearchNonrelational legacy systems

Identifying Measures and Dimensions The attribute varies continuously: Balance United Sold Cost Sales The attribute is perceived as a constant or discrete value: Description Location Color Size DimensionsMeasures

Determining Granularity YEAR? QUARTER? MONTH? WEEK? DAY?

Identifying Business Rules Location Geographic proximity miles miles > 5 miles Product Type Monitor Status PC 15 inch New Server 17 inch Rebuilt 19 inch Custom None Time Month>Quarter>Year Store Store>District>Region

Creating the Dimensional Model Identify fact tables - Translate business measures into fact tables - Analyze source system information for additional measures - Identify base and derived measures - Document additivity of measures Identify dimension tables Link fact tables to the dimension tables Create views for users

Dimension Tables Dimension tables have the following characteristics: zContain textual information that represents the attributes of the business zContain relatively static data zAre joined to a fact table through a foreign key reference Facts (units, price) Channel Time Product Customer

Fact Tables Fact tables have the following characteristics: zContain numeric measures (metric) of the business zMay contain summarized (aggregated) data zMay contain date-stamped data zAre typically additive zHave key value that is typically a concatenated key composed of the primary keys of the dimensions zJoined to dimension tables through foreign keys that reference primary keys in the dimension tables

Facts (units, price) Channel Time Product Customer Fact table Dimension tables

Star Schema Model zCentral fact table zRadiating dimensions zDenormalized model Sales Fact Table Product_id Store_ id Item_id Day_id Sales_dollars Sales_units Product Table Product_id Product_desc Store Table Store_id District_id Time Table Day_id Month_id Year_id Item Table Item_id Item_desc

Star Schema Model zEasy for users to understand zFast response to queries zSimple metadata zSupported by many front end tools zLess robust to change zSlower to build zDoes not support history

Snowflake Schema Model Sales Fact Table Product_id Store_ id Item_id Day_id Sales_dollars Sales_units Product Table Product_id Product_desc Store Table Store_id District_id Time Table Day_id Month_id Year_id Item Table Item_id Item_desc District Table District_id District_desc Dept Table Dept_id Dept_desc Mgr_id Mgr Table Dept_id Mgr_id Mgr_name

Snowflake Schema Model zDirect use by some tools zMore flexible to change zProvides for speedier data loading zMay become large and unmanageable zDegrades query performance zMore complex metadata CountryStateCountyCity

Using Summary Data Phase 3: Modeling summaries zProvides fast access to precomputed data zReduces use of I/O, CPU, and memory zIs distilled from source systems and precalculated summaries zUsually exists in summary fact tables

Designing Summary Tables zAverage zMaximum zTotal zPercentage UnitsSales($)Store Product A Total Product B Total Product C Total

Summary Tables Example SALES FACTS Sales$ Region Month 10,000 North Jan 99 12,000 North Feb 99 11,000 South Jan 99 15,000 West Mar 99 18,000 South Feb 99 20,000 North Jan 99 10,000 East Jan 99 2,000 West Mar 99 SALES BY MONTH/REGION Month Region Tot_Sales$ Jan 99 North 41,000 Jan 99 East 10,000 Feb 99 South 40,000 Mar 99 West 17,000 SALES BY_MONTH Month Tot_Sales Jan 99 51,000 Feb 99 40,000 Mar 99 17,000

Summary Management in Oracle8i Summary advisor Summary recommendations Space requirements Summary usage Region State City ProductTime Sales summary

Using Time in the Data Warehouse

The Time Dimension zTime is critical to the data warehouse zA consistent representation of time is required for extensibility Sales fact Time dimension Where should the element of time be stored?

Creating the Physical Model Phase 4: Creating the Physical Model Translate the dimensional design to a physical model for implementation Define storage strategy for tables and indexes Perform database sizing Define initial indexing strategy Define partitioning strategy Update metadata document with physical information

Physical Model Design Tasks zDefine naming and database standards zPerform database sizing zDesign tablespaces zDevelop initial indexing strategy zDevelop data partition strategy zDefine storage parameters zSet initialization parameters zUse parallel processing

Using Data Modeling Tools zTools with a GUI enable definition, modeling, and reporting zAvoid a mix of modeling techniques caused by: - Development pressure - Developers with lack of knowledge - No strategy zDetermine a strategy zWrite and publish formally zMake available electronically Spreadsheets CASE tools Paper and pencil

Summary This lesson discussed the following topics: zCreating a business model zCreating a dimensional model zModeling the summaries zCreating a physical model Select among business processes Physical model 2,3 Business model Dimensional model