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 |
|
rmi
Starting Member
6 Posts |
 Posted - 2011-02-22 : 04:48:15
|
| Just out of curiosity:If I have for example table products which have 50 columns, should I divide it into multiple tables like product_prices, product_measures, product_spesification and so?If one record has only one distinct value for each column is there any reason to divide table in multiple tables?I know the benefit when having multiple tables is that there can be multiple values for same product but if it's not necessary.//rmi |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2011-02-22 : 05:32:12
|
I can see no reason to split your data in multiple tables as long as you would get always a 1:1 relationship.
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
|
|
|
How many columns is 'good'