Are you interested to learn more about database normalisation? or not sure really what it’s about? Or chances are if you’ve worked with, or created your own database, you’ve performed database normalisation without even knowing it.
Well I found a great article on this topic and it’s definitely a keeper. Anyway the below is shamelessly ripped from their site, because they simply explain it no better than I would have liked to anyway:
If you’ve been working with databases for a while, chances are you’ve heard the term normalization. Perhaps someone’s asked you “Is that database normalized?” or “Is that in BCNF?” All too often, the reply is “Uh, yeah.” Normalization is often brushed aside as a luxury that only academics have time for. However, knowing the principles of normalization and applying them to your daily database design tasks really isn’t all that complicated and it could drastically improve the performance of your DBMS.
What is Normalisation?
Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table) and ensuring data dependencies make sense (only storing related data in a table). Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored.
If you would like to ensure your database is normalised, continue reading on the following articles:
- Database Normalization Basics
- Putting your Database in First Normal Form (1NF)
- Putting your Database in Second Normal Form (2NF)
- Putting your Database in Third Normal Form (3NF)
Post a Comment