Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 19, 2011 08:56 AM by himalaya.garg
Dec 15, 2011 08:12 AM|LINK
Please take a look at
I little hesistate starting new project untill i get assured about SQL database design.
Now I am going to start a new project. Please somebody suggest any changes in DB design or possibility of normalization that I left.
Project Scenario is:
Requestor submits the request to the chemical analysts for doing tests on sample.
1. He selects the project under which new request to make.
2. Gives number of samples in this project and no. of tests.
3. Samples have properties. He fill value of each property value for each sample.
4. He gives name of tests.
5. Select which sample is going for which test, in which lab(s) and what method reference to use for the test.
6.Finally filling the results for each sample test by each lab for each method reference.
Dec 19, 2011 06:16 AM|LINK
Seems ok and normalised and have correct design for parent-chile relationships.
Further normalization is also depends on your functional requirement. For Ex. Support you want to have requirement which shows project wise samples data or tasks, its better to have that parent column into child table (reduce normalization) .So that you
do not require to join multiple tables to fetch the data and will provide you better performance.
But as per as Normalization concern the DB seems in perfect shape.
Dec 19, 2011 06:27 AM|LINK
Dec 19, 2011 07:41 AM|LINK
What about dharnendra's idea？I still canot see your images……。
Dec 19, 2011 08:56 AM|LINK
Here is the link:
Now I am sticking to it. Hope for the Best..