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 |
|
John Sourcer
Yak Posting Veteran
91 Posts |
 Posted - 2008-01-16 : 01:43:47
|
| OK, I asked a dumb question yesterday and hope I am not again.I have a table of many objects and need a related table with properties. The properties could grow. Which approach is better?a)A lookup table listing the properties for each object as some objects may not have propertiesb)A matrixed table with fixed columns for each property |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-01-16 : 01:46:00
|
quote:
Originally posted by John Sourcer
OK, I asked a dumb question yesterday and hope I am not again.I have a table of many objects and need a related table with properties. The properties could grow. Which approach is better?a)A lookup table listing the properties for each object as some objects may not have propertiesb)A matrixed table with fixed columns for each property
I think first approach is better as when your properties keep on growing you may add new record to properties table linking to main table record rather than add new column to matrix table each time. |
 |
|
|
John Sourcer
Yak Posting Veteran
91 Posts |
Posted - 2008-01-16 : 01:51:39
|
| I thought so! Thanks for your advice visakh16! |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-01-16 : 02:21:54
|
http://www.datamodel.org/NormalizationRules.html
E 12°55'05.25"N 56°04'39.16" |
|
|
|
|
|
|
Matrix vs Lookup