Components of A Successful Data Warehouse

Slides:



Advertisements
Similar presentations
Business Information Warehouse Business Information Warehouse.
Advertisements

Data Warehouse Architecture Sakthi Angappamudali Data Architect, The Oregon State University, Corvallis 16 th May, 2005.
Chapter 13 The Data Warehouse
Data Warehousing: Defined and Its Applications Pete Johnson April 2002.
1 Components of A Successful Data Warehouse Chris Wheaton, Co-Founder, Client Advocate.
Data Conversion to a Data warehouse Presented By Sanjay Gunasekaran.
Week 6 Lecture The Data Warehouse Samuel Conn, Asst. Professor
©Silberschatz, Korth and Sudarshan18.1Database System Concepts - 5 th Edition, Aug 26, 2005 Buzzword List OLTP – OnLine Transaction Processing (normalized,
1 Brett Hanes 30 March 2007 Data Warehousing & Business Intelligence 30 March 2007 Brett Hanes.
Database Systems – Data Warehousing
Data Warehouse Overview September 28, 2012 presented by Terry Bilskie.
1 Data Warehouses BUAD/American University Data Warehouses.
Data Warehouse Development Methodology
2 Copyright © Oracle Corporation, All rights reserved. Defining Data Warehouse Concepts and Terminology.
Data Warehousing.
State of Wisconsin Department of Revenue Data Warehouse Presentation August 16, 2000.
Decision Support and Date Warehouse Jingyi Lu. Outline Decision Support System OLAP vs. OLTP What is Date Warehouse? Dimensional Modeling Extract, Transform,
Database Design – Lecture 18 Client/Server, Data Warehouse and E-Commerce Database Design.
Best Practices for Implementing
June 08, 2011 How to design a DATA WAREHOUSE Linh Nguyen (Elly)
Acct 6910 Building Business Intelligence Systems An Introduction to Data Warehouse.
1 Copyright © Oracle Corporation, All rights reserved. Business Intelligence and Data Warehousing.
The Need for Data Analysis 2 Managers track daily transactions to evaluate how the business is performing Strategies should be developed to meet organizational.
2 Copyright © 2006, Oracle. All rights reserved. Defining Data Warehouse Concepts and Terminology.
1 Data Warehousing Data Warehousing. 2 Objectives Definition of terms Definition of terms Reasons for information gap between information needs and availability.
Business Intelligence Overview
Project Execution Methodology
Jan 2016 Solar Lunar Data.
Advanced Applied IT for Business 2
Defining Data Warehouse Concepts and Terminology
THE COMPELLING NEED FOR DATA WAREHOUSING
Data warehouse and OLAP
Introduction.
Chapter 13 The Data Warehouse
Data Warehouse.
Q1 Jan Feb Mar ENTER TEXT HERE Notes
Defining Data Warehouse Concepts and Terminology
How to Successfully Implement an Agile Project
Average Monthly Temperature and Rainfall



Data Warehouse Overview September 28, 2012 presented by Terry Bilskie
An Introduction to Data Warehousing

Gantt Chart Enter Year Here Activities Jan Feb Mar Apr May Jun Jul Aug
Q1 Q2 Q3 Q4 PRODUCT ROADMAP TITLE Roadmap Tagline MILESTONE MILESTONE

Step 3 Step 2 Step 1 Put your text here Put your text here
Introduction of Week 9 Return assignment 5-2


Data Warehousing Concepts

Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Q1 Q2 Q3 Q4 PRODUCT ROADMAP TITLE Roadmap Tagline MILESTONE MILESTONE

Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Text for section 1 1 Text for section 2 2 Text for section 3 3
Analytics, BI & Data Integration
Executive Project Kickoff
Q1 Q2 Q3 Q4 PRODUCT ROADMAP TITLE Roadmap Tagline MILESTONE MILESTONE
Data Warehouse and OLAP Technology
Presentation transcript:

Components of A Successful Data Warehouse Chris Wheaton, Co-Founder, Client Advocate

Presentation Information Presentation: Successful Components of a Data Warehouse The purpose of this presentation is to provide attendees with the understanding of how to build a successful data warehouse/business intelligence solution.

Presentation Information Author: Chris Wheaton Biography: Chris Wheaton is a Co-Founder of BASE Consulting Group, Inc. He initiated and has contributed to the development of the Business Intelligence and Data Warehousing Certificate Program at the University of California, Berkeley Extension and is a lecturer in the program. He has presented on Data Warehousing topics at conferences throughout the United States including the Business Objects and Oracle Applications User Conferences. Contact Information: E-mail: cwheaton@baseconsulting.com Phone: (510) 628-3300 Ext. 223

Agenda Data Warehouse ? What is it? Why do it? Why do they fail? How do you control business risk? How do you control technical risk?

Many names for the same thing Data Warehouse? What is it? Many names for the same thing Decision Support System (DSS) Executive Information System Management Information System Business Intelligence Solution Analytic Application Data Warehouse Six terms for the same thing: a system for helping companies get the information they want, when they want it…etc.

Data Warehouse Objectives Data Warehouse? What is it? Data Warehouse Objectives Business Access to specific high-value information on a timely basis. Analysis Makes the restructured data available to users via user-friendlier query and reporting tools. Reporting Technical Gets the data off of the transaction system for analysis. Performance Restructures and integrates the data so that it is easier to use for reporting and analysis. Integration

Data Warehouse Risks Why do they fail? Business User Acceptance Content Does the solution answer the right questions? Does the solution have enough data? User Acceptance Is it too complex for the average user? Is the data timely enough? Technical Performance Is the performance of the user queries satisfactory? Can data be loaded to the data warehouse within the allotted timeframe? Integration How do we combine information from multiple systems? The LAP brothers refer to categories of data warehousing products. And don’t forget HOLAP, Hybrid Online Analytical Processing, which refers to systems that use both relational and multi-dimensional technology together. No one category has shown itself to be best for all situations. This course discusses practices and techniques that are applicable to all.

Controlling Business Risk How do you control the risks? Controlling Business Risk We have found that the best way to address the business risks associated with a data warehouse project is to employ a methodology with the following components: Enterprise Strategy Phased Delivery Iterative Prototyping

How do you control the risks?

How do you control the risks? Enterprise Strategy Asses technical landscape Identify business drivers Define analytical processes to be supported Identify major facts, dimensions and attributes Map and gap to data sources Assess current architecture and tools Recommend subject area phasing and tool selection

____________________________ How do you control the risks? Phased Subject Areas Phase 1 Prototype 1 Phase 2 Prototype 1 Transition Phase 1 Prototype 2 Phase 2 Prototype 2 Conceptual Architecture Phase 1 Prototype 3 Phase 2 Prototype 3 ____________________________ 1 2 3 4 5 7 8 9 11 Phase 1 Deployed to Production 6 Phase 2 Deployed to Production 10 SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC Phase 1 Requirements Phase 2 Requirements Deliverable # Milestone

How do you control the risks? Subject Area Scope Examples are: Bookings, Billings, Backlog Customer Support Calls Inventory Marketing G/L Transactions Subject Area Focus A related set of business entities as defined by specific user group. Integration between subject areas.

Iterative Prototyping How do you control the risks? Iterative Prototyping

Controlling Technical Risk We have found that the best way to address the technical risks associated with a data warehouse project is to employ an architecture with the following components: Integrated Staging Area Dimensional Data Store

Architectural Overview Data Warehouse – What do you deliver? Architectural Overview

Integrated Staging Area Data Warehouse – What do you deliver? Integrated Staging Area Database tables holding production data before it is loaded into the dimensional data store tables. Tables usually resemble the source data tables, and have not been re-structured except to allow for some integration. Critical to source system reconciliation. Staging area may also include flat files in original format. Some data warehouse architectures load the source system data into an ODS before it is restructured for the data warehouse. The reasons for this are as follows: The source system may have a tight window for extracting data. By extracting data in its native form (or by using a database replication facility), and ODS reduces the burden on the transaction systems. Other systems may want to query or even update the data before it is put in the data warehouse. This is why an ODS is NOT a data warehouse, but can be a transactional database in itself. The ODS may be a less expensive environment to store hot backup data in case the Data Warehouse needs to be reloaded.

Dimensional Data Store Data Warehouse – What do you deliver? Dimensional Data Store Dimension Tables Sales Time Geo Product Fact Table Sales by Geo & Day Sales by Product & Day Aggregates

Advantages of a Dimensional Model Data Warehouse – What do you deliver? Advantages of a Dimensional Model Standardization of dimensions helps standardize reporting across areas of the business. Dimension tables preserve the history of the dimensional information. Whole new dimensions can be introduced without major disruptions to the fact table.

Extract, Transform and Load Data Warehouse – What do you deliver? Extract, Transform and Load