Need Insights on DB Design

khwaja

Registered User.
Local time
Today, 19:45
Joined
Jun 13, 2003
Messages
254
I have a DB that that is being successfully used but I am ware that the sheer number of fields and the nature of info contained therein, my table needs normalising. I read on normalisation and tried to relate as much as I could but in some cases, you are simply lost because you don't want to create myriad of table just to have a normalised DB. I will give you a couple of examples if anyone can advise if these need to be sitting in another table.

I have a stores table which has a one to many relationship with projects table. This 'many' table has a large number of fields which are relevant to projects undertaken. I have removed a lot of fields from this table, eg, bunch of resources (eg PM, engineers). Now I am left with a lot of dates. These could be project opening closing date, approval date, and so on.

Do you think these dates should be in a seperate table? I know these dates are inevitably associated with projects but can't establish if these do need to be sitting outside of projects table . Similarly, I have a number of cost elements which are currently part of the table. Just because these are different type of costs, does it mean these have to to in another table. I have attched an excel file of fields for your revirew. I have highlighted the ones I have removed. Will appreciate some help.
 

Attachments

Users who are viewing this thread

Back
Top Bottom