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 |
|
ahmeds08
Aged Yak Warrior
737 Posts |
 Posted - 2010-11-25 : 08:13:56
|
| hello everybody,i was given a document to prepare the table structure in sql server for a hospital domin project.when the table was created there were 92 columns in it.could any body suggest me wether is it a good practice to create a table with so many columns.will it have any performance issues. |
|
|
nigelrivett
Master Smack Fu Yak Hacker
3385 Posts |
Posted - 2010-11-25 : 08:23:53
|
| non-clustered indexes can partition the table vertically.Depends on how many rows there are as to whether it will be an issue.I would guess that columns could be split into volatile and non-volatile tables to save page splitting.Are there a lot of character columns - maybe could be normalised if so.Not necessarily a bad thing in itself==========================================Cursors are useful if you don't know sql.SSIS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
ahmeds08
Aged Yak Warrior
737 Posts |
Posted - 2010-11-25 : 08:38:00
|
| 70% Of the columns are varchars.now what is the best thing to go with. |
|
|
|
|
|
|
table design