Junk text characters causing SSIS import to fail with truncation error

  • Hello all,

    There have been some junk text text characters in my file to be imported causing truncation errors in my SSIS package.

    In my source application the text looks like a dash '-'. When it gets exported it looks like '–'.

    The data gets exported to a file (not a SSIS process). This export does have a SQL statement associated with it so if there are suggestions for fixing this here, that would be great.

    The file then gets imported with an SSIS package. Here is where I got my truncation error. Any suggestions for preventing this at this stage would be welcome.

    Thanks!

  • Its sounds like the file generator ( The app that created the file ) is using unicode instead of ascII, verify that the file format its ascii and not unicode.

  • I won't be able to change the format of the file, I can change the SQL that determines the data in the file. Can I remove the unicode characters in a SELECT statement?

Viewing 3 posts - 1 through 2 (of 2 total)

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