1. Normalization is one of the important processes while designing databases.
Normalization is actually a technique for reviewing the database design and it includes a
set of mathematical rules.
Answer the following questions using specific examples:
1. Does normalization always lead to a good design? Why or why not?
2. What kind of issues, problems are possible in the normalization process?
1.
From the definition of normalization which is the process of efficiently organizing the
data in a database by eliminate redundant data and ensure data dependencies make
sense (only storing related data in a table). Both of these are valuable goals as they
reduce the amount of space a database consumes and ensure that data is logically
stored.
Yes! Normalization always leads to good and successful database design because it
structures the data to eliminates duplications, unnecessary information and provide
adequate search path for all necessary information. This will ensure that the tables, keys,
columns and relationships are well-defined and in order to have an efficient database.
So we should know that without normalization, a database system will be inefficient,
slow, wrong and will not produce adequate result as expected.
2.
Though normalization is a complex process with different intensity levels and specific
rules. When normalizing to design good, functional, efficient and successful database we
need to store data where it belongs uniquely and logically which involves few steps
and every step is called forms, on the normalization process there will be some few
issues and problems which are:
• The problem of joining more tables which can take long and is more tasking because
of the work involved. This will also make queries more complicated and the read time
slower.
• The exhibitions turn out to be very slow as the typical structure type advances.

2. • The indexing will not work efficiently because of requirement to join tables
• The data model becomes incredibly hard to queries as the information model is
advanced for applications.
• The table will contain codes as opposed to genuine information which will make the
work more cumbersome, complicated and the read time very slow.
Reference:
Normalization (n.d). Retrieved from
https://condor.depaul.edu/gandrus/240IT/accesspages/normalization3.htm
GeeksForGeeks: Advantages and Disadvantages of Normalisation (2021, November 12).
https://www.geeksforgeeks.org/advantages-and-disadvantages-of-normalization/