Why is database normalization necessary

Share on facebook
Share on twitter
Share on linkedin
Share on telegram
Share on whatsapp


The database normalization is a technique commonly used to organize the contents of transactional database tables and data stores. The application of this measure should not be considered optional, but rather like a necessary step to ensure a successful database design.


Photo credits: istock cybrain

The consequences of the lack of database normalization son:

  • Inaccuracy of database systems.

  • Slowing down processes.

  • Inefficiency in operations.

The database normalization helps to avoid these negative effects already from the design of new databases and It also allows you to check if the existing ones guarantee the necessary data or referential integrity. It is best to proceed to normalize the data before creating the database tables, even though it is always preferable to guarantee its integrity and, even if the databases already exist and are not newly created, use these techniques to put them to the test, be clear about the objectives to be achieved in the procedure.

Objectives of database normalization

When proceeding with database normalization, must be determined 4 objectives:

  1. Organize data into logical groups, in such a way that each group describes a small part of the whole.
  2. Minimize the amount of duplicate data stored in a database.
  3. Perfect the organization of data in a way that, When modifications are required, the change should only be applied in one place.
  4. Create a database that can be accessed quickly and where it is feasible to manipulate the data with maximum efficiency and without compromising its integrity.

Database normalization is especially important in the transactional processing environment., especially where it takes place online. This is due to the agility with which data modifications are carried out, that, at the same time, they usually occur randomly.. Inserts, deletions or updates impact the stored data and can reduce the performance of the database if it has not been normalized.

Despite this, before you can start normalizing a database, it is It is necessary to carry out a requirements analysis, which will be useful to establish the policies and procedures to be applied. This research will result in a compendium of Business rules.

These rules must be obtained by consensus Y, this agreement between the database users, both in terms of the use of the different items in each table, as in terms of your definitions, is essential to achieve the objectives of the database normalization. Schemas or methodologies can be used to reach consensus, that facilitate the transition through the requirements stage, database analysis and schema.. The important thing is that the rules are clear and that the meaning of each term and how to use it is confirmed before starting to standardize..

(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = “//connect.facebook.net/es_ES/all.js#xfbml=1&status=0”;
fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, 'facebook-jssdk'));

Subscribe to our Newsletter

We will not send you SPAM mail. We hate it as much as you.