Google manages its ongoing invoices and payments using the following database table. Does it confirm to the second normal form? Why or Why not? If it is not in 2NF, normalize it into the 2NF tables. PaymentID Pay_Amount InvoiceNo DueDate AmountDue Late HD590 500.90 9100 1/1/2009 600.00 Y HD590 500.90 9500 1/5/2009 150.00 N IV111 90.00 9100 1/1/2009 600.00 N HR200 89.12 8081 1/9/2009 100.00 N
Google manages its ongoing invoices and payments using the following
|
PaymentID |
Pay_Amount |
InvoiceNo |
DueDate |
AmountDue |
Late |
|
HD590 |
500.90 |
9100 |
1/1/2009 |
600.00 |
Y |
|
HD590 |
500.90 |
9500 |
1/5/2009 |
150.00 |
N |
|
IV111 |
90.00 |
9100 |
1/1/2009 |
600.00 |
N |
|
HR200 |
89.12 |
8081 |
1/9/2009 |
100.00 |
N |
Step 1:-
Given:-
|
PaymentID |
Pay_Amount |
InvoiceNo |
DueDate |
AmountDue |
Late |
|
HD590 |
500.9 |
9100 |
1/1/2009 |
600 |
Y |
|
HD590 |
500.9 |
9500 |
1/5/2009 |
150 |
N |
|
IV111 |
90 |
9100 |
1/1/2009 |
600 |
N |
|
HR200 |
89.12 |
8081 |
1/9/2009 |
100 |
N |
2NF stands for 2 normal forms. This comes under normalization.1NF contains an atomic value or a single value in the table.
2NF is in 1NF and no partial dependency. Partial dependency is defined as a non-prime attribute that is functionally dependent on the subset of the candidate key.
Normalization is defined as a process to reduce the data redundancy in the table and make the consistency in the table. Data redundancy means duplication values.
Step by step
Solved in 2 steps
