InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 14:26:35 GMT20http://www.sqlservercentral.com/Forums/Topic1375412-9-1.aspxSean,Thanks for the reply. Appreciate it.Thu, 03 Jan 2013 09:23:48 GMTAVBhttp://www.sqlservercentral.com/Forums/Topic1375412-9-1.aspx[quote][b]AVB (10/22/2012)[/b][hr]I'm building an import package for a CSV file that has about 200 columns. If every column was maxed out it would be about 2200 bytes and is well below the max table size. Should I split this up into multiple tables because of the amount of columns?[/quote]My guess is that with that many columns the data could stand to be normalized. I would import it into a wide table and then normalize it. I don't see any reason to break this into 2 tables. If the rows were too wide then yes but otherwise it is going to be more work than needed.Mon, 22 Oct 2012 09:29:23 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1375412-9-1.aspxI'm building an import package for a CSV file that has about 200 columns. If every column was maxed out it would be about 2200 bytes and is well below the max table size. Should I split this up into multiple tables because of the amount of columns?Mon, 22 Oct 2012 07:15:03 GMTAVB