May 5, 2010 at 10:03 pm
Hi
I am new to data base and having problem in normalizing
The problem: I have a entity category table in hospital database which has entities like doctors,suppliers,patient,staff etc: each entity consists of variable no of tables,some tables like address,phone are common to many or all and some are entity specific how do i proceed as i want to make address,phone table only once and attach them with entity with other entity specefic tables to get the full picture of entity.
EG:
Doctors linked to address table,phone table,fee table,
Staff linked to:address,phone,salary,duty roster
Supplier linked to address, phone, products etc
May 5, 2010 at 11:49 pm
This was removed by the editor as SPAM
May 7, 2010 at 2:52 am
would like to point out few things ,i am asking this as i want to break down contacts etc to related tables as there can be more than one phone no or more than one type of address ,emails so i want to break them down to their own tables,but relating them to each entry will lead to many similer tables like suppliers phone,doctors phone etc.
Futher it will be great help if you could point me to some refrence material on stuff tables
May 7, 2010 at 6:31 am
This was removed by the editor as SPAM
May 7, 2010 at 7:11 am
misc 53111 (5/7/2010)
would like to point out few things ,i am asking this as i want to break down contacts etc to related tables as there can be more than one phone no or more than one type of address ,emails so i want to break them down to their own tables,but relating them to each entry will lead to many similer tables like suppliers phone,doctors phone etc.Futher it will be great help if you could point me to some refrence material on stuff tables
In an OLTP system there is just one thing worst than lack of normalization which is excess of normalization.
Before modeling "phone", "address" and "email" tables please look at pros and cons - sometimes a great theoretical idea bumps heads on with reality.
_____________________________________
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.Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply