7 relational database design algorithms and further dependencies

Chapter 11
Relational Database Design
Algorithms and Further
Dependencies

Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe

Chapter Outline









0. Designing a Set of Relations
1. Properties of Relational Decompositions
2. Algorithms for Relational Database Schema
3. Multivalued Dependencies and Fourth Normal
Form
4. Join Dependencies and Fifth Normal Form
5. Inclusion Dependencies
6. Other Dependencies and Normal Forms


Slide 11- 2

DESIGNING A SET OF RELATIONS
(1)


The Approach of Relational Synthesis
(Bottom-up Design):







Assumes that all possible functional dependencies
are known.
First constructs a minimal set of FDs
Then applies algorithms that construct a target set
of 3NF or BCNF relations.
Additional criteria may be needed to ensure the
the set of relations in a relational database are
satisfactory (see Algorithms 11.2 and 11.4).

Slide 11- 3

DESIGNING A SET OF RELATIONS
(2)


Goals:


Lossless join property (a must)




Dependency preservation property




Algorithm 11.1 tests for general losslessness.
Algorithm 11.3 decomposes a relation into BCNF
components by sacrificing the dependency
preservation.

Additional normal forms



4NF (based on multi-valued dependencies)
5NF (based on join dependencies)


Slide 11- 4

1. Properties of Relational
Decompositions (1)


Relation Decomposition and
Insufficiency of Normal Forms:
 Universal Relation Schema:




A relation schema R = {A1, A2, …, An}
that includes all the attributes of the
database.

Universal relation assumption:


Every attribute name is unique.


Slide 11- 5

Properties of Relational
Decompositions (2)


Relation Decomposition and
Insufficiency of Normal Forms (cont.):


Decomposition:




The process of decomposing the universal relation
schema R into a set of relation schemas D =
{R1,R2, …, Rm} that will become the relational
database schema by using the functional
dependencies.

Attribute preservation condition:


Each attribute in R will appear in at least one
relation schema Ri in the decomposition so that no
attributes are “lost”.


Slide 11- 6

Decompositions (2)




Another goal of decomposition is to have each
individual relation Ri in the decomposition D be in
BCNF or 3NF.
Additional properties of decomposition are
needed to prevent from generating spurious
tuples


Slide 11- 7

Decompositions (3)


Dependency Preservation Property of a
Decomposition:




Definition: Given a set of dependencies F on R,
the projection of F on Ri, denoted by Ri(F) where
Ri is a subset of R, is the set of dependencies X 
Y in F+ such that the attributes in X υ Y are all
contained in Ri.
Hence, the projection of F on each relation
schema Ri in the decomposition D is the set of
functional dependencies in F+, the closure of F,
such that all their left- and right-hand-side
attributes are in Ri.


Slide 11- 8

Decompositions (4)


Dependency Preservation Property of a
Decomposition (cont.):


Dependency Preservation Property:






A decomposition D = {R1, R2, ..., Rm} of R is
dependency-preserving with respect to F if the
union of the projections of F on each Ri in D is
equivalent to F; that is
((R1(F)) υ . . . υ (Rm(F)))+ = F+
(See examples in Fig 10.12a and Fig 10.11)

Claim 1:


It is always possible to find a dependencypreserving decomposition D with respect to F such
that each relation Ri in D is in 3nf.

Slide 11- 9

Decompositions (5)


Lossless (Non-additive) Join Property of a
Decomposition:


Definition: Lossless join property: a decomposition D = {R1,
R2, ..., Rm} of R has the lossless (nonadditive) join property
with respect to the set of dependencies F on R if, for every
relation state r of R that satisfies F, the following holds, where *
is the natural join of all the relations in D:

* ( R1(r), ..., Rm(r)) = r



Note: The word loss in lossless refers to loss of information,
not to loss of tuples. In fact, for “loss of information” a better
term is “addition of spurious information”


Slide 11- 10

Decompositions (6)
Lossless (Non-additive) Join Property of a Decomposition
(cont.):

Algorithm 11.1: Testing for Lossless Join Property

Input: A universal relation R, a decomposition D = {R1, R2, ...,
Rm} of R, and a set F of functional dependencies.
1. Create an initial matrix S with one row i for each relation Ri in D, and
one column j for each attribute Aj in R.
2. Set S(i,j):=bij for all matrix entries. (* each bij is a distinct symbol
associated with indices (i,j) *).
3. For each row i representing relation schema Ri
{for each column j representing attribute Aj
{if (relation Ri includes attribute Aj) then set S(i,j):= aj;};};

(* each aj is a distinct symbol associated with index (j) *)

CONTINUED on NEXT SLIDE



Slide 11- 11

Decompositions (7)
Lossless (Non-additive) Join Property of a Decomposition (cont.):

Algorithm 11.1: Testing for Lossless Join Property
4. Repeat the following loop until a complete loop execution results in no changes to S
{for each functional dependency X Y in F
{for all rows in S which have the same symbols in the columns corresponding to
attributes in X
{make the symbols in each column that correspond to an attribute in Y
be the same in all these rows as follows:
If any of the rows has an “a” symbol for the column, set the
other rows to that same “a” symbol in the column.
If no “a” symbol exists for the attribute in any of the rows,
choose one of the “b” symbols that appear in one of the rows for the attribute and set
the other rows to that same “b” symbol in the column ;};
};
};
5. If a row is made up entirely of “a” symbols, then the decomposition has the lossless join
property; otherwise it does not.



Slide 11- 12

Properties of Relational Decompositions
(8)
Lossless (nonadditive) join test for n-ary decompositions.
(a) Case 1: Decomposition of EMP_PROJ into EMP_PROJ1 and
EMP_LOCS fails test.
(b) A decomposition of EMP_PROJ that has the lossless join property.


Slide 11- 13

Properties of Relational Decompositions (8)

Lossless (nonadditive) join
test for n-ary
decompositions.
(c) Case 2: Decomposition
of EMP_PROJ into EMP,
PROJECT, and
WORKS_ON satisfies test.


Slide 11- 14

Decompositions (9)


Testing Binary Decompositions for Lossless
Join Property




Binary Decomposition: Decomposition of a
relation R into two relations.
PROPERTY LJ1 (lossless join test for binary
decompositions): A decomposition D = {R1, R2}
of R has the lossless join property with respect to
a set of functional dependencies F on R if and only
if either




The f.d. ((R1 ∩ R2)  (R1- R2)) is in F+, or
The f.d. ((R1 ∩ R2)  (R2 - R1)) is in F+.


Slide 11- 15

3. Multivalued Dependencies and Fourth
Normal Form (1)
(a) The EMP relation with two MVDs: ENAME —>> PNAME and
ENAME —>> DNAME.
(b) Decomposing the EMP relation into two 4NF relations
EMP_PROJECTS and EMP_DEPENDENTS.


Slide 11- 16

3. Multivalued Dependencies and Fourth
Normal Form (1)
(c) The relation SUPPLY with no MVDs is in 4NF but not in 5NF if it has
the JD(R1, R2, R3). (d) Decomposing the relation SUPPLY into the
5NF relations R1, R2, and R3.


Slide 11- 17

Multivalued Dependencies and Fourth Normal
Form (2)
Definition:
A multivalued dependency (MVD) X —>> Y specified on relation
schema R, where X and Y are both subsets of R, specifies the
following constraint on any relation state r of R: If two tuples t1 and
t2 exist in r such that t1[X] = t2[X], then two tuples t3 and t4 should
also exist in r with the following properties, where we use Z to
denote (R – (X υ Y)):









t3[X] = t4[X] = t1[X] = t2[X].

t3[Y] = t1[Y] and t4[Y] = t2[Y].
t3[Z] = t2[Z] and t4[Z] = t1[Z].
An MVD X —>> Y in R is called a trivial MVD if (a) Y is a subset of
X, or (b) X υ Y = R.


Slide 11- 18

Form (3)
Inference
Rules
for
Multivalued Dependencies:

















Functional

and

IR1 (reflexive rule for FDs): If X  Y, then X –> Y.
IR2 (augmentation rule for FDs): {X –> Y}  XZ –> YZ.
IR3 (transitive rule for FDs): {X –> Y, Y –>Z}  X –> Z.
IR4 (complementation rule for MVDs): {X —>> Y}  X —>>
(R – (X  Y))}.
IR5 (augmentation rule for MVDs): If X —>> Y and W  Z
then WX —>> YZ.
IR6 (transitive rule for MVDs): {X —>> Y, Y —>> Z}  X —>>
(Z 2 Y).
IR7 (replication rule for FD to MVD): {X –> Y}  X —>> Y.
IR8 (coalescence rule for FDs and MVDs): If X —>> Y and
there exists W with the properties that

(a) W  Y is empty, (b) W –> Z, and (c) Y  Z, then X –> Z.

Slide 11- 19

Form (4)
Definition:

A relation schema R is in 4NF with respect to a set of
dependencies F (that includes functional dependencies
and multivalued dependencies) if, for every nontrivial
multivalued dependency X —>> Y in F+, X is a superkey
for R.


Note: F+ is the (complete) set of all dependencies
(functional or multivalued) that will hold in every relation
state r of R that satisfies F. It is also called the closure of
F.


Slide 11- 20

Form (5)
Decomposing a relation state of EMP that is not in 4NF:
(a) EMP relation with additional tuples.
(b) Two corresponding 4NF relations EMP_PROJECTS and
EMP_DEPENDENTS.


Slide 11- 21

Fifth Normal Form (5NF)






A table is in 5NF when it is in 4NF and there are
no cyclic dependencies.
Cyclic Dependency: occurs when there is a multifield primary key with three or more fields (ex. A,
B, C) and those fields are related in pairs AB, BC
and AC.
Can occur only with a multi-field primary key of
three or more fields


Slide 11- 22

Sample 5NF Violation


BUYING

*Buyer
Chris
Chris
Chris
Lori

*Product
Jeans
Jeans
Shirts
Jeans


*Company
Levi
Wrangler
Levi
Levi

Slide 11- 23

Do the math


Our sample is two buyers, two products and
two companies, so…
2 x 2 x 2 = 8 total records



But, what if our store has 20 buyers, 50
products and 100 companies?
20 x 50 x 100 = 100,000 total records


Slide 11- 24

Sample 5NF Violation


BUYERS
*Buyer

Chris

Jeans

Chris

Shirts

Lori


*Product

Jeans

PRODUCTS
*Product

*Company

Jeans

Wrangler

Jeans

Levi

Shirts

Levi


Slide 11- 25

The Correct Solution


Slide 11- 26

Check the Math, Again


If our company has 20 buyers, 50 products and
100 companies?
Buyers = 20 x 50 = 1000
Products = 50 x 100 = 5000
Companies = 20 x 100 = 2000
8,000 total records instead of 100,000!


Slide 11- 27

Other Dependencies and Normal Forms (4)
Domain-Key Normal Form (DKNF):








Definition:

A relation schema is said to be in DKNF if all constraints and
dependencies that should hold on the valid relation states can be
enforced simply by enforcing the domain constraints and key
constraints on the relation.
The idea is to specify (theoretically, at least) the ―ultimate normal
form‖ that takes into account all possible types of dependencies and
constraints. .
For a relation in DKNF, it becomes very straightforward to enforce all
database constraints by simply checking that each attribute value in a
tuple is of the appropriate domain and that every key constraint is
enforced.
The practical utility of DKNF is limited


Slide 11- 28

7 relational database design algorithms and further dependencies

More Related Content

What's hot (20)

Viewers also liked (10)

Similar to 7 relational database design algorithms and further dependencies (20)

More from Kumar (20)

Recently uploaded (20)

7 relational database design algorithms and further dependencies