Normalizing a large table
Posted on 2009-05-20
Although I understand normalization, I have a large table that I am having a tough time wrapping my mind around on how to split up.
This is a membership database for an association of doctors which contains over 50 tables already. Currently the Member table is linked to the OfficeInfo table via the MemID field, as one doctor may have several Offices. There is a combination Primary Key of MemID and OfficeType fields on the OfficeInfo table. The OfficeInfo table has over 100 fields and tracks office contact information, days of operation, hours of operation, languages spoken, procedures preformed, insurance providers taken, special needs, as well as other topics related to an office. Every time I try to break this table down into smaller tables, I just end up with several tables that have a one-one relationship. Is there something that I am not seeing? If the only way to normalize this table is to create several one-one related tables, would I be better off just leaving this a one large table?
I have attached a list of fields for the OfficeInfo table if this will help. I hope someone can get me pointed in the right direction on this one.