Normalization. Learners Support Publications www.lsp4you.com 2 Objectives u The purpose of normalization. u The problems associated with redundant data.

Slides:



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

The Relational Model System Development Life Cycle Normalisation
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 15 Basics of Functional Dependencies and Normalization for Relational.
1 Database Systems: A Practical Approach to Design, Implementation and Management International Computer Science S. Carolyn Begg, Thomas Connolly Lecture.
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
Normalization I.
Chapter 5 Normalization Transparencies © Pearson Education Limited 1995, 2005.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 15 Basics of Functional Dependencies and Normalization for Relational.
1 Minggu 10, Pertemuan 19 Normalization (cont.) Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
Normalization II. Boyce–Codd Normal Form (BCNF) Based on functional dependencies that take into account all candidate keys in a relation, however BCNF.
Chapter 14 Advanced Normalization Transparencies © Pearson Education Limited 1995, 2005.
Normalization. Introduction Badly structured tables, that contains redundant data, may suffer from Update anomalies : Insertions Deletions Modification.
FUNCTIONAL DEPENDENCIES
Lecture 12 Inst: Haya Sammaneh
Chapter 6 Normalization 正規化. 6-2 In This Chapter You Will Learn:  更動異常  How tables that contain redundant data can suffer from update 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,
Chapter 13 Normalization Transparencies. 2 Last Class u Access Lab.
1 Pertemuan 23 Normalisasi Matakuliah: >/ > Tahun: > Versi: >
Lecture 6 Normalization: Advanced forms. Objectives How inference rules can identify a set of all functional dependencies for a relation. How Inference.
Normalization Transparencies
CSC271 Database Systems Lecture # 28.
Chapter 13 Normalization Transparencies. 2 Chapter 13 - Objectives u Purpose of normalization. u Problems associated with redundant data. u Identification.
Chapter 13 Normalization. 2 Chapter 13 - Objectives u Purpose of normalization. u Problems associated with redundant data. u Identification of various.
CSE314 Database Systems Basics of Functional Dependencies and Normalization for Relational Databases Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E.
Chapter 13 Normalization © Pearson Education Limited 1995, 2005.
Lecture 5 Normalization. Objectives The purpose of normalization. How normalization can be used when designing a relational database. The potential problems.
Chapter 13 Normalization Transparencies Last Updated: 08 th May 2011 By M. Arief
Chapter 10 Normalization Pearson Education © 2009.
Normalization Transparencies 1. ©Pearson Education 2009 Objectives How the technique of normalization is used in database design. How tables that contain.
Chapter 13 Normalization Transparencies. 2 Chapter 13 - Objectives u How to undertake process of normalization. u How to identify most commonly used normal.
Lecture Nine: Normalization
Dr. Mohamed Osman Hegaz1 Logical data base design (2) Normalization.
© Pearson Education Limited, Normalization Bayu Adhi Tama, M.T.I. Faculty of Computer Science University of Sriwijaya.
9/23/2012ISC329 Isabelle Bichindaritz1 Normalization.
Normalization. 2 u Main objective in developing a logical data model for relational database systems is to create an accurate representation of the data,
Lecture 10 Normalization. Introduction Relations derived from ER model may be ‘faulty’ – Subjective process. – May cause data redundancy, and insert/delete/update.
IST Database Normalization Todd Bacastow IST 210.
11/10/2009GAK1 Normalization. 11/10/2009GAK2 Learning Objectives Definition of normalization and its purpose in database design Types of normal forms.
Normalization. Overview Earliest  formalized database design technique and at one time was the starting point for logical database design. Today  is.
ITD1312 Database Principles Chapter 4C: Normalization.
Chapter 7 Normalization Chapter 14 & 15 in Textbook.
Database Architecture Normalization. Purpose of Normalization A technique for producing a set of relations with desirable properties, given the data requirements.
1 CS490 Database Management Systems. 2 CS490 Database Normalization.
Chapter 8 Relational Database Design Topic 1: Normalization Chuan Li 1 © Pearson Education Limited 1995, 2005.
Normalization.
Advanced Normalization
Normalization Karolina muszyńska
Normalization DBMS.
Normalization Dongsheng Lu Feb 21, 2003.
Advanced Normalization
Normalization Lecture 7 May Aldoayan.
Chapter 14 Normalization
Chapter 15 Basics of Functional Dependencies and Normalization for Relational Databases.
Normalization.
Database Normalization
Chapter 14 & Chapter 15 Normalization Pearson Education © 2009.
Normalization.
Normalization Dongsheng Lu Feb 21, 2003.
Chapter 14 Normalization – Part I Pearson Education © 2009.
Normalization – Part II
Database solutions The process of normalization Marzena Nowakowska Faculty of Management and Computer Modelling Kielce University of Technology rooms:
Normalization Dale-Marie Wilson, Ph.D..
Chapter 14 Normalization.
Minggu 9, Pertemuan 18 Normalization
Chapter 14 Normalization.
Normalization February 28, 2019 DB:Normalization.
國立臺北科技大學 課程:資料庫系統 2015 fall Chapter 14 Normalization.
Chapter 7 Normalization Chapter 14 & 15 in Textbook.
Chapter 14 Normalization Pearson Education © 2009.
Presentation transcript:

Normalization

Learners Support Publications 2 Objectives u The purpose of normalization. u The problems associated with redundant data. u The identification of various types of update anomalies such as insertion, deletion, and modification anomalies. u How to recognize the appropriateness or quality of the design of relations.

Learners Support Publications 3 Objectives u The concept of functional dependency, the main tool for measuring the appropriateness of attribute groupings in relations. u How functional dependencies can be used to group attributes into relations that are in a known normal form. u How to define normal forms for relations.

Learners Support Publications 5 Objectives u How to undertake the process of normalization. u How to identify the most commonly used normal forms, namely first (1NF), second (2NF), and third (3NF) normal forms, and Boyce–Codd normal form (BCNF). u How to identify fourth (4NF), and fifth (5NF) normal forms.

Learners Support Publications 6 Objectives u How to undertake the process of normalization. u How to identify the most commonly used normal forms, namely first (1NF), second (2NF), and third (3NF) normal forms, and Boyce–Codd normal form (BCNF). u How to identify fourth (4NF), and fifth (5NF) normal forms.

Learners Support Publications 7 Normalization  Main objective in developing a logical data model for relational database systems is to create an accurate representation of the data, its relationships, and constraints.  To achieve this objective, we must identify a suitable set of relations.

Learners Support Publications 8 Normalization  A technique for producing a set of relations with desirable properties, given the data requirements of an enterprise.  Developed by E.F. Codd (1972).  Often performed as a series of tests on a relation to determine whether it satisfies or violates the requirements of a given normal form.

Learners Support Publications 9 Normalization  Four most commonly used normal forms are first (1NF), second (2NF), third (3NF) and Boyce-Codd (BCNF) normal forms.  Based on functional dependencies among the attributes of a relation.  A relation can be normalized to a specific form to prevent the possible occurrence of update anomalies.

Learners Support Publications 10 Data Redundancy  Major aim of relational database design is to group attributes into relations to minimize data redundancy and reduce file storage space required by base relations.  Problems associated with data redundancy are illustrated by comparing the Staff and Branch relations with the Staff_Branch relation.

Learners Support Publications 11 Data Redundancy

Learners Support Publications 12 Data Redundancy  Staff_Branch relation has redundant data; the details of a branch are repeated for every member of staff.  In contrast, the branch information appears only once for each branch in the Branch relation and only the branch number (Branch_No) is repeated in the Staff relation, to represent where each member of staff is located.

Learners Support Publications 13 Update Anomalies  Relations that contain redundant information may potentially suffer from update anomalies.  Types of update anomalies include – Insertion – Deletion – Modification

Learners Support Publications 14 Lossless-join and Dependency Preservation Properties u Two important properties of decomposition. – Lossless-join property enables us to find any instance of the original relation from corresponding instances in the smaller relations. – Dependency preservation property enables us to enforce a constraint on the original relation by enforcing some constraint on each of the smaller relations.

Learners Support Publications 15 Functional Dependency  Main concept associated with normalization.  Functional Dependency – Describes the relationship between attributes in a relation. – For example, if A and B are attributes of relation R, B is functionally dependent on A (denoted A  B), if each value of A in R is associated with exactly one value of B in R.

Learners Support Publications 16 Functional Dependency  Property of the meaning or semantics of the attributes in a relation.  The determinant of a functional dependency refers to the attribute or group of attributes on the left-hand side of the arrow.  Diagrammatic representation.

Learners Support Publications 17 Example - Functional Dependency

Learners Support Publications 18 The Process of Normalization  Formal technique for analyzing a relation based on its primary key and the functional dependencies between the attributes of that relation.  Often executed as a series of steps. Each step corresponds to a specific normal form, which has known properties.

Learners Support Publications 19 The Process of Normalization  As normalization proceeds, the relations become progressively more restricted (stronger) in format and also less vulnerable to update anomalies.

Learners Support Publications 20 Relationship Between Normal Forms

Learners Support Publications 21 Unnormalized Form (UNF) u A table that contains one or more repeating groups.  To create an unnormalized table – Transform the data from the information source (e.g. form) into table format with columns and rows.

Learners Support Publications 22 First Normal Form (1NF) u A relation in which the intersection of each row and column contains one and only one value.

Learners Support Publications 23 UNF to 1NF u Nominate an attribute or group of attributes to act as the key for the unnormalized table. u Identify the repeating group(s) in the unnormalized table which repeats for the key attribute(s).

Learners Support Publications 24 UNF to 1NF u Remove the repeating group by – Entering appropriate data into the empty columns of rows containing the repeating data (‘flattening’ the table). – Or by – Placing the repeating data along with a copy of the original key attribute(s) into a separate relation.

Learners Support Publications 25 Second Normal Form (2NF)  Based on the concept of full functional dependency.  Full functional dependency indicates that if – A and B are attributes of a relation, – B is fully dependent on A if B is functionally dependent on A but not on any proper subset of A.

Learners Support Publications 26 Second Normal Form (2NF) u A relation that is in 1NF and every non- primary-key attribute is fully functionally dependent on the primary key.

Learners Support Publications NF to 2NF  Identify the primary key for the 1NF relation.  Identify the functional dependencies in the relation.  If partial dependencies exist on the primary key remove them by placing then in a new relation along with a copy of their determinant.

Learners Support Publications 28 Third Normal Form (3NF)  Based on the concept of transitive dependency.  Transitive Dependency is a condition where – A, B and C are attributes of a relation such that if A  B and B  C, – then C is transitively dependent on A through B. (Provided that A is not functionally dependent on B or C).

Learners Support Publications 29 Third Normal Form (3NF) u A relation that is in 1NF and 2NF and in which no non-primary-key attribute is transitively dependent on the primary key.

Learners Support Publications NF to 3NF  Identify the primary key in the 2NF relation.  Identify functional dependencies in the relation.  If transitive dependencies exist on the primary key remove them by placing them in a new relation along with a copy of their determinant.

Learners Support Publications 31 Boyce-Codd Normal Form (BCNF)  Based on functional dependencies that takes into account all candidate keys in a relation.  For a relation with only one candidate key, 3NF and BCNF are equivalent.  A relation is in BCNF, if and only if every determinant is a candidate key.

Learners Support Publications 32 Boyce-Codd Normal Form (BCNF)  Violation of BCNF may occur in a relation that – contains two (or more) composite keys – which overlap and share at least one attribute in common.

Learners Support Publications NF to BCNF u Identify all candidate keys in the relation.  Identify all functional dependencies in the relation. u If functional dependencies exists in the relation where their determinants are not candidate keys for the relation, remove the functional dependencies by placing them in a new relation along with a copy of their determinant.

Learners Support Publications 34 Example 1 - Normalization Report

Learners Support Publications 35 Example 1 - Normalization UNF to 1NF

Learners Support Publications 36 Example 1 - Normalization UNF to 1NF (Alternative)

Learners Support Publications 37 Example 1 - Normalization FDs for Customer_Rental Relation

Learners Support Publications 38 Example 1 - Normalization Customer_Rental to 2NF Relations

Learners Support Publications 39 Example 1 - Normalization Property_Owner to 3NF Relations

Learners Support Publications 40 Example 1 - Normalization Process of Decomposition

Learners Support Publications 41 Example 1 - Normalization Summary of 3NF Relations

Learners Support Publications 42 Example 2 - Normalization 3NF to BCNF Relations

Learners Support Publications 43 Example 3 - Normalization Report

Learners Support Publications 44 Example 3 - Normalization UNF to 1NF Relation

Learners Support Publications 45 Example 3 - Normalization FDs of Property_Inspection Relation

Learners Support Publications 46 Example 3 - Normalization Review Process of Decomposition

Learners Support Publications 47 Fourth Normal Form (4NF) u Associated with a dependency called multi- valued dependency (MVD). u MVDs in a relation are due to first normal form (1NF), which disallows an attribute in a row from having a set of values.

Learners Support Publications 48 MVD u Represents a dependency between attributes (for example, A, B, and C) in a relation, such that for each value of A there is a set of values for B, and a set of values for C. However, the set of values for B and C are independent of each other. u MVD between attributes A, B, and C in a relation using the following notation: A   B A   C

Learners Support Publications 49 Fourth Normal Form (4NF) u A relation that is in Boyce-Codd Normal Form and contains no MVDs. u BCNF to 4NF involves the removal of the MVD from the relation by placing the attribute(s) in a new relation along with a copy of the determinant(s).

Learners Support Publications 50 Example 4 - Normalization BCNF to 4NF Relations

Learners Support Publications 51 Fifth Normal Form (5NF) u Lossless-join property refers to when we decompose a relation into two relations - we can rejoin the resulting relations to produce the original relation. u However, sometimes there is the requirement to decompose a relation into more than two relations. Although rare, these cases are managed by join dependency and 5NF.

Learners Support Publications NF and Lossless-join Dependency u Lossless-join Dependency – A property of decomposition, which ensures that no spurious rows are generated when relations are reunited through a natural join operation. u 5NF – A relation that has no join dependency.

Learners Support Publications 53 Example 4 - Normalization 4NF to 5NF Relations

Learners Support Publications 54 The Process of Normalization up to 5NF