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 |
|
ConfusedAgain
Yak Posting Veteran
82 Posts |
 Posted - 2014-03-19 : 13:18:00
|
| I have a table that has in the region of 150 columns. This is because data comes from various sources and there is not a lot that can be done about this. What I am trying to work out is the best way to deal with this on a performance basis.The data held in this table is seen via a windows .net application in a datagridview that collects the data from a SQL View of the table.150 fields in a table is quite a lot to work with would I be better splitting this table so I had the strings in one table the numeric in another and the dates in another all linking back to a main table with a UID.What is the most efficient method for performance and for maintenance of this data? |
|
|
|
|
|
Table with many fields