Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Gerald30
Yak Posting Veteran
62 Posts |
Posted - 2012-05-31 : 21:38:51
|
| Hello.I need some advise please help me.I have a table which contains the records of Damage receive of an item per process.The table contains the following information.Control No, Type of Damage, Damage PCS, Inserted Date.Lets say if I have 3 process, I will also have 3 tables for each of them.Now I`m thinking of consolidating these 3 table into one.Would it be ok?I was worried that the consolidated table will get really big that may be a burden on the database when it comes to querying.The consolidated Table will have this information.Control No, Process Name, Type Of Damage, Damage Pcs, Inserted Date.Please help.Thank you. |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-05-31 : 21:52:47
|
| its ok as i dont think damage received will grow so large.Only problem with table design is it looks a a bit denormaisedWhy cant you maintain process, damagetype etc details in separate table so that you dont have to repeat their values for each damage registered against them? You could have separate master entry tables for damagetype,process etc and used their ids as reference in your above tableie basically apply some level of normalisation------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
 |
|
|
|
|
|