5 ms·
If choose to organize your data using a relational model and then choose not to normalize that relational design you're doing it wrong. Some of the benefits yo
by jussij 5y ago
If choose to organize your data using a relational model and then choose not to normalize that relational design you're doing it wrong.
Some of the benefits you get by doing proper normalized include:
* Avoids repetitive entries and duplicate data.
* Helps reduce the storage space required.
* Prevents the restructuring of the database to accommodate new requirements.
* Prevents the need for coding changes to accommodate new requirements.
* Increases the speed and flexibility of queries.
With a poorly normalized relational design you are throwing away the essence of the 'relational' model and
that 'relational' concept is right there in the name, RDMS.
- gregjor 5y agoNormalizing allows enforcing referential integrity and reduces/eliminates update anomalies. Those seem like theoretical concerns until your data gets corrupted.
- jussij 5y agoSurely since you agree normalization helps to 'reduces/eliminates update anomalies' then that also means it's going to reduce the chance of data corruption? Also what type of software design and development is not based on theoretical concerns? Software developers spend years studying theory in the hope they can use that knowledge in their own designs. Now I don't disagree normalization is a 'theoretical exercise' but it is also a helpful tool/technique that will make your life easier.
- gregjor 5y agoI think you misunderstood my comment. I have heard developers dismiss normalization as a theoretical concern. It’s not. Normalizing prevents update anomalies, for one thing. That’s not the same as “data corruption.” In my experience most software developers don’t spend years studying theory. They spend hours studying buzzwords and fads.