Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Lecture 18 of 42 Monday, 13 October 2008.

Slides:



Advertisements
Similar presentations
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Advertisements

Manipulating Functional Dependencies Zaki Malik September 30, 2008.
Dr. Kalpakis CMSC 461, Database Management Systems URL: Relational Database Design.
Chapter 3 Notes. 3.1 Functional Dependencies A functional dependency is a statement that – two tuples of a relation that agree on some particular set.
Temple University – CIS Dept. CIS616– Principles of Data Management V. Megalooikonomou Functional Dependencies (based on notes by Silberchatz,Korth, and.
Topics to be discusses Functional Dependency Key
©Silberschatz, Korth and Sudarshan Relational Database Design First Normal Form Pitfalls in Relational Database Design Functional Dependencies Decomposition.
7.1 Chapter 7: Relational Database Design. 7.2 Chapter 7: Relational Database Design Features of Good Relational Design Atomic Domains and First Normal.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Slides adapted from A. Silberschatz et al. Database System Concepts, 5th Ed. Relational Database Design - part 2 - Database Management Systems I Alex Coman,
CMSC424: Database Design Instructor: Amol Deshpande
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Refining an ER Diagram Given the F.D.s: sid  dname.
Functional Dependencies (Part 3) Presented by Nash Raghavan All page numbers are in reference to Database System Concepts (5 th Edition)
1 CMSC424, Spring 2005 CMSC424: Database Design Lecture 9.
Relational Database Design Theory Lecture 6. The Banking Schema branch = (branch_name, branch_city, assets) customer = (customer_id, customer_name, customer_street,
Relational Database Design
1 Multi-valued Dependencies. 2 Multivalued Dependencies There are database schemas in BCNF that do not seem to be sufficiently normalized. Consider a.
Relational Database Design Theory Lecture 6. Relational Database Design Features of Good Relational Design First Normal Form Decomposition Using Functional.
1 Database Theory and Methodology. 2 The Good and the Bad So far we have not developed any measure of “goodness” to measure the quality of the design,
Chapter 14 Advanced Normalization Transparencies © Pearson Education Limited 1995, 2005.
Chapter 8: Relational Database Design First Normal Form First Normal Form Functional Dependencies Functional Dependencies Decomposition Decomposition Boyce-Codd.
©Silberschatz, Korth and Sudarshan7.1Database System Concepts Chapter 7: Relational Database Design First Normal Form Pitfalls in Relational Database Design.
Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 8: Relational.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan Chapter 7: Relational Database Design.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2 Chapter 7: Relational Database Design First Normal Form Goals of Relational.
Computing & Information Sciences Kansas State University Wednesday, 01 Oct 2008CIS 560: Database System Concepts Lecture 15 of 42 Wednesday, 01 October.
Chapter 7: Relational Database Design. 7.2Unite International CollegeDatabase Management Systems Chapter 7: Relational Database Design Features of Good.
 Features of Good Relational Design  Atomic Domains and First Normal Form  Decomposition Using Functional Dependencies  Functional Dependency Theory.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
Chapter 7: Relational Database Design. 7.2Unite International CollegeDatabase Management Systems Chapter 7: Relational Database Design Features of Good.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design Pitfalls in.
Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 8: Relational.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
BCNF & Lossless Decomposition Prof. Sin-Min Lee Department of Computer Science.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
Computing & Information Sciences Kansas State University Tuesday, 27 Feb 2007CIS 560: Database System Concepts Lecture 18 of 42 Tuesday, 27 February 2007.
Computing & Information Sciences Kansas State University Wednesday, 04 Oct 2006CIS 560: Database System Concepts Lecture 17 of 42 Wednesday, 04 October.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Database System Concepts ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational Database.
1 Dept. of CIS, Temple Univ. CIS616/661 – Principles of Data Management V. Megalooikonomou Integrity Constraints (based on slides by C. Faloutsos at CMU)
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Database System Concepts, 5th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Relational.
Chapter 7: Relational Database Design
Lecture 17 4 th Normal Form Prof. Sin-Min Lee Department of Computer Science.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts Chapter 7: Relational Database Design First Normal.
Chapter 8 Relational Database Design. 2 Relational Database Design: Goals n Reduce data redundancy (undesirable replication of data values) n Minimize.
1 CS 430 Database Theory Winter 2005 Lecture 8: Functional Dependencies Second, Third, and Boyce-Codd Normal Forms.
Computing & Information Sciences Kansas State University Friday, 03 Oct 2007CIS 560: Database System Concepts Lecture 16 of 42 Wednesday, 03 October 2007.
Database System Concepts, 5th Ed. Bin Mu at Tongji University Chapter 7: Relational Database Design.
Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts.
Database System Concepts, 5th Ed. ©Sang Ho Lee Chapter 7: Relational Database Design.
Module 5: Overview of Database Design -- Normalization
Relational Database Design
Chapter 8: Relational Database Design
Chapter 7: Relational Database Design
Chapter 7: Relational Database Design
Temple University – CIS Dept. CIS331– Principles of Database Systems
Normal Form: 4 & 5.
Chapter 7: Relational Database Design
Chapter 7: Relational Database Design
Chapter 7: Relational Database Design
Chapter 7: Relational Database Design
Chapter 7: Relational Database Design
Chapter 7a: Overview of Database Design -- Normalization
Presentation transcript:

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Lecture 18 of 42 Monday, 13 October 2008 William H. Hsu Department of Computing and Information Sciences, KSU KSOL course page: Course web site: Instructor home page: Reading for Next Class: Second half of Chapter 7, Silberschatz et al., 5 th edition More Normal Forms Notes: JSP, MP4; Applications of Normalization

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Goals of Normalization Let R be a relation scheme with a set F of functional dependencies. Decide whether a relation scheme R is in “good” form. In the case that a relation scheme R is not in “good” form, decompose it into a set of relation scheme {R 1, R 2,..., R n } such that  each relation scheme is in good form  the decomposition is a lossless-join decomposition  Preferably, the decomposition should be dependency preserving.

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts How good is BCNF? There are database schemas in BCNF that do not seem to be sufficiently normalized Consider a database classes (course, teacher, book ) such that (c, t, b)  classes means that t is qualified to teach c, and b is a required textbook for c The database is supposed to list for each course the set of teachers any one of which can be the course’s instructor, and the set of books, all of which are required for the course (no matter who teaches it).

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts There are no non-trivial functional dependencies and therefore the relation is in BCNF Insertion anomalies – i.e., if Marilyn is a new teacher that can teach database, two tuples need to be inserted (database, Marilyn, DB Concepts) (database, Marilyn, Ullman) courseteacherbook database operating systems Avi Hank Sudarshan Avi Pete DB Concepts Ullman DB Concepts Ullman DB Concepts Ullman OS Concepts Stallings OS Concepts Stallings classes How good is BCNF? (Cont.)

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Therefore, it is better to decompose classes into: courseteacher database operating systems Avi Hank Sudarshan Avi Jim teaches coursebook database operating systems DB Concepts Ullman OS Concepts Shaw text This suggests the need for higher normal forms, such as Fourth Normal Form (4NF), which we shall see later. How good is BCNF? (Cont.)

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Functional-Dependency Theory We now consider the formal theory that tells us which functional dependencies are implied logically by a given set of functional dependencies. We then develop algorithms to generate lossless decompositions into BCNF and 3NF We then develop algorithms to test if a decomposition is dependency-preserving

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Closure of a Set of Functional Dependencies Given a set F set of functional dependencies, there are certain other functional dependencies that are logically implied by F.  For example: If A  B and B  C, then we can infer that A  C The set of all functional dependencies logically implied by F is the closure of F. We denote the closure of F by F +. We can find all of F + by applying Armstrong’s Axioms:  if   , then    (reflexivity)  if   , then      (augmentation)  if   , and   , then    (transitivity) These rules are  sound (generate only functional dependencies that actually hold) and  complete (generate all functional dependencies that hold).

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Example R = (A, B, C, G, H, I) F = { A  B A  C CG  H CG  I B  H} some members of F +  A  H  by transitivity from A  B and B  H  AG  I  by augmenting A  C with G, to get AG  CG and then transitivity with CG  I  CG  HI  by augmenting CG  I to infer CG  CGI, and augmenting of CG  H to infer CGI  HI, and then transitivity

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Procedure for Computing F + To compute the closure of a set of functional dependencies F: F + = F repeat for each functional dependency f in F + apply reflexivity and augmentation rules on f add the resulting functional dependencies to F + for each pair of functional dependencies f 1 and f 2 in F + if f 1 and f 2 can be combined using transitivity then add the resulting functional dependency to F + until F + does not change any further NOTE: We shall see an alternative procedure for this task later

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Closure of Functional Dependencies (Cont.) We can further simplify manual computation of F + by using the following additional rules.  If    holds and    holds, then     holds (union)  If     holds, then    holds and    holds (decomposition)  If    holds and     holds, then     holds (pseudotransitivity) The above rules can be inferred from Armstrong’s axioms.

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Closure of Attribute Sets Given a set of attributes  define the closure of  under F (denoted by  + ) as the set of attributes that are functionally determined by  under F Algorithm to compute  +, the closure of  under F result :=  ; while (changes to result) do for each    in F do begin if   result then result := result   end

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Example of Attribute Set Closure R = (A, B, C, G, H, I) F = {A  B A  C CG  H CG  I B  H} (AG) + 1.result = AG 2.result = ABCG(A  C and A  B) 3.result = ABCGH(CG  H and CG  AGBC) 4.result = ABCGHI(CG  I and CG  AGBCH) Is AG a candidate key? 1.Is AG a super key? 1.Does AG  R? == Is (AG) +  R 2.Is any subset of AG a superkey? 1.Does A  R? == Is (A) +  R 2.Does G  R? == Is (G) +  R

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Uses of Attribute Closure There are several uses of the attribute closure algorithm: Testing for superkey:  To test if  is a superkey, we compute  +, and check if  + contains all attributes of R. Testing functional dependencies  To check if a functional dependency    holds (or, in other words, is in F + ), just check if    +.  That is, we compute  + by using attribute closure, and then check if it contains .  Is a simple and cheap test, and very useful Computing closure of F  For each   R, we find the closure  +, and for each S   +, we output a functional dependency   S.

Computing & Information Sciences Kansas State University Monday, 13 Oct 2008CIS 560: Database System Concepts Canonical Cover Sets of functional dependencies may have redundant dependencies that can be inferred from the others  For example: A  C is redundant in: {A  B, B  C}  Parts of a functional dependency may be redundant  E.g.: on RHS: {A  B, B  C, A  CD} can be simplified to {A  B, B  C, A  D}  E.g.: on LHS: {A  B, B  C, AC  D} can be simplified to {A  B, B  C, A  D} Intuitively, a canonical cover of F is a “minimal” set of functional dependencies equivalent to F, having no redundant dependencies or redundant parts of dependencies