This is not as complicated as it may sound.
Let’s look at this in more detail.
All this means that each attribute must hold a single atomic value.
In this relationship, A determines the value of B, while B depends on A.
Any other attributesin this case,EmployeeNameandDeptNamemust depend on the primary key to obtain its value.
This is called partial dependency.
For example, consider the table in the section above that adheres only to 1NF.
Here it is, again:
Tina has two records.
If we update one without realizing that there are two, the result would be inconsistent data.
We might be disallowed to even add a new employee if theLocationattribute does not allow NULL values.
Full dependency is not the whole picture, though, when it comes to normalization.
You must check that that your database is inThird Normal Form(3NF).