Bulk Loading Data for Other Locales

If you load data for other locales into your hub using database bulk-load utilities, ensure that the encoding in the add_update_<entity_type>.ddf jobs matches the codepage for your database. If these values do not match, some of the data might be translated into the database's codepage incorrectly.
The add_update_<entity_type>.ddf jobs interact with the DBMS bulk-load utilities by writing a data file representing your entities, and then invoking the bulk-load utilities with that data file as input. To change the encoding of the data file, open the Properties dialog box for the Write to Staging File node at the bottom of the job, and set the Encoding to a value that matches your database.
In addition to setting the output file encoding, you might find it necessary to change the control files used by the database utilities, which guide the interpretation of the file contents.
Database Control Files
Database
Relevant Files
Oracle
Look for the characterset parameter in .ctl files.
SQL Server
bcp files have a column collation field.
For more information, see your database documentation.
Last updated: April 19, 2017