LutzM (12/30/2010)
I strongly recommend to normalize your tables. The sooner the better. Normalization is the key for flexibility, I'd say.
Building on Lutz's comment I'll say you cannot pull a database design out of a hat - proper data modeling is the foundation of a sound database design.
Do things the right way, start with an ER Model that truthfully represents business reality and needs then move into a logical model and normalize to the 3NF - Once validated then build your tables.
Notes:
ER Model - Entity/Relationship Model
3NF - Third Normal Form
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.