1 / 23

Chapter 5: Relational Database Design

Chapter 5: Relational Database Design. Information Technology Department Bryar Hassan (MSc Eng.) bryar.hassan@kissr.edu.krd. Contents. What normalization is and what role it plays in database design About the normal forms 1NF, 2NF, 3NF, BCNF, and 4NF

mjustin
Download Presentation

Chapter 5: Relational Database Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 5: Relational Database Design Information Technology Department Bryar Hassan (MSc Eng.) bryar.hassan@kissr.edu.krd

  2. Contents • What normalization is and what role it plays in database design • About the normal forms 1NF, 2NF, 3NF, BCNF, and 4NF • How normal forms can be transformed from lower normal forms to higher normal forms • That normalization and E-R modeling are used concurrently to produce a good database design • That some situations require denormalization to generate information efficiently Database System Concepts

  3. Database Tables and Normalization • Table is basic building block in database design • Normalization is process for assigning attributes to entities • Reduces data redundancies • Helps eliminate data anomalies • Produces controlled redundancies to link tables • Normalization stages • 1NF - First normal form • 2NF - Second normal form • 3NF - Third normal form • 4NF - Fourth normal form Database System Concepts

  4. Need for Normalization Figure 5.1 Database System Concepts

  5. Figure 5.1 Observations • PRO_NUM intended to be primary key • Table entries invite data inconsistencies • Table displays data anomalies • Update • Modifying JOB_CLASS • Insertion • New employee must be assigned project • Deletion • If employee deleted, other vital data lost Database System Concepts

  6. Conversion to 1NF • Repeating groups must be eliminated • Proper primary key developed • Uniquely identifies attribute values (rows) • Combination of PROJ_NUM and EMP_NUM • Dependencies can be identified • Desirable dependencies based on primary key • Less desirable dependencies • Partial • based on part of composite primary key • Transitive • one nonprime attribute depends on another nonprime attribute Database System Concepts

  7. Dependency Diagram (1NF) Database System Concepts

  8. Data Organization: 1NF Figure 5.2 Database System Concepts

  9. 1F Summarized • All key attributes defined • No repeating groups in table • All attributes dependent on primary key Database System Concepts

  10. Conversion to 2NF • Start with 1NF format: • Write each key component on separate line • Write original key on last line • Each component is new table • Write dependent attributes after each key PROJECT (PROJ_NUM, PROJ_NAME) EMPLOYEE (EMP_NUM, EMP_NAME, JOB_CLASS, CHG_HOUR) ASSIGN (PROJ_NUM, EMP_NUM, HOURS) Database System Concepts

  11. 2NF Conversion Results Figure 5.3 Database System Concepts

  12. 2NF Summarized • In 1NF • Includes no partial dependencies • No attribute dependent on a portion of primary key • Still possible to exhibit transitive dependency • Attributes may be functionally dependent on nonkeyattributes Database System Concepts

  13. Conversion to 3NF • Create separate table(s) to eliminate transitive functional dependencies PROJECT (PROJ_NUM, PROJ_NAME) ASSIGN (PROJ_NUM, EMP_NUM, HOURS) EMPLOYEE (EMP_NUM, EMP_NAME, JOB_CLASS) JOB (JOB_CLASS, CHG_HOUR) Database System Concepts

  14. 3NF Summarized • In 2NF • Contains no transitive dependencies Database System Concepts

  15. Normalization and Database Design • Normalization should be part of the design process • E-R Diagram provides macro view • Normalization provides micro view of entities • Focuses on characteristics of specific entities • May yield additional entities • Difficult to separate normalization from E-R diagramming • Business rules must be determined Database System Concepts

  16. Initial ERD for Contracting Company Figure 5.8 Database System Concepts

  17. Modified ERD for Contracting Company Figure 5.9 Database System Concepts

  18. Final ERD for Contracting Company Figure 5.10 Database System Concepts

  19. Higher-Level Normal Forms • Fourth Normal Form (4NF) • Table is in 3NF • Has no multiple sets of multivalued dependencies Database System Concepts

  20. Conversion to 4NF Figure 5.12 Set of Tables in 4NF Figure 5.11 Multivalued Dependencies Database System Concepts

  21. De-normalization • Normalization is one of many database design goals • Normalized table requirements • Additional processing • Loss of system speed • Normalization purity is difficult to sustain due to conflict in: • Design efficiency • Information requirements • Processing Database System Concepts

  22. Un-normalized Table Defects • Data updates less efficient • Indexing more cumbersome • No simple strategies for creating views Database System Concepts

  23. Exercises • Consider the below relation and answer the following questions: • List all functional dependencies satisfied by the relation • Convert the above relation to 1NF, 2NF, 3NF, and then 4NF Database System Concepts

More Related