Chapter 13 Normalization Transparencies. 2 Chapter 13 - Objectives u How to undertake process of normalization. u How to identify most commonly used normal.

Slides:



Advertisements
Similar presentations
The Relational Model System Development Life Cycle Normalisation
Advertisements

1 Database Systems: A Practical Approach to Design, Implementation and Management International Computer Science S. Carolyn Begg, Thomas Connolly Lecture.
Normalization I.
Chapter 5 Normalization Transparencies © Pearson Education Limited 1995, 2005.
INFO 340 Lecture 7 Functional Dependency, Normalization.
1 Minggu 10, Pertemuan 19 Normalization (cont.) Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
Introduction to Schema Refinement. Different problems may arise when converting a relation into standard form They are Data redundancy Update Anomalies.
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.
Normalization. Learners Support Publications 2 Objectives u The purpose of normalization. u The problems associated with redundant data.
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
Lecture9:Functional Dependencies and Normalization for Relational Databases Prepared by L. Nouf Almujally Ref. Chapter Lecture9 1.
CSC271 Database Systems Lecture # 28.
ITS232 Introduction To Database Management Systems Siti Nurbaya Ismail Faculty of Computer Science & Mathematics, Universiti Teknologi MARA (UiTM), Kedah.
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.
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.
Functional Dependency, Normalization
Normalization Transparencies 1. ©Pearson Education 2009 Objectives How the technique of normalization is used in database design. How tables that contain.
ITS232 Introduction To Database Management Systems Siti Nurbaya Ismail Faculty of Computer Science & Mathematics, Universiti Teknologi MARA (UiTM), Kedah.
Lecture9:Functional Dependencies and Normalization for Relational Databases Ref. Chapter Lecture9 1.
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,
Chapter 5.1 and 5.2 Brian Cobarrubia Database Management Systems II January 31, 2008.
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.
NORMALIZATION.
1 CS490 Database Management Systems. 2 CS490 Database Normalization.
Chapter 9 Normalization Chapter 14 & 15 in Textbook.
Chapter 8 Relational Database Design Topic 1: Normalization Chuan Li 1 © Pearson Education Limited 1995, 2005.
Normalization.
Normalization DBMS.
Normalization Dongsheng Lu Feb 21, 2003.
Chapter 7 Normalization Chapter 14 & 15 in Textbook.
Normalization Lecture 7 May Aldoayan.
Chapter 14 Normalization
CHAPTER 5 Normalization Of Database Tables (Part II: The Process)
Normalization.
Database Normalization
Chapter 14 & Chapter 15 Normalization Pearson Education © 2009.
Normalization.
Normalization and FD.
Normalization Dongsheng Lu Feb 21, 2003.
Chapter 7 Normalization Chapter 13 in Textbook.
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.
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:

Chapter 13 Normalization Transparencies

2 Chapter 13 - Objectives u How to undertake process of normalization. u How to identify most commonly used normal forms, namely 1NF, 2NF, 3NF

3 Functional Dependency u Property of the meaning (or semantics) of the attributes in a relation. u Diagrammatic representation: u Determinant of a functional dependency refers to attribute or group of attributes on left-hand side of the arrow.

4 Example - Functional Dependency

5 StaffNo  sName, position, salary, branchNo, bAddress u branchNo  bAddress u bAddress  branchNo u branchNo, position  salary u bAddress, position  salary

6 The Process of Normalization  Formal technique for analyzing a relation based on its primary key and functional dependencies between its attributes.  Often executed as a series of steps. Each step corresponds to a specific normal form, which has known properties.  As normalization proceeds, relations become progressively more restricted (stronger) in format and also less vulnerable to update anomalies.

7 Relationship Between Normal Forms

8 Unnormalized Form (UNF) u A table that contains one or more repeating groups.  To create an unnormalized table: –transform data from information source (e.g. form) into table format with columns and rows.

9 First Normal Form (1NF) u A relation in which intersection of each row and column contains one and only one value.

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

11 UNF to 1NF u Remove repeating group by: –entering appropriate data into the empty columns of rows containing repeating data (‘flattening’ the table). Or by –placing repeating data along with copy of the original key attribute(s) into a separate relation.

12 1 st Normal From

13 Second Normal Form (2NF)  Based on concept of full functional dependency: –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. u 2NF - A relation that is in 1NF and every non- primary-key attribute is fully functionally dependent on the primary key.

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

15 Partial Dependency u A,B  C, D, E u B  C u D is partially depend on B

16 Convert 1 st Normal form to 2 nd Normal Form u Table (A, B, C, D, E) u A, B  C, D, E u B  C u Table_1 (A, B, D, E) u Table_2 (B, C) u There is no partial dependency in Table_1 and Table_2.

17 Example: The CAR relation schema: CAR(State, Reg#, SerialNo, Make, Model, Year) has two keys Key1 = {State, Reg#}, Key2 = {SerialNo}, which are also superkeys. {SerialNo, Make} is a superkey but not a key. Is there a partial dependency?

18 Example clientNoCfNameClNamepropertyNoviewDatecomment CR56AlineStewartPA145/24/2001too small CR56AlineStewartPG364/28/2001 CR56AlineStewartPG45/26/2001 CR62MaryTiregearPA145/14/2001no dining room CR74MikeRichiePG44/21/2001 CR76JohnKayPG44/20/2001too remote Primary key:Functional Dependencies:

19 ClientNo CfName ClName ClientNo propertyNo viewDate comment Viewing Client 2 nd Normal Form

20 Third Normal Form (3NF)  Based on concept of transitive dependency: –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). u 3NF - A relation that is in 1NF and 2NF and in which no non-primary-key attribute is transitively dependent on the primary key.

21 2NF 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 copy of their determinant.

22 Transitive Dependency u Table (A, B, C, D, E) u A, B  C, D, E u D  E u A, B  D  E (Transitivity)

23 3 rd Normal Form u Table (A, B, C, D, E) u A, B  C, D, E u B  C (Partial Dependency) u D  E (Transitive Dependency) u Table_1 (A, B, D, E) u Table_2 (B, C) u Table_1 (A, B, D) u Table_3 (D, E) u Table_2 (B, C) 2 nd Normal Form 3 rd Normal Form

24 StaffNo  sName, position, salary, branchNo, bAddress u branchNo  bAddress u bAddress  branchNo u branchNo, position  salary u bAddress, position  salary Transitive dependency Primary Key:

25 3 rd Normal Form

26 General Definitions of 2NF and 3NF u Second normal form (2NF) –A relation that is in 1NF and every non- primary-key attribute is fully functionally dependent on any candidate key. u Third normal form (3NF) –A relation that is in 1NF and 2NF and in which no non-primary-key attribute is transitively dependent on any candidate key.

27 Review of Normalization (UNF to 3 rd Normal Form)

28 Review of Normalization (UNF to 3rd)

29 Review of Normalization (UNF to BCNF)

30 Review of Normalization (UNF to BCNF)

31 2 nd normal Form PropertyNopAddresses properyNo iDateiTimecommentsstaffNosNamecarReg PROPERTY INSPECTION/STAFF

32 3 rd Normal Form PropertyNopAddresses PROPERTY properyNo iDateiTimecommentsstaffNocarReg INSPECTION staffNosName STAFF