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 |
|
X-Factor
Constraint Violating Yak Guru
392 Posts |
 Posted - 2007-03-27 : 18:54:34
|
| Hi, I have a table of themes where each row stores the values for CSS attributes.So far there are 18 values which makes a total of 21 columns.Now, given that every theme has a value for each CSS value, I figure that the table is completely normalized.So is there anything wrong with this?Personally, I think its much easier to manage and program one table with lots of columns rather than several linked tables.Cheers, XF |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-03-27 : 19:39:00
|
if a theme is made up of that many attributes, i see nothing wrong with a column for each.The reason to use separate tables would be if you were very often duplicating data between the themes, or if the themes are somehow related to one another, like if a theme was made up from subelements. If that's the case you could consider having different tables for each subelement, and a theme would just be a collection of subelements.
www.elsasoft.org |
 |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
|
|
|
What's wrong with a lot of columns?