Database - Database Design Using Normalization - Discussion

Discussion :: Database Design Using Normalization - General Questions (Q.No.1)

1. 

Needing to using more complicated SQL in database applications is a(n) ________ of normalization.

[A]. advantage
[B]. disadvantage
[C]. either an advantage or disadvantage
[D]. neither an advantage nor disadvantage

Answer: Option B

Explanation:

No answer description available for this question.

Sunny said: (Jul 22, 2011)  
please anyone can tell me why it so?

Pranav Gupta said: (May 14, 2012)  
As soon as we reduce the redundancy by higher normalization, it also increase the complications.

Dileep Jaiswal said: (Sep 21, 2012)  
Complication decrease efficiency of the access data from the database.

Sheetal said: (Oct 13, 2012)  
Normalization means reducing redundancy that means only 1 entry for search data. And until that particular table is not find our search does not get completed.

Gsvm said: (Aug 9, 2013)  
Because as we normalize a database, the INSERT, UPDATE & DELETE query is efficient to use and help in improving performance but performance becomes very low in large database when using SELECT query to retrieve data from a DB.

Priti Tiwari said: (Sep 26, 2013)  
Removing complexity means doing normalization. So complexity is only disadvantage and complexity is not required in database operations.

Ranjeet said: (Jun 7, 2014)  
When you normalize any table it is divided into one or more table to full fill the requirement of different normalization form and when you need to fetch data you have to perform joins between these tables because the columns now are at different tables.

In denormalize you just need to execute select query no joins.

Omkar said: (Jul 17, 2019)  
Please tell me in short about the normalization and dependecy and consistency in mysql.

Post your comments here:

Name *:

Email   : (optional)

» Your comments will be displayed only after manual approval.