Help Importing Excel via SSIS, Cannot mod Registry
I have run up on the major issue of importing Excel 2007 to SQL Server 2005 with characters over 255 being truncated. We are in an agency that will not allow us to change our registry entries so I cannot modify the TypeGuessRows value. Can anyone give me another solid workaround for this aggravating problem ?
August 31st, 2011 3:46pm

I have run up on the major issue of importing Excel 2007 to SQL Server 2005 with characters over 255 being truncated. We are in an agency that will not allow us to change our registry entries so I cannot modify the TypeGuessRows value. Can anyone give me another solid workaround for this aggravating problem ? If you can use third-party solutions, check the commercial CozyRoc Excel Source Plus component. It is a solid workaround.SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2011 11:37pm

I think a safer bet will be to convert the excel file to a .csv file and import it as a flat file. Less headaches!MCTS, MCITP - Please mark posts as answered where appropriate. Answer #1: Have you tried turning it off and on again? Answer #2: It depends...
September 1st, 2011 2:06am

I have run up on the major issue of importing Excel 2007 to SQL Server 2005 with characters over 255 being truncated. We are in an agency that will not allow us to change our registry entries so I cannot modify the TypeGuessRows value. Can anyone give me another solid workaround for this aggravating problem ? The Excel driver reads the first 8 rows to determine the datatype. Just move a row with long column values to the upper 8 rows. And of course switching to CSV is even better :-)Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2011 3:12am

Unfortunately I cannot just move the long data to the first 8 rows because it occurs in more than 1 column. I really appreciate yall's responses so much. I tried the txt and csv routes but I ran into issues with those too but I have tried so many things that I cannot remember exactly what they were !!! I am going to take a look at the 3rd party component and see I can use that. Again...thanks.....YALL ROCK :) Susan Cranford
September 2nd, 2011 11:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics