 Definition  Components  Advantages  Limitations Contents  Definition Definition  Normal Forms Normal Forms  First Normal Form First Normal Form.

Slides:



Advertisements
Similar presentations
Normal forms - 1NF, 2NF and 3NF
Advertisements

5 5 Normalization of Database Tables Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
DATA MODELS A collection of conceptual tools for describing data, data relationships, data semantics, and consistency constraints. Provide a way to describe.
Normalisation to 3NF Database Systems Lecture 11 Natasha Alechina.
Boyce-Codd NF Takahiko Saito Spring 2005 CS 157A.
NORMALIZATION FIRST NORMAL FORM (1NF): A relation R is in 1NF if all attributes have atomic value = one value for an attribute = no repeating groups =
Chapter 8 Normal Forms Based on Functional Dependencies Deborah Costa Oct 18, 2007.
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
CS263:Revision on Normalisation
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.
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 5 Normalization of Database Tables
Normalization. Introduction Badly structured tables, that contains redundant data, may suffer from Update anomalies : Insertions Deletions Modification.
Chapter 4: Logical Database Design and the Relational Model (Part II)
Week 6 Lecture Normalization
Lecture 12 Inst: Haya Sammaneh
 Definition  Components  Advantages  Limitations Contents  DBMS DBMS  Functions Functions  Architecture Architecture.
Functional Dependence An attribute A is functionally dependent on attribute(s) B if: given a value b for B there is one and only one corresponding value.
Logical Database Design ( 補 ) Unit 7 Logical Database Design ( 補 )
Avoiding Database 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
RDBMS Concepts/ Session 3 / 1 of 22 Objectives  In this lesson, you will learn to:  Describe data redundancy  Describe the first, second, and third.
Concepts of Database Management, Fifth Edition
1 A Guide to MySQL 2 Database Design Fundamentals.
Your name here. Improving Schemas and Normalization What are redundancies and anomalies? What are functional dependencies and how are they related to.
資料庫正規化 Database Normalization 取材自 AIS, 6 th edition By Gelinas et al.
Logical Database Design Relational Model. Logical Database Design Logical database design: process of transforming conceptual data model into a logical.
SALINI SUDESH. Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that avoid unnecessary duplication of.
M Taimoor Khan Course Objectives 1) Basic Concepts 2) Tools 3) Database architecture and design 4) Flow of data (DFDs)
Chapter 7 1 Database Principles Data Normalization Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that.
1 CMPT 275 Phase: Design. Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces Data Persistance.
CORE 2: Information systems and Databases NORMALISING DATABASES.
Normalization Well structured relations and anomalies Normalization First normal form (1NF) Functional dependence Partial functional dependency Second.
11/07/2003Akbar Mokhtarani (LBNL)1 Normalization of Relational Tables Akbar Mokhtarani LBNL (HENPC group) November 7, 2003.
Lecture No 14 Functional Dependencies & Normalization ( III ) Mar 04 th 2011 Database Systems.
©NIIT Normalizing and Denormalizing Data Lesson 2B / Slide 1 of 18 Objectives In this section, you will learn to: Describe the Top-down and Bottom-up approach.
In this session, you will learn to: Describe data redundancy Describe the first, second, and third normal forms Describe the Boyce-Codd Normal Form Appreciate.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 5 (Part c): Logical Database Design and the Relational Model Modern Database Management.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Normalization Hour1,2 Presented & Modified by Mahmoud Rafeek Alfarra.
Normalisation 1NF to 3NF Ashima Wadhwa. In This Lecture Normalisation to 3NF Data redundancy Functional dependencies Normal forms First, Second, and Third.
Dr. T. Y. Lin | SJSU | CS 157A | Fall 2015 Chapter 3 Database Normalization 1.
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.
Objectives of Normalization  To create a formal framework for analyzing relation schemas based on their keys and on the functional dependencies among.
Advanced Database System
NORMALIZATION Handout - 4 DBMS. What is Normalization? The process of grouping data elements into tables in a way that simplifies retrieval, reduces data.
Logical Database Design and Relational Data Model Muhammad Nasir
Chapter 4 © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 4: Logical Database Design and the Relational Model Modern Database Management.
Microsoft Access CS 110 Fall Entity Relationship Model Entities Entities Principal data object about which information is to be collectedPrincipal.
SLIDE 1IS 257 – Fall 2006 Normalization Normalization theory is based on the observation that relations with certain properties are more effective.
Lecture # 17 Chapter # 10 Normalization Database Systems.
Database Normalization. What is Normalization Normalization allows us to organize data so that it: Normalization allows us to organize data so that it:
1 CS490 Database Management Systems. 2 CS490 Database Normalization.
A Guide to SQL, Eighth Edition
Normalization Karolina muszyńska
A brief summary of database normalization
Chapter 5: Logical Database Design and the Relational Model
Functional Dependencies
Example Question–Is this relation Well Structured? Student
Unit 4: Normalization of Relations
Normalization of Database Tables Uploaded by: mysoftbooks.ml
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
Unit 7 Normalization (表格正規化).
Normalisation to 3NF.
DATABASE DESIGN & DEVELOPMENT
Review of Week 3 Relation Transforming ERD into Relations
Presentation transcript:

 Definition  Components  Advantages  Limitations Contents  Definition Definition  Normal Forms Normal Forms  First Normal Form First Normal Form  Second Normal Form Second Normal Form  Third Normal Form Third Normal Form

Definition It is a process of simplifying a relation in such a form that no data is lost during simplification. Simplification is based on certain conditions. The process of normalization was first developed by E.F.Codd. The basic objectives of normalization are to reduce redundancy.

Normal Forms Data can be represented in any of normal forms : first, second or third if it satisfies conditions which are as follows : 1. Data must be represented in atomic form without any group (First Normal Form). 2. There should not be any key which is not completely dependent (Second Normal Form). 3. There should not be transitive dependency (Third Normal Form).

Example Consider a database that contains information of parts supplied by some supplier. Name of city in which supplier is located along with status value of city are also stored in database. Functional dependency diagram for this database can be : P# S# Status City Qty

Example Contd.. In this database S# and P# combination is used as primary key. Qty value depends upon this combination. City in which supplier is located and status value of the city are only related with S#.

First Normal Form (1NF) S#P#QtyCityStatus S1P1100Delhi30 S1P2150Delhi30 S1P3125Delhi30 S1P4140Delhi30 S2P2280Mumbai20 S2P3160Mumbai20 S3P4120Delhi30 A relation is said to be in first normal form if data items are represented in atomic form i.e without any group data item

1NF Contd.. In above table, data items are in two dimensional tabular form without any group, therefore, data is in first normal form. This representation shows a number of limitations : 1. Insertion : If we want to insert information of supplier S4 located at Jaipur with status value 40. We can’t insert this information until that supplier supplies at least one part.

1NF Contd.. 2. Deletion : If we delete the supplier S2 we will loss the information that S2 is located in Mumbai and also that Mumbai has status value Updation : If we change the city of S1 from Delhi to Ambala it is required to search the whole relation otherwise inconsistency may occur. The solution of these problems can be obtained by using Second Normal Form.

Second Normal Form (2NF) A relation is said to be in second normal form if it is in first normal form and every non key attribute is fully dependent on primary key. The solution to the first normal form problems can be obtained by splitting the relation in two relations as follows : S#P#QtyCityStatus S1P1100Delhi30 S1P2150Delhi30 S1P3125Delhi30 S1P4140Delhi30 S2P2280Mumbai20 S2P3160Mumbai20 S3P4120Delhi30 S#CityStatus S1Delhi30 S2Mumbai20 S3Delhi30

2NF Contd.. The second normal form still have problems due to transitive dependency. In second relation S# determines city and city determines status, therefore, status is transitively dependent on S#. Problems of second normal form are : 1. Insertion : We can’t enter the fact that a particular city has a particular status value. e.g. we can’t enter information that particular city Jaipur has a status value 40 until some supplier is located in that city.

2NF Contd.. 2. Deletion : If we delete any record from second relation we will loss the information that a particular city has particular status value. e.g. if we delete the information of supplier S2, the information that the status of Mumbai is 20 is also lost.

2NF Contd.. 3. Updation : If we want to change the status value for Delhi from 30 to 50 the there is a problem of searching the whole second relation otherwise inconsistency will occur. These problems can be solved if we split the second relation and making the relation in Third Normal Form.

Third Normal Form (3NF) A relation is in third normal form if and only if it is in second normal form and every non key attribute is not transitively dependent on primary key. The second relation can be split into two relations which will remove the problems of second relation S#P#Qty S1P1100 S1P2150 S1P3125 S1P4140 S2P2280 S2P3160 S3P4120 S#City S1Delhi S2Mumbai S3Delhi CityStatus Delhi30 Mumbai20

3NF Contd.. Now these two relations are in third normal form. This normal form removes the insertion, deletion & updation anomalies of second normal form i.e. here,  We insert the information that city Jaipur has a status value 40 even though no supplier is located in that city.  We can also delete the information of supplier S2 & this deletion will not effect the status value of Mumbai.  We can also modify the status of any city because changes has to occur at only one place.

Thank You