You usually normalize a database to avoid data redundancy. It\'s easy to see in a table full of names that there is plenty of redundancy. If your goal is to create a catalog
You should normalize it out if you need to avoid the delete anomaly that comes with not breaking it out. That is, if you ever need to answer the question, has my database ever had a person named "Joejimbobjake" in it, you need to avoid the anomaly. Soft deletes is probably a much better way than having a comprehensive first name table (for example), but you get my point.