Second Normal Form Table Normalization
Definition Examples and Recommendations
Second Normal Form (2NF) Definition
Since 2000 we have developed nearly 500 databases for clients throughout the world. See a sample of them at our recent clients page.
We also offer Microsoft SQL Server / Azure / Cloud database development through our programmer partnership with Jay McCormick and his team.
Second Normal Form (2NF) only comes into play when the primary key of the table is comprised of two or more fields and each of these fields is not a candidate to be a primary key of the table.
Below is our table from First normal form.
To remove the partial dependencies we move Emp_Hire_Date to the Employee table and move Project_Manager to the Project table. These fields have partial dependencies because they are not dependent on both fields that comprise the primary key.
Now our second normal form table looks like this:
The two fields, together, create a unique record and are therefore the primary key of the table.
There are a few problems with this table, however. First, if we delete a project we lose employee names unless they are a member of another project. If the employee gets married and changes their last name then every occurrence of the person's name will need to be updated. Similarly, if someone decides to make a slight change to the project name then many records may have to be updated. See how we prevent multiple updates with our table design rules.
As noted above the second normal form is a special case that is designed to deal with tables that have composite primary keys. Follow this discussion with 3rd normal form examples.
Copyright 2000-2017 Blue Claw Database Design
Microsoft Access 2007, Access 2010, MS Access 2013