Multidimensional Modeling MIS 497. What is multidimensional model? Logical view of the enterprise Logical view of the enterprise Shows main entities of.

Slides:



Advertisements
Similar presentations
Banking Business Scenario
Advertisements

ER Model For a college DB
Chapter 4 Tutorial.
Dimensional Modeling.
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
ER Modeling Case Studies
Alternative Database topology: The star schema
Microsoft Excel Working with Excel Lists, Subtotals and Pivot Tables.
Dimensional Modeling – Part 2
Data Warehouse and Business Intelligence Dr. Minder Chen Spring 2010.
MIS 451 Building Business Intelligence Systems Logical Design (3) – Design Multiple-fact Dimensional Model.
1 Lecture 10: More OLAP - Dimensional modeling
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
Foundation Data Workshop
CSE6011 Warehouse Models & Operators  Data Models  relations  stars & snowflakes  cubes  Operators  slice & dice  roll-up, drill down  pivoting.
Data Warehousing ISYS 650. What is a data warehouse? A data warehouse is a subject-oriented, integrated, nonvolatile, time-variant collection of data.
Turning Data into Actionable Knowledge Presented By: Richard Henning President, Henning Software, Inc.
Data Warehousing DSCI 4103 Dr. Mennecke Introduction and Chapter 1.
Business Intelligence Instructor: Bajuna Salehe Web:
ER Modeling Case Studies
Chapter 5: Modeling Systems Requirements: Events and Things
DWH – Dimesional Modeling PDT Genči. 2 Outline Requirement gathering Fact and Dimension table Star schema Inside dimension table Inside fact table STAR.
Sayed Ahmed Logical Design of a Data Warehouse.  Free Training and Educational Services  Training and Education in Bangla: Training and Education in.
Data Warehouse and the Star Schema CSCI 242 ©Copyright 2014, David C. Roberts, all rights reserved.
IMS 6217: Data Warehousing / Business Intelligence Part 3 1 Dr. Lawrence West, Management Dept., University of Central Florida Analysis.
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
Hachim Haddouti, adv. DBMS & DW CSC5301, Ch4 Adv. DBMS & DW CH 4 Hachim Haddouti.
Datawarehouse & Datamart OLAPs vs. OLTPs Dimensional Modeling Creating Physical Design Using SQL Mgt. Studio Module II: Designing Datamarts 1.
Objects for Business Reporting MIS 497. Objective Learn about miscellaneous objects required for business reporting. Learn about miscellaneous objects.
Ahsan Abdullah 1 Data Warehousing Lecture-11 Multidimensional OLAP (MOLAP) Virtual University of Pakistan Ahsan Abdullah Assoc. Prof. & Head Center for.
Program Pelatihan Tenaga Infromasi dan Informatika Sistem Informasi Kesehatan Ari Cahyono.
1 Data Warehousing Lecture-13 Dimensional Modeling (DM) Virtual University of Pakistan Ahsan Abdullah Assoc. Prof. & Head Center for Agro-Informatics Research.
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.
Ahsan Abdullah 1 Data Warehousing Lecture-10 Online Analytical Processing (OLAP) Virtual University of Pakistan Ahsan Abdullah Assoc. Prof. & Head Center.
BUSINESS ANALYTICS AND DATA VISUALIZATION
DEFINING the BUSINESS REQUIREMENTS. Introduction OLTP and DW planning is different in term of requirements clarity Planning DW is about solving users’
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
DIMENSIONAL MODELING MIS2502 Data Analytics. So we know… Relational databases are good for storing transactional data But bad for analytical data What.
Modeling Issues for Data Warehouses CMPT 455/826 - Week 7, Day 1 (based on Trujollo) Sept-Dec 2009 – w7d11.
UNIT-II Principles of dimensional modeling
Shilpa Seth.  Multidimensional Data Model Concepts Multidimensional Data Model Concepts  Data Cube Data Cube  Data warehouse Schemas Data warehouse.
1 On-Line Analytic Processing Warehousing Data Cubes.
Data Warehousing Multidimensional Analysis
1 Agenda – 04/02/2013 Discuss class schedule and deliverables. Discuss project. Design due on 04/18. Discuss data mart design. Use class exercise to design.
Fact Table The fact table stores business events. The attributes explain the conditions of the entity at the time the business event happened.
Advanced Data Modeling. Heterogeneous Mapping Heterogeneous Mapping is the ability of MSTR7 tools to join on unlike column names. Heterogeneous Mapping.
Centre of Competence on data warehouse Workshop Helsinki Database Cube and Browsing the Cube Mark Rantala.
ISAM 5931: Data Warehousing & Data Mining Group Project submitted by : Mudassar Hakim & Gaurav Wadhwani.
Copyright© 2014, Sira Yongchareon Department of Computing, Faculty of Creative Industries and Business Lecturer : Dr. Sira Yongchareon ISCG 6425 Data Warehousing.
CIS Information and Databases 1 Information and Databases.
Modeling Your Data Chapter 2 cs5421. Part II Discussion of the Model: Good Design/ Bad Design? cs5422.
Order Database – ER Diagram Prepared by Bryan Borcher Spring 2014.
Last Updated : 26th may 2003 Center of Excellence Data Warehousing Introductionto Data Modeling.
SQL Server Analysis Services Understanding Unified Dimension Model (UDM)
The Need for Data Analysis 2 Managers track daily transactions to evaluate how the business is performing Strategies should be developed to meet organizational.
3 Copyright © 2006, Oracle. All rights reserved. Business, Logical, and Dimensional Modeling.
Houston Petroleum Valve Company Data-Mining Project Data Modeling Phase Fouad Alibrahim Mohammad H. Monakes University of Houston Clear Lake University.
Pindaro Demertzoglou Data Resource Management – MGMT 4170 Lally School of Management Rensselaer Polytechnic Institute.
DATA SCIENCE MIS0855 | Spring 2016 Designing Data
Operation Data Analysis Hints and Guidelines
Data warehouse and OLAP
Retail Sales is used to illustrate a first dimensional model
Retail Sales is used to illustrate a first dimensional model
Retail Sales is used to illustrate a first dimensional model
Dimensional Model January 16, 2003
DWH – Dimesional Modeling
Analysis Services Analysis Services vs. the Data Warehouse vs. OLTP DB
Presentation transcript:

Multidimensional Modeling MIS 497

What is multidimensional model? Logical view of the enterprise Logical view of the enterprise Shows main entities of the enterprise business and relationships between them Shows main entities of the enterprise business and relationships between them Not tied to a physical database and tables Not tied to a physical database and tables Not E-R diagram Not E-R diagram

Model Components Dimensions (Hierarchies in MSTR 7) Dimensions (Hierarchies in MSTR 7) Attributes Attributes Facts Facts Relationships Relationships

Multidimensional Data Model Example Time Year Quarter Month Day Geography Country Region City Store Products Division Department Category Item Store Manager

Attributes Attributes are abstract items with business relevance that are created for convenient qualification or summarization of data on a report. Attributes are abstract items with business relevance that are created for convenient qualification or summarization of data on a report. Attribute can also be defined as column headings on a report that are not a calculation Attribute can also be defined as column headings on a report that are not a calculation

Attribute relationships One to One One to One –Each customer has only one SSN. One to Many One to Many –Each customer can have several addresses. Many to Many Many to Many –Each customer can buy many items, an item can be purchased by many customers (item means SKU, not the same physical object). Many to One Many to One –Several phone numbers can belong to one store, and one store only.

Attribute relationships Out of all relationships, Many to Many is the trickiest one. If not modeled carefully, M;N can lead to double-counting and other unhappy consequences. Out of all relationships, Many to Many is the trickiest one. If not modeled carefully, M;N can lead to double-counting and other unhappy consequences. Practical ways of dealing with M;N relationships: Practical ways of dealing with M;N relationships: –Create a relationship table –Create a compound key »Not advisable, but sometimes necessary

Hierarchies (Dimensions) Hierarchies have the same meaning as Dimensions in MicroStrategy 7. Hierarchies have the same meaning as Dimensions in MicroStrategy 7. Hierarchies are based on relationships between Attributes. They allow end users to define and order groups of Attributes for display and browsing purposes. Hierarchies are based on relationships between Attributes. They allow end users to define and order groups of Attributes for display and browsing purposes. Time Year Quarter Month Day

Facts Data columns (usually numeric) that can be used to perform calculations needed to answer business questions. Data columns (usually numeric) that can be used to perform calculations needed to answer business questions. Facts are stored in Fact Tables or Base Tables Facts are stored in Fact Tables or Base Tables Facts can be aggregated on different levels: Facts can be aggregated on different levels: Aggregated on Region level Aggregated on Country level

Facts (continued) Same facts can be represented by different column name in the DW due to various historical and design reasons. Same facts can be represented by different column name in the DW due to various historical and design reasons. In the example below the same fact has two different names: SALES and DOLLAR_SALES In the example below the same fact has two different names: SALES and DOLLAR_SALES Facts are cross-dimensional, not limited to one dimension only. In the example above, the same fact crosses two dimensions: Geography and Time. Facts are cross-dimensional, not limited to one dimension only. In the example above, the same fact crosses two dimensions: Geography and Time.

Facts (continued) Facts are used to create metrics. Facts are used to create metrics. Metrics - business measurements (i.e. Dollar Sales, Units Sold, Gross Margin and etc.) used by businesses to analyze and report their performance. Metrics - business measurements (i.e. Dollar Sales, Units Sold, Gross Margin and etc.) used by businesses to analyze and report their performance. Metrics are usually a fact that has a mathematical function applied to it (sum, average, max, min and etc.) Metrics are usually a fact that has a mathematical function applied to it (sum, average, max, min and etc.) More on metrics in a separate presentation More on metrics in a separate presentation

What to read for more information: MicroStrategy 7 Project designer guide. MicroStrategy 7 Project designer guide. Have a good look at VMALL Data Model Have a good look at VMALL Data Model –Identify attributes, hierarchies and facts – you’ll need them for the Workshop.