I am using SSIS with SQL Server 2008 R2. I import large text files (about 0.5 GB), and these files use double quotes as a classifier for text, and a comma as a field separator.
Many of the files have text fields and include a comma between trailing double quotes. SSIS must interpret this one field (which contains a comma). Instead, he interprets it as two different fields.
I can find many workarounds for SQL 2005 - usually under the heading "undouble" - but the only workarounds of 2008 that I can find require some complicated programming. Does anyone have any easy workarounds for 2008?
Very much appreciated ...
ssis
Kim prince
source share