In the context of relational database normalization, which of the following statements is/are true?
Correct Answer :
It is always possible to obtain a dependency-preserving 3NF decomposition of a relation
It is always possible to obtain a dependency-preserving 1NF decomposition of a relation
It is not always possible to obtain a dependency-preserving BCNF decomposition of a relation
Solution :
The correct statements are:
1. It is always possible to obtain a dependency-preserving 3NF decomposition of a relation
2. It is always possible to obtain a dependency-preserving 1NF decomposition of a relation
3. It is not always possible to obtain a dependency-preserving BCNF decomposition of a relation
Let us analyze each statement step-by-step:
1. Dependency Preservation in 3NF (Third Normal Form):
For any relational schema and a set of functional dependencies , there is a standard algorithm (often called the 3NF Synthesis Algorithm) that guarantees a decomposition into schemas such that:
• Each is in 3NF.
• The decomposition is lossless-join.
• The decomposition preserves all functional dependencies in (i.e., the union of the projections of onto each is equivalent to ).
Thus, a dependency-preserving 3NF decomposition is always possible.
2. Dependency Preservation in 1NF (First Normal Form):
First Normal Form (1NF) only requires that the domain of each attribute contains only atomic values and that the value of each attribute in a tuple is a single value from its domain. It does not impose any restrictions on functional dependencies. Since a relation is already in 1NF or can trivially be decomposed/flattened into 1NF without losing any attributes or functional dependencies, obtaining a dependency-preserving 1NF decomposition is always possible.
3. Dependency Preservation in BCNF (Boyce-Codd Normal Form):
Boyce-Codd Normal Form is stricter than 3NF. It requires that for every non-trivial functional dependency , the determinant must be a superkey. Due to this strict requirement, we cannot always guarantee dependency preservation.
For example, consider the relation with functional dependencies:
Here, the candidate keys are and . The dependency violates BCNF because is not a superkey. If we decompose the relation to satisfy BCNF, we get and . However, in this decomposition, the functional dependency cannot be checked within any single decomposed relation without performing a join. Hence, the dependency is lost. This proves that it is not always possible to obtain a dependency-preserving BCNF decomposition.
Access expert-curated educational resources and study materials—completely free.
Create, conduct, and manage professional online assessments with Mindyard. Perfect for teachers and institutes.
Copyright © 2026 Mindyard. All Rights Reserved.