Second Normal Form
The second normal form is goal when every data item in a record which is not dependent on the primary key of the record should be erased and used to form a separate relation.
The PF department ensures which only one employee in the state is assigned a specific PF number. This is known as a one-to-one relation. The PF number uniquely recognized a specific employee; an employee is related with one and only one PF number. Therefore, if you know the Employee no., you can conclude the PF number. This is functional dependency. Thus a data item is functionally dependant if its value is uniquely related with a specific data item.
Second Normal Form – Employee Record
![1854_Second Normal Form.png](https://www.expertsmind.com/../CMSImages/1854_Second Normal Form.png)
Annual Salary Earned Record
![1235_Second Normal Form 1.png](https://www.expertsmind.com/../CMSImages/1235_Second Normal Form 1.png)
Bank Record
![1916_Second Normal Form 2.png](https://www.expertsmind.com/../CMSImages/1916_Second Normal Form 2.png)
The three record structures which are established are:
1.Employee record consisting of: Employee no., employee name employee details (grade, department code, exit code date of joining, and exit date), bank details (bank name, bank code, employees A/C no. address)
2. Annual salary earned record consisting of – employee no., month & year (MMYY) and net paid
3.Bank record consisting of: bank name, bank code and bank address. All the attributes of this relation are fully dependent on Bank code.
A table in Second Normal Form must denote which all the attributes, that are not dependent of primary key, must be removed. The table which is given below in Second Normal Form will be
Invoice_Master Invoice_Item Item_Master
Invoice_code Invoice_No Item_code
Inv_date item_code description
Order_code rate
Cust_code ord_qty
Cust_name Ord_value
Address
Invoice_value
There are no modifications in the Invoice details.