Should I create a separte table for this?

Trying to adhere to the normalization rule in cleaning up and re-design this database.  If I have a history table that has a history_Type column that currently stores varchar of the type.  Should I create a new table as History_Type with HistoryTypeId primary key as identity column and the a 2nd column as Type_Name as varchar.  Then change the History table to hold the HistoryTypeId  instead?  Thanks.
lapuccaAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Ephraim WangoyaConnect With a Mentor Commented:

Correct
0
 
Ephraim WangoyaCommented:

You are exactly correct.
That will be the best way to go about it.
0
 
lapuccaAuthor Commented:
So, by implementing it this way, is this conforming to NF2?  thanks.
0
 
Paul JacksonConnect With a Mentor Software EngineerCommented:
The reason why this would probably be a good idea is if you wanted to retrieve items from the history table based on the historytypeid as it will improve performance.
As for normilization rules moving this in to a separate table conforms with 2NF mormalization rule : Remove subsets of data that apply to multiple rows of a table and place them in separate tables.

0
 
lapuccaAuthor Commented:
Thank you both.  Jacko, thank you for the detail infro.  Since ew has answered both my questions hence I'm spliting up the points this way.  But I appreciate both your help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.