Errors importing file in SSIS when upgrading from 2005 to 2012

  • We are migrating to 2012 and all is going well except for an SSIS issue.

    We nightly download a financial file from an external provider. An SSIS package then loads this into a table using a flat file source. Nothing too sophisticated.

    This works fine under 2005 but have hit a problem in 2012, getting the error:

    [Source File [116]] Error: The column delimiter for column "Description 2" was not found.

    [Source File [116]] Error: An error occurred while processing file

    "\\xxx\yyy\ myfile.csv" on data row 41935.

    On further investigation of the file we can see the row has a double text delimiter (“) inside the column separators (,) (just prior to AAA below).

    "56371","03-DEC-2010","22-JUN-2010","03-DEC-2012","ABC","PQR","ZZSWAP",""AAA Frz 15Oct@5 % PPP 22/SEP/2011", “CREQWE"

    Researching this, it appears there are changes in this area for 2012.

    This is causing us big issues as we have no ability to avoid this in the source. The format is delimited, delimiter is comma and text qualifier double quote.

    Anyone any ideas how we can modify the package so it handles this like 2005 please?

  • How did 2005 handle it? Did it ignore one of the two repeated "s?

    If it did, sounds like a bug to me.

    I just had a quick look - if you set the 'Text Qualifier' property to <empty string>, SSIS can at least parse the columns correctly (though of course the " characters remain).

    You could subsequently do a Replace in your data flow to get rid of them.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • SQL 2005 treated the extra " as a normal character so " appears in the database column

  • How big is the file, roughly?

    One option would be to pre-process it - maybe use s script task to replace "" with ".

    If the file is huge, it might make sense to do it a different way though.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • That's the conclusion we're come to also!

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply