What stage of normalization is this? (moving repeating data into separate table)

Posted by Sergio on Stack Overflow See other posts from Stack Overflow or by Sergio
Published on 2010-04-12T10:56:29Z Indexed on 2010/04/12 11:43 UTC
Read the original article Hit count: 338

Filed under:
|

Hi There,

I have noticed that when designing a database I tend to shift any repeating sets of data into a separate table. For example, say I had a table of people, with each person living in a state. I would then move these repeating states into a separate table and reference them with foreign keys.

However, what if I was not storing any more data about states. I would then have a table with StateID and State in. Is this action correct? State is dependant on the primary key of the users table, so does shifting it into its own table help with anything?

Thanks,

© Stack Overflow or respective owner

Related posts about normalization

Related posts about database