Comments on: How to Solve Problem That Excel Data Imported Into SQL Server Via DTS Became Null http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html Random thoughts and news by Andrew Chen and friends Thu, 09 Feb 2012 14:05:12 +0000 http://wordpress.org/?v=2.5 By: Gabe http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-105626 Gabe Thu, 16 Sep 2010 15:19:28 +0000 http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-105626 I want to expand on what Alan Houck mentioned. Firstly, while the default for TypeGuessRows is 8, setting this to 0 "only" examines the first 16,384 lines. Obviously I say "only" because that's far better than 8 but it doesn't examine ALL 65536 rows of an Excel 2000 or 2003 sheet (not sure about 2007 or 2010 as I haven't used those but I know they allow more than 2^16 rows). Secondly, I've done imports with SQL Server 2005 Import Wizard and even with TypeGuessRows set to 0, I'd still get NULL imports when a column had mixed datatypes (and there were far less than 16,384 rows of data imported). That being said, I've had experiences where I didn't use a script with the "IMEX=1" parameter and the TypeGuessRows change helped import the data correctly (usually an error was avoided in these instances "column doesn't allow mixed datatypes"). I've also had experiences where the "IMEX=1" was used in a script and that was the only way to get data imported correctly...but in all of those instances the TypeGuessRows were set to 0 so I'd be interested to see an instance where "IMEX=1" doesn't work because TypeGuessRows = 8. I think the best bet is, change TypeGuessRows AND use a script with IMEX=1 at all times. HTH I want to expand on what Alan Houck mentioned.

Firstly, while the default for TypeGuessRows is 8, setting this to 0 “only” examines the first 16,384 lines. Obviously I say “only” because that’s far better than 8 but it doesn’t examine ALL 65536 rows of an Excel 2000 or 2003 sheet (not sure about 2007 or 2010 as I haven’t used those but I know they allow more than 2^16 rows).

Secondly, I’ve done imports with SQL Server 2005 Import Wizard and even with TypeGuessRows set to 0, I’d still get NULL imports when a column had mixed datatypes (and there were far less than 16,384 rows of data imported).

That being said, I’ve had experiences where I didn’t use a script with the “IMEX=1″ parameter and the TypeGuessRows change helped import the data correctly (usually an error was avoided in these instances “column doesn’t allow mixed datatypes”). I’ve also had experiences where the “IMEX=1″ was used in a script and that was the only way to get data imported correctly…but in all of those instances the TypeGuessRows were set to 0 so I’d be interested to see an instance where “IMEX=1″ doesn’t work because TypeGuessRows = 8.

I think the best bet is, change TypeGuessRows AND use a script with IMEX=1 at all times.

HTH

]]> By: Shazzbot http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-88335 Shazzbot Tue, 06 Apr 2010 11:31:55 +0000 http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-88335 Thank you thank you thank you! That worked, nothing else suggested anywhere else, ever, has worked for me. Thank you thank you thank you! That worked, nothing else suggested anywhere else, ever, has worked for me.

]]> By: Jaya http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-71061 Jaya Mon, 28 Sep 2009 10:24:42 +0000 http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-71061 Thanks so much for an intelligent and usable article. Thanks so much for an intelligent and usable article.

]]> By: Andrew Chen http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-62556 Andrew Chen Thu, 11 Jun 2009 06:57:50 +0000 http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-62556 I am glad that help. Thank you for commenting :cool: I am glad that help. Thank you for commenting :cool:

]]> By: SQLMadness http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-62340 SQLMadness Mon, 08 Jun 2009 19:15:38 +0000 http://www.siusic.com/wphchen/how-to-solve-problem-that-excel-data-imported-into-sql-server-via-dts-became-null-108.html#comment-62340 I wanted to thank you for this tip. It help me sort out a problem with NULL values when importing to SQL using Jet engine. I wanted to thank you for this tip. It help me sort out a problem with NULL values when importing to SQL using Jet engine.

]]>