MIS 451 Building Business Intelligence Systems

Slides:

Advertisements

Similar presentations

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

Advertisements

Author: Graeme C. Simsion and Graham C. Witt Chapter 11 Logical Database Design.

Chapter 4 Tutorial.

Chapter 4 Tutorial.

Lecture 3 Themes in this session Basics of the multidimensional data model and star- join schemata The process of, and specific design issues in, multidimensional.

Dimensional Modeling.

Tips and Tricks for Dimensional Modeling

MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management

CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.

Cognos 8 Training Session

Business Intelligence Simon Pease. Experience with BI Developing end-to-end BI prototype for Plan International Developing end-to-end BI prototype for.

BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.

Alternative Database topology: The star schema

Copyright © Starsoft Inc, Data Warehouse Architecture By Slavko Stemberger.

Dimensional Modeling CS 543 – Data Warehousing. CS Data Warehousing (Sp ) - Asim LUMS2 From Requirements to Data Models.

Data Warehousing - 2 ISYS 650. Data Warehouse Design - Star Schema - Dimension tables – contain descriptions about the subjects of the business such as.

OLAP. Overview Traditional database systems are tuned to many, small, simple queries. Some new applications use fewer, more time-consuming, analytic queries.

© Ron McFadyen1 Many-to-one-to-many We need information that can only be obtained by accessing two fact tables through a common dimension … drilling across.

MIS 451 Building Business Intelligence Systems Logical Design (5) – Aggregate.

Dimensional Modeling – Part 2

Business Intelligence. On-Line Analytical Processing (OLAP) Tools The use of a set of graphical tools that provides users with multidimensional views.

1 ACCTG 6910 Building Enterprise & Business Intelligence Systems (e.bis) Dimensional Modeling II Olivia R. Liu Sheng, Ph.D. Emma Eccles Jones Presidential.

MIS 451 Building Business Intelligence Systems Logical Design (3) – Design Multiple-fact Dimensional Model.

Data Warehousing ISYS 650. What is a data warehouse? A data warehouse is a subject-oriented, integrated, nonvolatile, time-variant collection of data.

Lecture 5 CS.456 DATABASE DESIGN.

Joins and Cardinality Demystified

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.

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.

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.

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.

Bus Architecture. Value Chain Identifies the natural logical flow of an organization’s primary activities Operational source systems produce snapshots.

BI Terminologies.

Hachim Haddouti, adv. DBMS & DW CSC5301, Ch5 Chapter 5: The Value Chain Adv. DBMS & DW Hachim Haddouti.

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

1 On-Line Analytic Processing Warehousing Data Cubes.

Competitive (Business) Intelligence Systems The Road to Denormalization (starring Charlie Sheen & other Random Celebrities)

Creating the Dimensional Model

MIS 451 Building Business Intelligence Systems Logical Design (1)

Data warehousing theory and modelling techniques Graduate course on dimensional modelling.

June 08, 2011 How to design a DATA WAREHOUSE Linh Nguyen (Elly)

1 Figure 12.2 registration events in factless fact table Faculty Student Course Term Year termKey (FK) studentKey (FK) declaredMajorKey (FK) creditAttainmentKey.

DO NOT COPY --CONFIDENTIAL Homework 5 Partial Key Star Diagrams & Data Warehouse Design BCIS 4660 Dr. Nick Evangelopoulos Spring 2012.

1 Copyright © 2009, Oracle. All rights reserved. Oracle Business Intelligence Enterprise Edition: Overview.

MIS 451 Building Business Intelligence Systems Data Staging.

Data warehousing for Profit Analysis By A Sai Krishna Geethika Lokanadham Mithun Rajanna KV Kumar.

Last Updated : 26th may 2003 Center of Excellence Data Warehousing Introductionto Data Modeling.

Houston Petroleum Valve Company Data-Mining Project Data Modeling Phase Fouad Alibrahim Mohammad H. Monakes University of Houston Clear Lake University.

DATA WAREHOUSING – DIMENSIONAL MODELLING AND SCHEMAS With MIKE –AARONE ATUHE Handout 5.

Building the Corporate Data Warehouse Pindaro Demertzoglou Data Resource Management.

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.

Operation Data Analysis Hints and Guidelines

On-Line Analytic Processing

Competing on Analytics II

Inventory is used to illustrate:

Retail Sales is used to illustrate a first dimensional model

Multivalued Dimensions and Bridges

Assignment 2 Due Thursday Feb 9, 2006

Retail Sales is used to illustrate a first dimensional model

Data warehouse architecture CIF, DM Bus Matrix Star schema

Retail Sales is used to illustrate a first dimensional model

Dimensional Model January 16, 2003

Query Functions.

Power BI Desktop.

Presentation transcript:

MIS 451 Building Business Intelligence Systems Logical Design (4)

D4: Conformed Dimension A conformed dimension table is a dimension table shared by fact tables. Ex: PRODUCT dimension table is shared by two fact tables – SALESFACT and PROCOST. A conformed dimension table should mean the same thing with every fact table to which it is joined. D: refers to special considerations for dimension tables or special types of dimension tables

D4: Conformed Dimension Conformed dimension tables connect separate star schemas into an enterprise star schema. Support drill across queries on star schema

D5: Role-playing Dimension Role-playing dimension is a dimension which plays several simultaneous roles when used with a fact table. In the following star schema, time dimension plays two different roles – ORDERDATE and DELIVERYDATE.

D5: Role-playing Dimension Although ORDERDATE and DELIVERYDATE have exactly the same table structure, they need to be treated as different tables. SALEFACT (CUSTOMER_KEY, PRODUCT_KEY, ORDERDATE_KEY, DELIVERYDATE_KEY, QUANTITY, SALES) ORDERDATE (ORDERDATE_KEY, ODATE, DAY_OF_WEEK, DAY_OF_MONTH) DELIVERYDATE (DELIVERYDATE_KEY, DDATE, DAY_OF_WEEK, DAY_OF_MONTH) Query: List sales of products ordered on Wednesday and delivered on Friday Select sum(sales) From SALEFACT S, ORDERDATE O, DELIVERYDATE D Where S.ORDERDATE_KEY = O. ORDERDATE_KEY AND S. DELIVERYDATE_KEY = D. DELIVERYDATE_KEY AND O.DAY_OF_WEEK = 3 AND D.DAY_OF_WEEK = 5

D5: Role-playing Dimension If we replace ORDERDATE and DELIVERYDATE with one time dimension table SDATE, we get, SALEFACT (CUSTOMER_KEY, PRODUCT_KEY, ORDERDATE_KEY, DELIVERYDATE_KEY, QUANTITY, SALES) SDATE (SDATEID, SDATE, DAY_OF_WEEK, DAY_OF_MONTH) Note: ORDERDATE_KEY and DELIVERYDATE_KEY in SALEFACT table are foreign keys refer to SDATEID in SDATE table. Query: List total sales ordered on Wednesday and delivered on Friday Select sum(sales) From SALEFACT S, SDATE SD Where S.ORDERDATE_KEY = SD.SDATEID AND S.DELIVERYDATE_KEY = SD.SDATEID AND SD.DAY_OF_WEEK = 3 AND SD.DAY_OF_WEEK = 5 This query will return nothing!

F2: Types of Fact Attributes Additive fact attributes can be added along any dimension.

F2: Types of Fact Attributes Non-additive fact attributes cannot be added along any dimension.

F2: Types of Fact Attributes Semi-additive fact attributes can be added along some dimensions.

F3: Factless Fact Table Factless fact table is a fact table that contains only warehouse keys without any fact attributes. Factless fact table is useful for event tracking, such as tracking student class attendance event.

F3: Factless Fact Table

F3: Factless Fact Table Instead of sum function used in common fact tables, query on factless fact tables use count function How may courses did student Mark take on 01/01/99? Select count(course_key) From Attendance A, Attend_time AT, Student S, Course C Where A.Time_key = AT.Time_key AND S.Student_key = A.Student_key AND S.SNAME = ‘Mark’ AND AT.Date = ’01/01/99’

Readings: Chapter 3: p49 – p52 Chapter 5 Chapter 10