Normalization and de-normalization

Normalization It is the process of organizing data into related table. To normalize database, we divide database into tables and establish relationships between the tables. It reduces redundancy. It is done to improve performance of query. Steps of normalization: 1 NF Entities of the table must have unique identifier or entity key. 2 NF All the attributes of the table must depend on the entity key for that entity. 3NF All attributes that are not part of the key must not depend on any other non-key attributes. De-normalization The process of adding redundant data to get rid of complex join, in order to optimize database performance. This is done to speed up database access by moving from higher to lower form of normalization. Below is illustration of Normalization using some examples Rules for First Normal Form (1NF) Eliminate repeating groups. This table contains repeating groups of data in the Software column.

Computer 1 2 3

Software Word Access, Word, Excel Word, Excel

To follow the First Normal Form, we store one type of software for each record.

Computer 1 2 2 2 3 3 Rules for second Normal Form (2NF)

Software Word Access Word Excel Word Excel

Eliminate redundant data plus 1NF. This table contains the name of the software which is redundant data.

Computer 1 2 2 2 3 3

Software Word Access Word Excel Word Excel

To eliminate the redundant storage of data, we create two tables. The first table stores a reference SoftwareID to our new table that has a unique list of software titles. Computer SoftwareID 1 1 2 2 2 1 2 3 3 1 3 3 SoftwareID Software 1 Word 2 Access 3 Excel Rules for Third Normal Form (3NF)

Eliminate columns not dependent on key plus 1NF and 2NF. In this table, we have data that contains both data about the computer and the user. Computer User Name User Hire Date Purchased 1 Joe 4/1/2000 5/1/2003 2 Mike 9/5/2003 6/15/2004 To eliminate columns not dependent on the key, we would create the following tables. Now the data stored in the computer table is only related to the computer, and the data stored in the user table is only related to the user. Computer Purchased 1 5/1/2003 2 6/15/2004 User User Name User Hire Date 1 Joe 5/1/2003 2 Mike 6/15/2004 Computer User 1 1 2 1

Advantages of normalization
1. Smaller database: By eliminating duplicate data, you will be able to reduce the overall size of the database. 2. Better performance: a. Narrow tables: Having more fine-tuned tables allows your tables to have less columns and allows you to fit more records per data page. b. Fewer indexes per table mean faster maintenance tasks such as index rebuilds. c. Only join tables that you need.

Disadvantages of normalization
1. More tables to join: By spreading out your data into more tables, you increase the need to join tables. 2. Tables contain codes instead of real data: Repeated data is stored as codes rather than meaningful data. Therefore, there is always a need to go to the lookup table for the value.

3. Data model is difficult to query against: The data model is optimized for applications, not for ad hoc querying.