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 some data. #2, #3. Wikipedia is your friend here.
On Thu, Oct 3, 2019 at 2:47 PM shivambhatele <shivambhatel...@gmail.com> wrote: > Hello All, > > 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 > > > > > > -- > Sent from: http://sqlite.1065341.n5.nabble.com/ > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
