Prepare
Practice
Interview
Aptitude
Reasoning
English
GD
Placement papers
HR
Current affairs
Engineering
MCA
MBA
Online test
Login
3NF relational database design form is considered adequate - Database
Home
>>
Category
>>
Programming Language (MCQ) questions
>>
Database
Q. Which normal relational database design the form that is considered adequate?
- Published on 25 Aug 15
a.
3NF
b.
5NF
c.
2NF
d.
4NF
ANSWER: 3NF
Related Content
Networking (
207
)
Database (
97
)
C programming (
58
)
Software Engineering (
28
)
SQL (
5
)
HTML (
74
)
Web Technologies (
11
)
Data Structure (
140
)
Operating System (
96
)
Java (
25
)
Oracle (
5
)
C++ (
50
)
Algorithms (
7
)
PL/SQL (
13
)
JavaScript (
7
)
XML (
0
)
CSS (
1
)
Discussion
Nirja Shah
-Posted on 05 Nov 15
- A technique of organising data is known as database Normalisation.
- It is a systematic approach of decomposing tables to eliminate data redundancy and undesirable characteristics like Insertion, Update and Deletion Anamolies.
- There is a multi-step process followed that puts data into tabular form by removing duplicated data from the relation tables.
- It is mainly used for two purpose:
1. Eliminating the redundant(useless) data.
2. Ensuring data dependencies make sense i.e data is logically stored.
2NF
- In this form there must not be any partial dependency of any column on primary key.
- It means that for a table that has concatenated primary key, each column in the table that is not part of the primary key must depend upon the entire concatenated key for its existence.
- A table fails Second normal form when any column depends only on one part of the concatenated key.
3NF
- This form applies that every non-prime attribute of table must be dependent on primary key, or we can say that, there should not be the case that a non-prime attribute is determined by another non-prime attribute.
- The transitive functional dependency should be removed from the table and also the table must be in Second Normal form.
4NF
- This normal form is used in database normalization.
- It is the next level of normalization after Boyce–Codd normal form (BCNF).
- Whereas the second, third, and Boyce–Codd normal forms are concerned with functional dependencies, 4NF is concerned with a more general type of dependency known as a multivalued dependency.
- A Table is in 4NF if and only if, for every one of its non-trivial multivalued dependencies X \⇒ Y, X is a superkey—that is, X is either a candidate key or a superset thereof.
5NF
- Fifth normal form (5NF), also known as project-join normal form (PJ/NF) is a level of database normalization designed to reduce redundancy in relational databases recording multi-valued facts by isolating semantically related multiple relationships.
- A table is said to be in the 5NF if and only if every non-trivial join dependency in it is implied by the candidate keys.
- A join dependency *{A, B, … Z} on R is implied by the candidate key(s) of R if and only if each of A, B, …, Z is a superkey for R.
- The fifth normal form was first described by Ronald Fagin in his 1979 conference paper Normal forms and relational database operators.
➨
Post your comment / Share knowledge
Required!
Required!
Invalid Email Id!
Required!
Enter the code shown above:
Please enter the code shown above
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)
MCQs
English
Tutorials
Download
▲