Normalization of a database

We use a database (or databases) to store a certain group of information of interest in an orderly and efficient. One of the features offered by a typical database allows the database to extract all and only the data that match a certain criteria, specified by the user.

For example, imagine a database to store master data to some gym-goers. Suppose then be interested to know the names and surnames of all the members who have not yet reached thirty years.

And 'possible to obtain this information through a simple database query, the query also more commonly known, precisely allowing the identification and visualization of the desired data.

So a database is a tool for grouping and managing information of all kinds through the use of tables, where data is placed in relation to each other. But how the information is grouped? By what standard are built the tables?

The more immediate solution may be the inclusion of all data of interest in a single table. This operation, however, helps to build a table with a number of rows (records) and columns (fields) very high in relation to the amount of data treated.

The problem caused by the use of a single table, moreover, is conceptual. The use of a single table does not disclose in a timely and clarifying what are the specific relationships that typically also involve one or more subsets of the data examined.

Instead of imagining the information is contained in multiple tables, it becomes necessary and not simply to ensure that there are no duplicate information, resulting in waste of memory and need for multiple update operations.

Just to provide guidelines for these choices, ensuring efficiency and completeness of the data structure, the so-called normal forms are defined in a database.
A structured database in normal form, in fact, easy and faster data operations by reducing the risk of redundancy and data inconsistency.

So let us try to understand what is meant by normal forms and normalization of databases.

• <<
• 1
• 2
• 3
• 4
• >>