Scribd
Upload
52 views

Normalisation Database

The document discusses the three rules of first normal form (1NF) for database organization: 1) Define data items and columns, 2) Ensure no repeating groups of data, and 3) Ensure each table has a primary key. It provides examples of how to transform an unnormalized table into 1NF by splitting it into separate tables for atomic values and removing repeating groups.

Uploaded by

Shane Orija
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
52 views

Normalisation Database

The document discusses the three rules of first normal form (1NF) for database organization: 1) Define data items and columns, 2) Ensure no repeating groups of data, and 3) Ensure each table has a primary key. It provides examples of how to transform an unnormalized table into 1NF by splitting it into separate tables for atomic values and removing repeating groups.

Uploaded by

Shane Orija
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

First normal form (1NF) sets the very basic rules for an organized database:

 Define the data items required, because they become the columns in a table. Place related
data items in a table.

 Ensure that there are no repeating groups of data.

 Ensure that there is a primary key.

First Rule of 1NF:

You must define the data items. This means looking at the data to be stored, organizing the data into
columns, defining what type of data each column contains, and finally putting related columns into
their own table.

For example, you put all the columns relating to locations of meetings in the Location table, those
relating to members in the MemberDetails table, and so on.

Second Rule of 1NF:

The next step is ensuring that there are no repeating groups of data. Consider we have the following
table:

CREATE TABLE CUSTOMERS(

ID INT NOT NULL,

NAME VARCHAR (20) NOT NULL,

AGE INT NOT NULL,

ADDRESS CHAR (25),

ORDERS VARCHAR(155)

);

So if we populate this table for a single customer having multiple orders, then it would be something
as follows:

ID NAME AGE ADDRESS ORDERS

100 Sachin 36 Lower West Side Cannon XL-200

100 Sachin 36 Lower West Side Battery XL-200

100 Sachin 36 Lower West Side Tripod Large

But as per 1NF, we need to ensure that there are no repeating groups of data. So let us break above
table into two parts and join them using a key as follows:

CUSTOMERS table:
CREATE TABLE CUSTOMERS(

ID INT NOT NULL,

NAME VARCHAR (20) NOT NULL,

AGE INT NOT NULL,

ADDRESS CHAR (25),

PRIMARY KEY (ID)

);

This table would have the following record:

ID NAME AGE ADDRESS

100 Sachin 36 Lower West Side

ORDERS table:

CREATE TABLE ORDERS(

ID INT NOT NULL,

CUSTOMER_ID INT NOT NULL,

ORDERS VARCHAR(155),

PRIMARY KEY (ID)

);

This table would have the following records:

ID CUSTOMER_ID ORDERS

10 100 Cannon XL-200

11 100 Battery XL-200

12 100 Tripod Large

Third Rule of 1NF:

The final rule of the first normal form, create a primary key for each table which we have already
created.
1st Normal Form Definition

A database is in first normal form if it satisfies the following conditions:

 Contains only atomic values

 There are no repeating groups

An atomic value is a value that cannot be divided. For example, in the table shown below, the values
in the [Color] column in the first row can be divided into "red" and "green", hence
[TABLE_PRODUCT] is not in 1NF.

A repeating group means that a table contains two or more columns that are closely related. For
example, a table that records data on a book and its author(s) with the following columns: [Book ID],
[Author 1], [Author 2], [Author 3] is not in 1NF because [Author 1], [Author 2], and [Author 3] are all
repeating the same attribute.

1st Normal Form Example

How do we bring an unnormalized table into first normal form? Consider the following example:

This table is not in first normal form because the [Color] column can contain multiple values. For
example, the first row includes values "red" and "green."

To bring this table to first normal form, we split the table into two tables and now we have the
resulting tables:
2nd Normal Form Definition

A database is in second normal form if it satisfies the following conditions:

 It is in first normal form

 All non-key attributes are fully functional dependent on the primary key

In a table, if attribute B is functionally dependent on A, but is not functionally dependent on a proper


subset of A, then B is considered fully functional dependent on A. Hence, in a 2NF table, all non-key
attributes cannot be dependent on a subset of the primary key. Note that if the primary key is not a
composite key, all non-key attributes are always fully functional dependent on the primary key. A
table that is in 1st normal form and contains only a single key as the primary key is automatically in
2nd normal form.

2nd Normal Form Example

Consider the following example:

This table has a composite primary key [Customer ID, Store ID]. The non-key attribute is [Purchase
Location]. In this case, [Purchase Location] only depends on [Store ID], which is only part of the
primary key. Therefore, this table does not satisfy second normal form.

To bring this table to second normal form, we break the table into two tables, and now we have the
following:
What we have done is to remove the partial functional dependency that we initially had. Now, in the
table [TABLE_STORE], the column [Purchase Location] is fully dependent on the primary key of that
table, which is [Store ID].

3rd Normal Form Definition

A database is in third normal form if it satisfies the following conditions:

 It is in second normal form

 There is no transitive functional dependency

By transitive functional dependency, we mean we have the following relationships in the table: A is
functionally dependent on B, and B is functionally dependent on C. In this case, C is transitively
dependent on A via B.

3rd Normal Form Example

Consider the following example:

In the table able, [Book ID] determines [Genre ID], and [Genre ID] determines [Genre Type].
Therefore, [Book ID] determines [Genre Type] via [Genre ID] and we have transitive functional
dependency, and this structure does not satisfy third normal form.

To bring this table to third normal form, we split the table into two as follows:
Now all non-key attributes are fully functional dependent only on the primary key. In [TABLE_BOOK],
both [Genre ID] and [Price] are only dependent on [Book ID]. In [TABLE_GENRE], [Genre Type] is only
dependent on [Genre ID].

You might also like