Data Warehousing Data Warehousing: A Definition “A data warehouse is a single integrated store of data which provides the infrastructural basis for informational.

Slides:



Advertisements
Similar presentations
Introduction to Databases
Advertisements

Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Lecture 5 Themes in this session Building and managing the data warehouse Data extraction and transformation Technical issues.
Managing Data Resources
© Prentice Hall CHAPTER 14 Managing Technological Resources.
Multidimensional Database Structure
Information Integration. Modes of Information Integration Applications involved more than one database source Three different modes –Federated Databases.
File Systems and Databases
Fundamentals of Information Systems, Second Edition 1 Organizing Data and Information Chapter 3.
Components and Architecture CS 543 – Data Warehousing.
File Systems and Databases Hachim Haddouti
Introduction to Database Management
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Organizing Data and Information Chapter 5.
Principles of Information Systems, Sixth Edition Organizing Data and Information Chapter 5.
Lecture-8/ T. Nouf Almujally
CASE STUDY: Implementing and Administering SAS® Enterprise Guide® Across the Enterprise As a Solution for Data Access Security Ulf Borjesson Evangeline.
By N.Gopinath AP/CSE. Why a Data Warehouse Application – Business Perspectives  There are several reasons why organizations consider Data Warehousing.
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
Week 1 Lecture MSCD 600 Database Architecture Samuel ConnSamuel Conn, Asst. Professor Suggestions for using the Lecture Slides.
Understanding Data Warehousing
Database Design - Lecture 1
 Introduction Introduction  Purpose of Database SystemsPurpose of Database Systems  Levels of Abstraction Levels of Abstraction  Instances and Schemas.
DBS201: DBA/DBMS Lecture 13.
Data Administration & Database Administration
Data Warehousing Seminar Chapter 5. Data Warehouse Design Methodology Data Warehousing Lab. HyeYoung Cho.
Chapter 1 Introduction to Databases Pearson Education ©
Data Warehouse Concepts Transparencies
Data Warehouse Management March 13, 2000 Prof. Hwan-Seung Yong Dept. of CSE, Ewha Womans Univ. The Case for Data Warehousing.
Database System Concepts and Architecture
Organizing Data and Information AD660 – Databases, Security, and Web Technologies Marcus Goncalves Spring 2013.
1 Chapter 1 Database Systems Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
Chapter 1 : Introduction §Purpose of Database Systems §View of Data §Data Models §Data Definition Language §Data Manipulation Language §Transaction Management.
BUS1MIS Management Information Systems Semester 1, 2012 Week 6 Lecture 1.
Fundamentals of Information Systems, Seventh Edition 1 Chapter 3 Data Centers, and Business Intelligence.
©Silberschatz, Korth and Sudarshan1.1Database System Concepts Chapter 1: Introduction Purpose of Database Systems View of Data Data Models Data Definition.
Announcements. Data Management Chapter 12 Traditional File Approach  Structure Field  Record  File  Fixed All records have common fields, and a field.
5-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Principles of Information Systems, Sixth Edition Organizing Data and Information Chapter 5.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 4 Data and Databases. Learning Objectives Upon successful completion of this chapter, you will be able to: Describe the differences between data,
Data Warehouse. Group 5 Kacie Johnson Summer Bird Washington Farver Jonathan Wright Mike Muchane.
Data resource management
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS Instructor Ms. Arwa Binsaleh.
Chapter 5 DATA WAREHOUSING Study Sections 5.2, 5.3, 5.5, Pages: & Snowflake schema.
Management Information Systems, 4 th Edition 1 Chapter 8 Data and Knowledge Management.
Managing Data Resources. File Organization Terms and Concepts Bit: Smallest unit of data; binary digit (0,1) Byte: Group of bits that represents a single.
CISB594 – Business Intelligence Data Warehousing Part II.
Database Systems. Role and Advantages of the DBMS Improved data sharing Improved data security Better data integration Minimized data inconsistency Improved.
Database Management Systems (DBMS)
DATA RESOURCE MANAGEMENT
Two-Tier DW Architecture. Three-Tier DW Architecture.
Principles of Information Systems, Sixth Edition Organizing Data and Information Chapter 5.
Principles of Information Systems, Sixth Edition Organizing Data and Information Chapter 5.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 1 Database Systems.
Business intelligence systems. Data warehousing. An orderly and accessible repositery of known facts and related data used as a basis for making better.
Chapter 8: Data Warehousing. Data Warehouse Defined A physical repository where relational data are specially organized to provide enterprise- wide, cleansed.
Data Warehouse Data Mart Elahe Soroush. Agenda  Data Warehouse definition  Concepts  Logical transformation  Physical transformation  DW components.
Foundations of information systems : BIS 1202 Lecture 4: Database Systems and Business Intelligence.
Business Intelligence and Decision Support Systems (9 th Ed., Prentice Hall) Chapter 8: Data Warehousing.
THE LEONS COLLEGE OF LAW1 Organizing Data and Information Chapter 4.
Building a Data Warehouse
Introduction to DBMS Purpose of Database Systems View of Data
Manajemen Data (2) PTI Pertemuan 6.
Chapter 1 Database Systems
File Systems and Databases
Chapter 5 Data Resource Management.
An Introduction to Data Warehousing
Data Model.
Introduction to DBMS Purpose of Database Systems View of Data
Presentation transcript:

Data Warehousing Data Warehousing: A Definition “A data warehouse is a single integrated store of data which provides the infrastructural basis for informational applications in the enterprise” Kelly, “Data Warehousing”, p55 Will be a collection of tools - not just a database –query system to support decision making –Ability to trawl (mine) in a way that suits the user –integrated store of consistent, up to date data Main aim to maximise the effective use of data within a business. Create a bridge between disparate systems

Data Warehousing Old Rationale for IS Automate the business process reduce costs Information seen as a fortuitous by-product Emphasis on IS as a input/processing/output –define functions –specify what system does –difficult to change outputs

Data Warehousing Problems With a Data Processing Approach Data problems –resident in different systems –inconsistent –different attributes –different time bands/frames –irreconcilable –Deletion vs. archiving of data –inappropriate and inconsistent data models

Data Warehousing Issues in Moving to Data Warehousing Philosophy Ownership issues Planning across department/functional areas Economic issues Standardisation of data model –similar data entities in multiple systems –data inextricably bound with application Standards in application design –piecemeal approaches to system implementation Multiple interpretations of reality

Data Warehousing The Business Case for Data Warehousing Reduce costs (?) Increase business e.g. through better understanding of customers Develop competitive advantage Change the nature of the business

Data Warehousing Advantages of Data Warehousing Removes query and reporting load from TPS Allows more appropriate technology for queries and reports Provides a more simple query interface to users May provide a higher integrity DB than a TPS Easy way of reporting across multiple systems May provide a DB with a longer memory than a TPS! May make TPS more secure by reducing access

Data Warehousing Disadvantages of Data Warehousing May rely too heavily on data generated only from TPS May complicate business processes by “institutionalising” reports, data for data’s sake Learning curve too long - technical and business aspects Culture of developing quick and dirty strategic applications End-users may not have skills for building queries Availability of data warehousing skills Data warehouses require high maintenance Cost of information may outweigh its benefit

Data Warehousing Problems to Consider Extracting, cleaning and loading of data may be time consuming Undetected error in systems feeding the warehouse Warehouse project may highlight unrecorded data in existing systems End user training in query and reporting tools may increase requests for IS written reports End user approaches to calculations may differ due to different business views Creation of a large-scale data warehouse may homogenise data - reducing content Conflict between “need to know” and “right to know” mindsets

Data Warehousing Data Warehousing Tools Meta-data modelling Data transformation –Extract –Cleanse –Load Database (relational, parallel) Query language

Data Warehousing Relationship Between Data Warehouse and Other Systems Data Warehouse TPS 1 TPS 2 TPS 3 User Application Information Retrieval Application Importing Process Periodic transformation And integration process

Data Warehousing Some Political Issues (IS) Who should a data warehousing development group report to? Who should administrate over the warehouse? (DBS or development group) How should the support of feeder system developers be gained? What about errors in the feeder system? Who has responsibility for data quality monitoring? What about changes to the feeder systems?

Data Warehousing Some Political Issues (User-IS) Why should users give up control of user managed databases? How is the co-operation gained of a user who’s spreadsheet is being automated? Should design be for the needs of the masses or the most demanding users? How many data marts should there be?

Data Warehousing Some Political Issues (User-User) Who has access to what data? Do all users define and interpret data the same way? Who has the final say about the “correctness” of data

Data Warehousing General Political Issues Imposes new obligations whose responsibilities are unclear. May require a change in processes that an organisation may not be comfortable with. Requires agreement on some and not all definitions of data

Data Warehousing Some Useful References... Kelly, (1998) “Data Warehousing”, Wiley