1 / 31

normalization

Learn about the normalization process in database design, different normal forms, and how to transform lower forms to higher forms. Discover the benefits of normalization and its role in reducing redundancies and data anomalies.

sflaherty
Download Presentation

normalization

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. DATABASE DESIGN & DEVELOPMENT normalization Zatil Ridh'wah Hj Darot

  2. normalization • Normalization is the process of _______________ data in a database so that it meets two basic requirements: • (1) There is no redundancy of data (all data is stored in only one place), and • (2) data dependencies are logical (all related data items are stored together). • Normalization is important for many reasons, but chiefly because it allows databases to take up as little disk space as possible, resulting in increased performance.

  3. objectives • What normalization is and what role it plays in the database design process. • 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 ER modeling are used concurrently to produce a good database design.

  4. Normalization • Process for ________________________ table structures to minimize data redundancies. • Reduces data anomalies • Series of stages called normal forms: • First normal form (1NF) • Second normal form (2NF) • Third normal form (3NF)

  5. Normalization (continued) • 2NF is better than 1NF; 3NF is better than 2NF • For most business database design purpose, 3NF is as high as needed in normalization • Highest level of normalization is not always most desirable.

  6. the need for normalization • Data redundancies and anomalies • Anomalies: • An inconsistency • A database structure that will be prone to errors in the data • Not necessarily wrong, but will promote __________data rather than prevent it

  7. summary of anomalies - review

  8. the normalization process

  9. the normalization process (cont'd) • Objective of normalization is to ensure that all tables are in at least 3NF • Higher forms are not likely to be encountered in business environment • Normalization works one relation at a time • Progressively breaks table into new set of relations based on ___________________

  10. the normalization process (cont'd) Partial dependency • Exists when there is a functional dependencies in which the determinant is only part of the primary key • For eg A,B C, A C (C dependent on A,B) Transitive dependency • Exists when there are functional dependencies such that X Y, Y Z, and X is the primary key.

  11. un- normalized table

  12. conversion to first normal form • Repeating group • Group of multiple entries of same type can exist for any single key attribute occurrence • Relational table _____________ contain repeating groups • Normalizing table structure will reduce data redundancies

  13. Normalization is three- step procedure: Step 1: Eliminating the repeating groups - Eliminate nulls: each repeating group attribute contains an appropriate data value Step 2: Identify the primary key - Must uniquely identify attribute value - New key must be composed Step 3: Identify all dependencies - Dependencies are depicted with a diagram

  14. conversion to first normal form (cont'd) • Dependency diagram: - Depicts all dependencies found within given table structure - Helpful in getting bird's eye view of all relationships among table's attributes - Makes it less likely that you will overlook an important ______________

  15. conversion to first normal form (cont'd) • First normal form describes tabular format: • All key attributes are defined • No repeating groups in the table • All attributes are _____________ on primary key • All relational tables satisfy 1NF requirements • Some tables contain partial dependencies • Dependencies are based on part of the primary key • Should be used with caution

  16. Conversion to second normal form • Step 1: Make new tables to eliminate partial dependencies • Write each key component on separate time, then write original (composite) key on last line • Each component will become key in new table • Step 2: Reassign corresponding dependent attributes • Determine attributes that are dependent on other attributes • At this point, most anomalies have been eliminated

  17. Conversion to second normal form (cont'd) • Table is in second normal form (2NF) when: • It is in 1NF and • It includes__________________: • No attribute is dependent on only portion of primary key

  18. conversion to third normal form • Step 1: Make new tables to eliminate transitive dependencies • For every transitive dependency, write its determinant as PK for new table • Determinant: any attribute whose value determines other values within a row

  19. conversion to third normal form (cont'd) • Step 2: Reassign corresponding dependent attributes • Identify attributes dependent on each determinant identified in step 2 • Identify dependency • Name table to reflect its contents and function

  20. conversion to third normal form (cont'd) • A table is in third normal form (3NF) when both of the following are true: • It is in 2NF • It contains ____________________

  21. Summary • Normalization minimizes data redundancies • First three normal form (1NF, 2NF and 3NF) are most commonly encountered • Table is in 1NF when: • All key attributes are defined • All remaining attributes are dependent on primary key

  22. summary (cont'd) • Table is in 2NF when it in 1NF and contains no partial dependencies • Table is in 3NF when it is in 2NF and contains no transitive dependencies • Table that is not in 3NF may be split into new tables until all of the tables meet 3NF requirements

  23. tutorial The table shown in Figure 1, lists sample dentist/patient appointment data. A patient is given an appointment at a specific time and date with a dentist located at a particular surgery. On each day of patient appointments, a dentist is allocated to a specific surgery for that day. (a) The table shown in Figure 1 is susceptible to update anomalies. Provide examples of insertion, deletion and update anomalies. (b) Identify the functional dependencies represented by the attributes shown in the table of Figure 1. State any assumptions you make about the data and the attributes shown in this table. (c) Describe and illustrate the process of normalizing the table shown in Figure 1 to 3NF relations. Identify the primary, alternate, and foreign keys in your 3NF relations.

  24. An agency called InstantCover supplies part-time/temporary staff to hotels throughout Scotland. The table shown in Figure 2 lists the time spent by agency staff working at two hotels. The National Insurance Number (NIN) is unique for employee. • The table shown in Figure 2 is susceptible to update anomalies. Provide examples of insertion, deletion, and modification anomalies. • Describe and illustrate the process of normalizing the table shown in Figure 2 to 3NF. State any assumptions you make about the data shown in this table.

  25. Given the ORDER table below, illustrate the process of normalizing the table structure to the Third Normal Form (3NF) i.e. showing all intermediate stages, that is, 1NF and 2NF. Draw the relevant dependency diagrams and identify all dependencies.Write the relational schemas associated with the normalized tables.

  26. references • Database Principles: Fundamentals of Design, Implementation, and Management. Tenth Edition. • Conolly, T. and Begg, C. (2014) Database Systems: A Practical Approach to Design, Implementation and Management. 6th Ed. Global Edition. Pearson.

More Related