Data Warehouse Architecture. Inmon’s Corporate Information Factory The enterprise data warehouse is not intended to be queried directly by analytic applications,

Slides:



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

CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
1 Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal or quotation. An Introduction to Data.
BY LECTURER/ AISHA DAWOOD DW Lab # 2. LAB EXERCISE #1 Oracle Data Warehousing Goal: Develop an application to implement defining subject area, design.
Accessing Organizational Information—Data Warehouse
Data Warehouse Architecture Sakthi Angappamudali Data Architect, The Oregon State University, Corvallis 16 th May, 2005.
Introduction to data warehouses
Dimensional Modeling Business Intelligence Solutions.
Data Warehouse IMS5024 – presented by Eder Tsang.
Ch1: File Systems and Databases Hachim Haddouti
IST722 Data Warehousing An Introduction to Data Warehousing Michael A. Fudge, Jr.
Data Warehouse Toolkit Introduction. Data Warehouse Bill Inmon's paradigm: Data warehouse is one part of the overall business intelligence system. An.
Components of the Data Warehouse Michael A. Fudge, Jr.
Business Intelligence
Data Warehouse & Data Mining
OLAP Theory-English version On-Line Analytical processing (Buisness Intelligence) [Ing.Skorkovský,CSc] KPH_ESF_MU.
1 Brett Hanes 30 March 2007 Data Warehousing & Business Intelligence 30 March 2007 Brett Hanes.
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.
Activity Running Time DurationIntro0 2 min Setup scenario 2 2 min SQL BI components & concepts 4 5 min Data input (Let’s go shopping) 9 7 min Whiteboard.
The Business Intelligence Side of Blue Mountain RAM Bill Lucas, IT Systems Architect and Senior Software Engineer.
DW-1: Introduction to Data Warehousing. Overview What is Database What Is Data Warehousing Data Marts and Data Warehouses The Data Warehousing Process.
Decision Support System Definition A Decision Support System is an interactive computer-based system or subsystem that helps people use computer communications,
OLAP Theory-English version On-Line Analytical processing (Business Intelligence) [Ing.J.Skorkovský,CSc.] Department of corporate economy.
Datawarehouse Objectives
Data warehousing and online analytical processing- Ref Chap 4) By Asst Prof. Muhammad Amir Alam.
BUS1MIS Management Information Systems Semester 1, 2012 Week 6 Lecture 1.
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.
2 Copyright © Oracle Corporation, All rights reserved. Defining Data Warehouse Concepts and Terminology.
The Data Warehouse “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of “all” an organisation’s data in support.
1 Reviewing Data Warehouse Basics. Lessons 1.Reviewing Data Warehouse Basics 2.Defining the Business and Logical Models 3.Creating the Dimensional Model.
CISB594 – Business Intelligence
Datawarehouse A sneak preview. 2 Data Warehouse Approach An old idea with a new interest: Cheap Computing Power Special Purpose Hardware New Data Structures.
1 Categories of data Operational and very short-term decision making data Current, short-term decision making, related to financial transactions, detailed.
Dimensional Modeling Primer Chapter 1 Kimball & Ross.
UNIT-II Principles of dimensional modeling
Chapter 5 DATA WAREHOUSING Study Sections 5.2, 5.3, 5.5, Pages: & Snowflake schema.
The Data Warehouse “A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of “all” an organisation’s data in support.
Business Intelligence Transparencies 1. ©Pearson Education 2009 Objectives What business intelligence (BI) represents. The technologies associated with.
The Data Warehouse Chapter Operational Databases = transactional database  designed to process individual transaction quickly and efficiently.
1 Categories of data Operational and very short-term decision making data Current, short-term decision making, related to financial transactions, detailed.
Data Resource Management Agenda What types of data are stored by organizations? How are different types of data stored? What are the potential problems.
The Need for Data Analysis 2 Managers track daily transactions to evaluate how the business is performing Strategies should be developed to meet organizational.
Introduction Data Vault. Historical development Business Intelligence 1950 Turing : First computers 1960Codd : 3NF 1970Management Information Systems.
Business Intelligence and Decision Support Systems (9 th Ed., Prentice Hall) Chapter 5: Data Warehousing.
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.
Business Intelligence and Decision Support Systems (9 th Ed., Prentice Hall) Chapter 8: Data Warehousing.
Data Warehouse/Data Mart It’s all about the data.
OLAP Theory-English version On-Line Analytical processing (Buisness Intelligence) Ing.Skorkovský,CSc Department of Corporate Economy Faculty of Economics.
Bartek Doruch, Managing Partner, Kamil Karbowiak, Managing Partner, Using Power BI in a Corporate.
CHAPTER SIX DATA Business Intelligence
Advanced Applied IT for Business 2
Chapter 13 Business Intelligence and Data Warehouses
Data warehouse and OLAP
Data Warehouse—Subject‐Oriented
Data Warehouse.
Designing Business Intelligence Solutions with Microsoft SQL Server
Overview and Fundamentals
Competing on Analytics II
Data Warehouse and OLAP
An Introduction to Data Warehousing
Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2009
Warehouse Architecture
MIS2502: Data Analytics Dimensional Data Modeling
Data Warehouse.
Data Warehousing Concepts
Technical Architecture
Data Warehouse and OLAP
Data Warehouse and OLAP Technology
Presentation transcript:

Data Warehouse Architecture

Inmon’s Corporate Information Factory The enterprise data warehouse is not intended to be queried directly by analytic applications, business intelligence tools, or the like. Its purpose is to feed additional data stores dedicated to a variety of analytic systems. The enterprise data warehouse is usually stored in a relational database management system, and Inmon advocates the use of third normal form database design. Data Marts These are databases that support a departmental view of information. With a subject area focus, each data mart takes information from the enterprise data warehouse and readies it for analysis. Inmon advocates the use of dimensional design for these data marts. The data marts may aggregate data from the atomic representation in the enterprise data warehouse.

A simplified view of W.H. Inmon’s architecture: the Corporate Information Factory

Ralph Kimball’s data warehouse architecture

Ralph Kimball’s data warehouse architecture: the dimensional data warehouse The dimensional data warehouse in the center of Figure is the end result of the ETL process. It is an integrated repository for atomic data. It contains a single view of business activities, as drawn from throughout the enterprise. It stores that information in a highly granular, or atomic, format. The dimensional data warehouse differs from the enterprise data warehouse in two important ways. First, it is designed according to the principles of dimensional modeling. It consists of a series of star schemas or cubes, which capture information at the lowest level of detail possible. This contrasts with the Inmon approach, where the enterprise data warehouse is designed using the principles of ER modeling.

Second, the dimensional data warehouse may be accessed directly by analytic systems. Concept of a data mart becomes a logical distinction; the data mart is a subject area within the datawarehouse. In Figure, this is represented by the box that highlights a subset of the tables in the dimensional data warehouse.

Stand Alone Data Mart The stand-alone data mart is an analytic data store that has not been designed in an enterprise context. It is focused exclusively on a subject area. One or more operational systems feed a database called a data mart. The data mart may employ dimensional design, an entity- relationship model, or some other form of design. Analytic tools or applications query it directly, bringing information to end users.

Development of a stand-alone data mart is often the most expedient path to visible results. it does not require cross-functional analysis, the data mart can be put into production quickly. No time must be spent constructing a consolidated view of product or customer, for example. No time must be spent comparing data from the sales system withwhat is tracked in the accounting system. Instead, the implementation takes a direct route from subject area requirements to implementation. Because results are rapid and less expensive, stand-alone data marts find their way into many organizations.

They are not always built from scratch. A stand-alone data mart may become part of the application portfolio when purchased as a packaged application, which provides a prebuilt solution in a subject area. Packaged data marts may also be available as add-ons to packaged operational applications. Prebuilt solutions like these can further increase the savings in time and cost.

Multiple Standalone Data Marts