Normalization is used to remove redundant data from the database and to store non-redundant and consistent data into it. Denormalization is used to combine multiple table data into one so that it can be queried quickly.
When should you not use normalization?
Some Good Reasons Not to Normalize
- Joins are expensive. Normalizing your database often involves creating lots of tables. ...
- Normalized design is difficult. ...
- Quick and dirty should be quick and dirty. ...
- If you're using a NoSQL database, traditional normalization is not desirable.
What are the reasons for de normalizing the data?
Denormalization is a strategy used on a previously-normalized database to increase performance. The idea behind it is to add redundant data where we think it will help us the most. We can use extra attributes in an existing table, add new tables, or even create instances of existing tables.
