September 2, 2020 at 10:29 am
Hello,
I have a couple of SSIS packages running, the first package exports data from SQL Server 2014 and saves it to a file share, the second package picks up the file and loads it into Salesforce using the data loader. One of my users has complained that Umlauts and Accent characters do not display correctly. I have tried various different code pages but nothing works for one reason or another.
All of my text columns in SQL server are nvarchar
All of my text columns in the flat file connection manager are DT_WSTR
I am using code page 65001 UTF-8
In the data flow source, I have set the code page to 65001 and AlwaysUseDefaultCodePage=True
With the settings above, the process is working but the umlaut and accent characters are replaced with garbage (eg, ü is replaced with ö)
I attempted to resolve the above issue by changing the code page to 1252 Latin, the issue with umlaut and accent characters is resolved but I get a failure on other data. One row has the degree (°) character and fails with error: "Data conversion failed. The data conversion for column "BillingStreet" returned status value 4 and status text "Text was truncated or one or more characters had no match in the target code page.". The BillingStreet datatype is nvarchar(500) and the SSIS datatype is DT_WSTR(500).
I then attempted to check the Unicode box in the flat file connection manager, this resolved the issue with the degree (°) character and also my issue with the umlauts and accent characters, however, the excel file looks a bit different, when I open it the whole row is displayed in the first excel column and when I run the second package to try and process the file, the Salesforce data loader complains that it doesn't recognize the file format.
I am working with garbage source data but what I am trying to achieve is to parse all characters in their original form, any help would be greatly appreciated.
September 2, 2020 at 11:19 am
At what point is the error failing? If you had already created the data flow task, and then changed the code page of the file, SSIS can have a habit of leaving parts of the dataflow using the old code page in the definitions in the data flow.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
September 2, 2020 at 2:38 pm
I believe it's failing on the flat file destination task, if I replace the destination task with a sort task, it returns all the data without any error.
I did initially use the 1252 Latin code page before changing it to UTF-8. Then, to try and remove any reference to the old code page, I deleted the flat file connection manager and the destination task before re-adding them. This didn't solve the issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply