Scribd
Upload
16 views

06-Schema Design and Normalization

The document outlines the steps in database design including requirements analysis, conceptual design, logical design, schema refinement, and physical design. It then discusses different types of dependencies like functional dependence, multivalued dependencies, partial dependencies, and transitive dependencies. Finally, it explains the stages of normalization including first, second, and third normal form and how they help remove redundancies and anomalies from database schemas.

Uploaded by

ww7271030
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
16 views

06-Schema Design and Normalization

The document outlines the steps in database design including requirements analysis, conceptual design, logical design, schema refinement, and physical design. It then discusses different types of dependencies like functional dependence, multivalued dependencies, partial dependencies, and transitive dependencies. Finally, it explains the stages of normalization including first, second, and third normal form and how they help remove redundancies and anomalies from database schemas.

Uploaded by

ww7271030
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Schema Design and Normalization

Steps in Database Design

• Requirements Analysis : user needs; what must database do?

• Conceptual Design : high level description (often done with ER model)

• Logical Design : translate ER into DBMS data model

• Schema Refinement : consistency, normalization

• Physical Design: indexes, disk layout

• Security Design : who accesses what, and how


Database Dependencies

• A dependency occurs in a database when information stored in the


same database table uniquely determines other information stored in the
same table.

• You can also describe this as a relationship where knowing the value of
one attribute (or a set of attributes) is enough to tell you the value of
another attribute (or set of attributes) in the same table.
Functional
Dependence
Salesperson Number Salesperson Name

• Salesperson Number is the determinant.

• The value of Salesperson Number determines the value of Salesperson


Name.

• Salesperson Name is functionally dependent on Salesperson Number.

7-4
Multivalued dependencies
• Multivalued dependencies occur when the presence of one or
more rows in a table implies the presence of one or more other rows in
that same table.
Partial Dependency

• Partial Dependency – when an non-key attribute is


determined by a part, but not the whole, of a COMPOSITE
primary key.

Partial
CUSTOMER Dependency

Cust_ID Name Order_ID


101 AT&T 1234
101 AT&T 156
125 Cisco 1250
Transitive dependencies

• Transitive dependencies occur when there is an indirect


relationship that causes a functional dependency.
• For example:
– ”A -> C” is a transitive dependency when it is true only because both “A -> B”
and “B -> C” are true.
Example FDs

Proper FDs Transitive FDs

Partial Key FD

Partial Key FDs


NORMALIZATION
Stages of Normalisation
Unnormalised
(UDF)
Remove repeating groups
First normal form
(1NF)
Remove partial dependencies
Second normal form
(2NF)
Remove transitive dependencies
Third normal form
(3NF)
1NF Normalization

Proper translation
from ER multi-value
attributes will
achieve 1NF.

Still not a good solution,


since we have redundancy in
Dnumber and Dmgr_ssn.
(This will be handled by 2NF.)
2NF Normalization

Move the partial key and dependent attributes to a new relation.


3NF Normalization

You might also like