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 |
|
royvagner
Starting Member
1 Post |
 Posted - 2009-01-08 : 13:35:54
|
| I have a table with 60 columns (most of the columns are int)what is better for performance?Leave the table like that or divide it for 2 or 3 tables? |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2009-01-09 : 08:42:32
|
| whats are columns for? can you explain purpose for 60 columns |
 |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-09 : 12:29:25
|
| Read about Normalization. |
|
|
|
ckim472
Starting Member
4 Posts |
Posted - 2009-02-05 : 14:48:03
|
| It also depends on how many rows you have.Star schema could be another option other than normalization depending on your purpose. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-02-07 : 20:31:22
|
quote:
what is better for performance?
Well in OLTP Environment, You should consider Normalization(upto 3rd form) to make it better. In OLAP environment,Dimension tables are denormalized (Star Schema)to make it better. If you are breaking dimension tables apart then you are going for Snow-Flaked Schema which can better or worse depending on your requirement. |
|
|
|
|
|
|
Table with 60 columns