Business Intelligence/ Decision Models Week 2 IT Infrastructure & Marketing Database Design and Implementation.

Slides:



Advertisements
Similar presentations
Dimensional Modeling.
Advertisements

CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
DATAWAREHOUSE FOR BANKING by Amey Aras Deepesh Dhake Hatem Murad Nirav Hamlai.
Alternative Database topology: The star schema
Outline What is a data warehouse? A multi-dimensional data model Data warehouse architecture Data warehouse implementation Further development of data.
Figure 5.1 Hierarchy of data for a computer-based file.
Copyright © Starsoft Inc, Data Warehouse Architecture By Slavko Stemberger.
Database Management n Database Hierarchy n File-oriented Approach n Database-oriented Approach n DBMS n Entity Relationship Diagram n Data Structures.
Dimensional Modeling Business Intelligence Solutions.
Data Warehouse IMS5024 – presented by Eder Tsang.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Key.
Chapter Physical Database Design Methodology Software & Hardware Mapping Logical Design to DBMS Physical Implementation Security Implementation Monitoring.
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.
Chapter 14 The Second Component: The Database.
Databases and Database Management Systems
CSE6011 Warehouse Models & Operators  Data Models  relations  stars & snowflakes  cubes  Operators  slice & dice  roll-up, drill down  pivoting.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
Data Warehousing DSCI 4103 Dr. Mennecke Introduction and Chapter 1.
Data Warehousing: Defined and Its Applications Pete Johnson April 2002.
IST Databases and DBMSs Todd S. Bacastow January 2005.
1 Chapter 1 Introduction to Accounting Information Systems Chapter 4 Database Management Systems.
1 DATABASE TECHNOLOGIES BUS Abdou Illia, Fall 2007 (Week 3, Tuesday 9/4/2007)
5.1 © 2007 by Prentice Hall 5 Chapter Foundations of Business Intelligence: Databases and Information Management.
Data Warehousing Seminar Chapter 5. Data Warehouse Design Methodology Data Warehousing Lab. HyeYoung Cho.
1 © Prentice Hall, 2002 Physical Database Design Dr. Bijoy Bordoloi.
Relational Database Concepts. Let’s start with a simple example of a database application Assume that you want to keep track of your clients’ names, addresses,
Using Data Hygiene. Real World Issues Focus moves from strategic concepts in identifying individuals to operational concepts. Representative issues Multiple.
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Chapter 7: Database Systems Succeeding with Technology: Second Edition.
CHAPTER 8: MANAGING DATA RESOURCES. File Organization Terms Field: group of characters that represent something Record: group of related fields File:
MIS 301 Information Systems in Organizations Dave Salisbury ( )
1 Data Warehousing Lecture-13 Dimensional Modeling (DM) Virtual University of Pakistan Ahsan Abdullah Assoc. Prof. & Head Center for Agro-Informatics Research.
Chapter 6 1 © Prentice Hall, 2002 The Physical Design Stage of SDLC (figures 2.4, 2.5 revisited) Project Identification and Selection Project Initiation.
Lecturer: Gareth Jones. How does a relational database organise data? What are the principles of a database management system? What are the principal.
DIMENSIONAL MODELLING. Overview Clearly understand how the requirements definition determines data design Introduce dimensional modeling and contrast.
1 Data Warehouses BUAD/American University Data Warehouses.
Object Persistence (Data Base) Design Chapter 13.
Object Persistence Design Chapter 13. Key Definitions Object persistence involves the selection of a storage format and optimization for performance.
Slide 1 Object Persistence Design Chapter 13 Alan Dennis, Barbara Wixom, and David Tegarden John Wiley & Sons, Inc. Slides by Fred Niederman Edited by.
Announcements. Data Management Chapter 12 Traditional File Approach  Structure Field  Record  File  Fixed All records have common fields, and a field.
Module 2: Information Technology Infrastructure Chapter 5: Databases and Information Management.
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
Ch3 Data Warehouse Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2009.
Designing a Data Warehousing System. Overview Business Analysis Process Data Warehousing System Modeling a Data Warehouse Choosing the Grain Establishing.
Chapter 5 DATA WAREHOUSING Study Sections 5.2, 5.3, 5.5, Pages: & Snowflake schema.
Physical Database Design Purpose- translate the logical description of data into the technical specifications for storing and retrieving data Goal - create.
OLAP On Line Analytic Processing. OLTP On Line Transaction Processing –support for ‘real-time’ processing of orders, bookings, sales –typically access.
Introduction & History of Database Systems
Business Intelligence Training Siemens Engineering Pakistan Zeeshan Shah December 07, 2009.
Copyright© 2014, Sira Yongchareon Department of Computing, Faculty of Creative Industries and Business Lecturer : Dr. Sira Yongchareon ISCG 6425 Data Warehousing.
Copyright © Archer Decision Sciences, Inc. Our Model Store DimensionProduct Dimension District Region Total Brand Manufacturer Total StoresProducts.
MIS 451 Building Business Intelligence Systems Data Staging.
INFS 6220 Systems Analysis & Design Transactional DBs vs. Data Warehouses.
I am Xinyuan Niu I am here because I love to give presentations. Data Warehousing.
Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke1 Data Warehousing and Decision Support Chapter 25.
1 Management Information Systems M Agung Ali Fikri, SE. MM.
Building the Corporate Data Warehouse Pindaro Demertzoglou Data Resource Management.
IT 5433 LM4 Physical Design. Learning Objectives: Describe the physical database design process Explain how attributes transpose from the logical to physical.
Enterprise Processes and Systems MIS 2000 Instructor: Bob Travica Updated 2016 Class 16.
Enterprise Processes and Systems
Data warehouse and OLAP
ITD1312 Database Principles Chapter 5: Physical Database Design
Data Warehouse—Subject‐Oriented
Data Warehouse.
Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2009
The Physical Design Stage of SDLC (figures 2.4, 2.5 revisited)
Data Warehousing Concepts
MIS2502: Data Analytics Relational Data Modeling 3
Presentation transcript:

Business Intelligence/ Decision Models Week 2 IT Infrastructure & Marketing Database Design and Implementation

Outline Issues with Mkt Databases DBMS Database Design and Schemas Data Integrity and Hygiene Demo and Lab: Table redundancy and Queries

DB Marketing Problems Lack of a marketing strategy. Focus on promotions instead of relationships. Failure to have a picture of every customer. Failure to personalize your communications. Building a DB and sending s in house. Getting the economics wrong. Failure to use tests and controls. Lack of a forceful leader. Bad DB architecture Corrupted data

DB Environment

Traditional Environment: Silo Approach Source: Laudon and Laudon 2012

Data Warehouse Technology

Marketing Datamart

Data Warehouse Architecture

Metadata

Database Management Systems (DBMS)

Flat Files Sequential Fixed or variable length record ABC D NameAddress Transactions  A

DBMS with VSAM Index QC ON QC ON TN NE NB IPE QC ON MB SK AB BC

Hierarchical Indexed Direct Access DBMS Cust_id NamePurchasesProducts Top down

Indexed Direct Access DBMS Key Record Records 1145………. 2167………. 3267………. 4107………. 5234………. 6110……….

Reversed Hierarchical DBMS Cust_id NamePurchases Products Psyte Code Lifestyle Bottom up/Top down

Reversed Hierarchical DBMS NAME PSYTE PURCHASES Dubé18120 Smith34130 Bertrand18150 White56200 Harris34 50 Habib18300 Jones34430 PSYTE NAMES 18 Dubé; Bertrand; Habib 34 Smith; Harris; Jones 56 White

Relational Database CUSTOMERS ORDERS PRODUCTS Customer ID PKOrder ID PKProduct ID PK Cust First NameCustomer ID FKProduct Name Cust Last NameProduct ID FKProduct Description StreetOrder Date CityOrder Amount State Zip 1 

Relational DBMS Multiple Tables Source: Laudon and Laudon 2012

Relational DBMS with Query Source: Laudon and Laudon 2012

Relational Design

An Unnormalized Relation For Order (flat file) An unnormalized relation contains repeating groups. For example, there can be many parts and suppliers for each order. There is only a one-to-one correspondence between Order Number and Order Date. Source: Laudon and Laudon 2012

Normalized Tables Created From Order Pros: Data integrity and updating Cons: Processing speed for large data sets Source: Laudon and Laudon 2012

Charitable Contributions

Source: Kishore-jaladi-DW.ppt The “Classic” Star Schema  A single fact table, with detail and summary data  Fact table primary key has only one key column per dimension  Each key is generated  Each dimension is a single table, highly de-normalized Tradeoff between data integrity, updating and speed Some alternatives: Star and Snowflake structure Benefits: Easy to understand, easy to define hierarchies, reduces # of physical joins, low maintenance, very simple metadata

Data Integrity and Hygiene

Data Integrity Issues Duplicates (with variations) Individuals with similar names Customer reappearances Change of addresses Incomplete addresses Transcription errors Change of names

Illustrating Data Hygiene Quantities ResponseResponse Rate Customers2,000,000 29, % Undel. 15%1,700,00015%29, % Dup. 20%1,360,00020%29, % Cost CPO CPM = $5002,000,000$1,000,00029,000$ ,700,000$850,00029,000 $ ,360,000$680,00029,000 $23.45 Revenue Profit ROI Price = $602,000,000$870,00029,000-$130, % GM 50%1,700,000$870,00029,000$20,000 2% 1,360,000$870,00029,000$190,000 28% BE = FC / (P-C)1,000,000 / 30 $ 33,334 BE = FC / (P-C) 850,000 / 30 $ 28,334 BE = FC / (P-C) 680,000 / 30 $ 22,667

Data Hygiene Processes (1) Standardize names Title, First name, Initials, Family name, Suffix Standardize addresses Address 1, Address 2, City, Province, Postal Code Abbreviations (apt., ave, p.o., province) Replace prestige names with postal addresses (i.e. Commerce Court) Scrubbing Ex. c/o, co, c/o Delivery FSA/LDU, Postal walk Address change database

Data Hygiene Processes (2) Data Comparison Duplicate (cost, abuse) Householding Hyphenated Names, Maiden Names, Spouse’s Name Recomposed Families, Roommates Consolidation (merge/purge) Multiple Accounts (financial Services) Multiple policies (insurances) Multiple phone numbers (telco) Multiple divisions within firm

Wrap-up Issues with Mkt Databases DBMS Database Design and Schemas Data Integrity and Hygiene Demo and Lab: Table redundancy and Queries

Next Week Data Import Data Preparation Data Transformation