XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Level 3 Objectives: Identifying and Eliminating Database.

Slides:



Advertisements
Similar presentations
© Pearson Education Limited, Chapter 8 Normalization Transparencies.
Advertisements

Preparing to Automate Data Management
Relational Terminology. Normalization A method where data items are grouped together to better accommodate business changes Provides a method for representing.
Normalization of Database Tables
Client/Server Databases and the Oracle 10g Relational Database
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
Boyce-Codd Normal Form Kelvin Nishikawa SE157a-03 Fall 2006 Kelvin Nishikawa SE157a-03 Fall 2006.
1 5 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 5 Database Design: Normalization.
4 Chapter 4 Normalization Hachim Haddouti. 4 Hachim Haddouti, CH4, see also Rob & Coronel 2 In this chapter, you will learn: What normalization is and.
Chapter 5 Normalization of Database Tables
Database Systems Design, Implementation, and Management Coronel | Morris 11e ©2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 5 Normalization of Database Tables.
Keys Chapter 8 Database Design for Mere Mortals. Why Keys Are Important They ensure that each record in a table can be properly identified. They help.
1 5 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 5 Database Design 1: Normalization.
Introduction to Schema Refinement. Different problems may arise when converting a relation into standard form They are Data redundancy Update Anomalies.
Chapter 3 The Relational Model and Normalization
Chapter 5 Normalization of Database Tables
© Abdou Illia MIS Spring 2015
Lecture 12 Inst: Haya Sammaneh
Preparing to Automate Data Management
A Guide to SQL, Eighth Edition Chapter Two Database Design Fundamentals.
Chapter 1 Overview of Database Concepts Oracle 10g: SQL
1 Chapter 1 Overview of Database Concepts. 2 Chapter Objectives Identify the purpose of a database management system (DBMS) Distinguish a field from a.
Concepts and Terminology Introduction to Database.
Lecture 2 An Overview of Relational Database IST 318 – DB Admin.
CBAD2103 Data Analysis and Modeling. Chapter 7 Conceptual Design Methodology.
Avoiding Database Anomalies
Normalization. 2 Objectives u Purpose of normalization. u Problems associated with redundant data. u Identification of various types of update anomalies.
NormalizationNormalization Chapter 4. Purpose of Normalization Normalization  A technique for producing a set of relations with desirable properties,
Database Systems: Design, Implementation, and Management Tenth Edition
Concepts of Database Management Sixth Edition Chapter 5 Database Design 1: Normalization.
Concepts of Database Management, Fifth Edition
A Normalisation Example Mark Kelly McKinnon Secondary College Vceit.com Based on work by Robert Timmer-Arends.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 6 Normalization of Database Tables.
1 A Guide to MySQL 2 Database Design Fundamentals.
1 DATABASE SYSTEMS DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT Chapter 7 Normalisation.
BIS Database Systems School of Management, Business Information Systems, Assumption University A.Thanop Somprasong Chapter # 5 Normalization of Database.
資料庫正規化 Database Normalization 取材自 AIS, 6 th edition By Gelinas et al.
Chapter 7 1 Database Principles Data Normalization Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that.
INSERT BOOK COVER 1Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall. Exploring Microsoft Office Access 2010 by Robert Grauer, Keith.
Chapter 1Introduction to Oracle9i: SQL1 Chapter 1 Overview of Database Concepts.
XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Preparing To Automate Data Management Chapter 1 “You.
XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Preparing To Automate Data Management Chapter 1 “You.
DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.
Database Design – Lecture 8
Normalization Transparencies 1. ©Pearson Education 2009 Objectives How the technique of normalization is used in database design. How tables that contain.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 16 Using Relational Databases.
© Pearson Education Limited, Normalization Bayu Adhi Tama, M.T.I. Faculty of Computer Science University of Sriwijaya.
Normalization Example. Database Systems, 8 th Edition 2 Database Tables and Normalization Normalization –Process for evaluating and correcting table structures.
Concepts of Database Management Seventh Edition Chapter 5 Database Design 1: Normalization.
BSA206 Database Management Systems Lecture 2: Introduction to Oracle / Overview of Database Concepts.
Logical Database Design and the Relational Model.
NORMALIZATION: ‘1NF’ The general rule: ‘’Any field which can have many, must have its own table’’ By Sam Beaumont.
Normalisation 1NF to 3NF Ashima Wadhwa. In This Lecture Normalisation to 3NF Data redundancy Functional dependencies Normal forms First, Second, and Third.
Microsoft Access 2010 Chapter 11 Database Design.
Lecture 4: Logical Database Design and the Relational Model 1.
Normalization. Overview Earliest  formalized database design technique and at one time was the starting point for logical database design. Today  is.
NormalisationNormalisation Normalization is the technique of organizing data elements into records. Normalization is the technique of organizing data elements.
Southern Methodist University CSE CSE 2337 Introduction to Data Management Chapter 5 Part II.
Database Architecture Normalization. Purpose of Normalization A technique for producing a set of relations with desirable properties, given the data requirements.
NORMALIZATION Handout - 4 DBMS. What is Normalization? The process of grouping data elements into tables in a way that simplifies retrieval, reduces data.
SLIDE 1IS 257 – Fall 2006 Normalization Normalization theory is based on the observation that relations with certain properties are more effective.
What Is Normalization  In relational database design, the process of organizing data to minimize redundancy  Usually involves dividing a database into.
XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Level 2 Objectives: Understanding and Creating Table.
Normalizing Database Designs. 2 Objectives In this chapter, students will learn: –What normalization is and what role it plays in the database design.
Client/Server Databases and the Oracle 10g Relational Database
A brief summary of database normalization
Functional Dependencies
Chapter 9 Designing Databases
Chapter 6 Normalization of Database Tables
Presentation transcript:

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Level 3 Objectives: Identifying and Eliminating Database Anomalies by Normalizing Data Learn the techniques for normalizing data Evaluate fields that are used as keys Test the database design

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 2 Normalizing the Tables in the Database Normalization  Design process  Goals Reduces space required to store data by eliminating duplicate data in database Reduces inconsistent data in database by storing data only once Reduces chance of deletion update and insertion anomalies

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 3 Normalizing the Tables in the Database (continued) Deletion anomaly  User deletes data from database  Unintentionally deletes only occurrence of data in database Update anomaly  Due to redundant data in database  User fails to update some records or updates records erroneously Insertion anomaly  User cannot add data to database unless preceded by entry of other data

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 4 Normalizing the Tables in the Database (continued) Functional dependency  Column in table considered functionally dependent on another column If each value in second column associated with exactly one value in first column Partial dependency  Field dependent on only part of primary key Composite primary key  Primary key uses two or more fields to create unique records in table

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 5 Normalizing the Tables in the Database (continued) Determinant  Field or collection of fields whose value determines value in another field  Inverse of dependency Natural key  Primary key that details obvious and innate trait of record Artificial key  Field whose sole purpose is to create primary key  Usually visible to users

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 6 Normalizing the Tables in the Database (continued) Surrogate key  Computer-generated primary key  Usually invisible to users

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 7 First Normal Form Repeating group  Field contains more than one value First normal form  1NF  Does not contain any repeating groups

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 8 Second Normal Form 2NF Table must be in 1NF Must not contain any partial dependencies on composite primary key Tables in 1NF and contain primary key with only one field  Automatically in 2NF

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 9 Third Normal Form 3NF Only determinants must be candidate keys Candidate key  Field or collection of fields that could function as primary key but was not chosen to do so Transitive dependency  Occurs between two nonkey fields both dependent on third field Tables in 3NF should not have transitive dependencies

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 10 Level 3 Summary Normal forms  First (1NF)  Second (2NF)  Third (3NF)

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 11 Chapter Summary Discovery:  Identify existing and missing data  Organize data into tables  Determine data types for each field Table relationships  Established through common fields  Types 1:M 1:1 M:N

XP Chapter 1 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 12 Chapter Summary (continued) Normalization  Reduces duplication and inconsistency  Forms: 1NF 2NF 3NF