Normalisation Review

-each non-key attribute for an entity occurrence is only stored once in the database
-this minimises storage requirements
-data consistency is ensured
-an attribute for an entity occurrence wil only have one value, so there will only be one correct/current value for an attribute
-improved date integrity
-improved data independance

-you need to be careful with trying to make data atomic. Just because you can split some types of data further, it isn't always the correct thing to do
-you can end up with more tables than an unnormalised database
-the more tables and the more complex the database, the slower queries can be to run
-it is necessary to assign more relationships to interact with larger numbers of tables
-with more tables, setting up queries can become more complex