I am looking to explore more about normalization in DBMS. I am confused
about some points. Can anyone tell me about these points? I have to google
it to read about all these points and I have found some blogs like this
normalization in DBMS <https://hackr.io/blog/dbms-normalization> but
still, I am not cleared some points
1. When is the process of normalization used?
2. Boyce and Codd Normal Form
3. 1NF, 2NF, and 3NF
Short answer. Duplicate data in a database is bad. Take school
departments. For each teacher, do you put "History", "Chemistry",
"Biology" for their department? What happens if someone enters "Bioolgy"
instead? So for your point #1, "as soon as duplicate data is possible".
Maybe not for surnames or firstnames, but certainly for address counties,
departments, car types, etc, etc. As soon as there is a definite list for
#2, #3. Wikipedia is your friend here.
On Wed, 2 Oct 2019 21:42:13 -0700 (MST)
shivambhatele <[hidden email]> wrote:
> 1. When is the process of normalization used?
> 2. Boyce and Codd Normal Form
> 3. 1NF, 2NF, and 3NF
Good information on database theory is remarkably scarce on the web,
and difficult for the beginner to distinguish from bad information on
database theory. And, actually, that's the case for almost any body of
knowledge. If you want to master a discipline, books are a better
I have tried referring people to wikipedia before. It's not
necessarily wrong; it's more a question of completeness and explication.
You just can't replace a book with a web page or pages.
An Introduction to Database Systems (8th Edition), 2003,
by C.J. Date
It's useful to understand normalization in the context of relational
algebra: by removing redundancy, you defend against anomalies that
would otherwise result from mathematically correct operations. So,
well, more than one chapter to read. :-)