and then one likeAccounting
. These are obviously the same department, but casing is changed. If you are not sure, and there is the possibility of data redundancy, go with the departmentID PK/FK.accounting
An egg is a chicken's house!
What I am wondering is, is it better to store the actual department name in the employee_table or should I store an ID from the department_table as a foreign key?
Blake Minghelli<br />SCWCD<br /> <br />"I'd put a quote here but I'm a non-conformist"
An egg is a chicken's house!
You normalize a database in order to ensure data consistency and stability, to minimize data redundancy, and to ensure consistent updatability and maintainability of the data, and avoid update and delete anomalies that result in ambiguous data or inconsistent results.
[OCP 17 book] | [OCP 11 book] | [OCA 8 book] [OCP 8 book] [Practice tests book] [Blog] [JavaRanch FAQ] [How To Ask Questions] [Book Promos]
Other Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, TOGAF part 1 and part 2
Don't get me started about those stupid light bulbs. |