Normalisation is one of the learning points that I were really excited about. To begin with a little story; as previous mentioned I have worked with databases on a “maintenance” and lighter level for many years. And when I were called in for an interview with a company that needed a new technician – working with databases were part of the tasks they wanted done. Now, normalisation is not something you ever never have to do when working in a Joomla environment – or I might say, its very rare. So when asked if I could do that, and I said no that has never been needed, I of course did not land the job. Ever since, I have wanted to learn more about normalisation.

So the days has finally arrived, and I can now – after following the lecture and reading the additional material – learned the uses of normalisation. Although it is not “needed” if you are that kind of programmer that does everything superbly correct right away – it is something that should be done every time to make sure the database is normalised.

So what is it? Well, it is a process of five steps (but only takes three):

  1. Starting point – Un-normalised data
  2. First normal form (1NF) – Table format. Primary key is identified. All data items are “atomic”.
  3. Second normal form (2NF) – No partial dependencies!
  4. Third normal form (3NF) – No transitive dependencies!
  5. Ending point – Normalised data