04.06.2015 Views

Database Modeling and Design

Database Modeling and Design

Database Modeling and Design

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6.1 Fundamentals of Normalization 113<br />

Report 1<br />

report_no<br />

editor<br />

dept_no<br />

dept_name<br />

dept_addr<br />

4216<br />

5789<br />

woolf<br />

koenig<br />

15<br />

27<br />

design<br />

analysis<br />

argus 1<br />

argus 2<br />

Report 2<br />

author_id<br />

53<br />

44<br />

71<br />

26<br />

38<br />

71<br />

author_name<br />

mantei<br />

bolton<br />

koenig<br />

fry<br />

umar<br />

koenig<br />

author_addr<br />

cs-tor<br />

mathrev<br />

mathrev<br />

folkstone<br />

prise<br />

mathrev<br />

Report 3<br />

report_no<br />

4216<br />

4216<br />

4216<br />

5789<br />

5789<br />

5789<br />

author_id<br />

53<br />

44<br />

71<br />

26<br />

38<br />

71<br />

Figure 6.3<br />

2NF tables<br />

Not all performance degradation is eliminated, however; report_no<br />

is still duplicated for each author, <strong>and</strong> deletion of a report requires<br />

updates to two tables (report1 <strong>and</strong> report3) instead of one. However,<br />

these are minor problems compared to those in the 1NF table report.<br />

Note that these three report tables in 2NF could have been generated<br />

directly from an ER (or UML) diagram that equivalently modeled this situation<br />

with entities Author <strong>and</strong> Report <strong>and</strong> a many-to-many relationship<br />

between them.<br />

6.1.4 Third Normal Form<br />

The 2NF tables we established in the previous section represent a significant<br />

improvement over 1NF tables. However, they still suffer from

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!