Normalization help

[chad101]

For my job history entity should I just store my placement number and remove the candidate number? Since placement number already determines the candidate number in the placement table.

 

[Greyowlsl]

Depends, could be usefull if you use forms later on.

 

[chad101]

thank you

True, but I am creating redundancy and I just don’t see the need of having a JOB_HISORY entity when history data is stored in the PLACEMENT entity. Unfortunately I am asked to create this history table which I cannot think of anything useful to store in it. I know sometimes rules have to be broken to increase query speed but PLACEMENT is adequate for any history information.

 

[Greyowlsl]

You could have the comp_name in there aswell...