Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Normalisation – A Technique to Design a Database System

DZone's Guide to

Normalisation – A Technique to Design a Database System

· Database Zone ·
Free Resource

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

The Normalisation is a data analysis technique to design a database system. The Normalisation allows the database designer to understand the current data structure within an organisation. The end result of a normalisation is a set of entity. We remove the unnecessary redudency by normalising the database table.

When we talk about normalise a database table practically there is a procedure to perform this. To normalise a table we need to proceed through various steps. These steps are called Normalisation Form. The Normalisation Form of NF are known as 1NF, 2NF, 3NF, 4NF, 5NF. Generally we follow the procedure upto 3NF as many of tables get normalised after 3NF. but sometimes we need to perform higher NF. Here are the steps to normalised a table:

Step 1: First we convert the data source into unnormalised form(UNF).
Step 2: Transform the unnormalised data into First normal form(1NF).
Step 3: Transform the 1NF into 2NF.
Step 4: Transform the 2NF to 3NF.

After 3NF if the data source is still in unmormalised form then we perform the following steps.

Step 5: Transform 3NF to Boyce-Code Normal Form(BCNF).
Step 6: Transform BCNF into 4NF.
Step 7: Transform 4NF to 5NF.

Normalisation is a bottom-up technique for database design, normally it is based on existing system.

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}