- Thank you received: 0
Unidentified character type when importing data from PG 12 to DTS SQL
- ernani.silva
- Topic Author
- Offline
- User
-
Less
More
2 years 7 months ago #14599
by ernani.silva
Unidentified character type when importing data from PG 12 to DTS SQL was created by ernani.silva
Hello,
I have the PGNP-Postgres-SE-1.4.0.3612-x64 to import data from PostgreSQL 12 to SQL Server 2017, that works fine.
But whenever I have to import data with a field that contains a special character such as "Á", "ã", "ô", the DTS returns with the unidentified character "?", did any one know how to solve this case?
The encoding from both PG and SQL are LATIN1
Thanks very much!
I have the PGNP-Postgres-SE-1.4.0.3612-x64 to import data from PostgreSQL 12 to SQL Server 2017, that works fine.
But whenever I have to import data with a field that contains a special character such as "Á", "ã", "ô", the DTS returns with the unidentified character "?", did any one know how to solve this case?
The encoding from both PG and SQL are LATIN1
Thanks very much!
Attachments:
Please Log in or Create an account to join the conversation.
- admin
- Offline
- Admin
-
Less
More
- Thank you received: 8
2 years 7 months ago #14600
by admin
Replied by admin on topic Unidentified character type when importing data from PG 12 to DTS SQL
Please change codepage using the Extended Properties FORCECP=WIN1252; parameter. Here is fragment of the Developer's Manual describing the parameter:
FORCECP String or Integer 1.4.0.3264
The code page identifier is used for the conversion of Postgres data into Windows Unicode (UTF-16). One of the predefined strings (see below), or and integer can be used. By default, the provider uses “client_encoding” parameter of the Postgres database. In some case using this parameter can fix conversion issues. For example, when SQL_ASCII database stores characters with values larger than 127, the parameter can be set as WIN1252 for correct conversion.
List of supported CP names: BIG5, EUC_CN, EUC_JIS_2004, EUC_JP, EUC_KR, EUC_TW, GB18030, GBK, ISO_8859_5, ISO_8859_6, ISO_8859_7, ISO_8859_8, JOHAB, KOI8, LATIN1, LATIN2, LATIN3, LATIN4, LATIN5, LATIN6, LATIN7, LATIN8, LATIN9, LATIN10, SHIFT_JIS_2004, SJIS, SQL_ASCII, UHC, UTF8, WIN1250, WIN1251, WIN, WIN1252, WIN1253, WIN1254, WIN1255, WIN1256, WIN1257, WIN1258, TCVN, WIN866, ALT, WIN874.
An integer value can be used for the CP, e.g. 1252 instead of WIN1252.
FORCECP String or Integer 1.4.0.3264
The code page identifier is used for the conversion of Postgres data into Windows Unicode (UTF-16). One of the predefined strings (see below), or and integer can be used. By default, the provider uses “client_encoding” parameter of the Postgres database. In some case using this parameter can fix conversion issues. For example, when SQL_ASCII database stores characters with values larger than 127, the parameter can be set as WIN1252 for correct conversion.
List of supported CP names: BIG5, EUC_CN, EUC_JIS_2004, EUC_JP, EUC_KR, EUC_TW, GB18030, GBK, ISO_8859_5, ISO_8859_6, ISO_8859_7, ISO_8859_8, JOHAB, KOI8, LATIN1, LATIN2, LATIN3, LATIN4, LATIN5, LATIN6, LATIN7, LATIN8, LATIN9, LATIN10, SHIFT_JIS_2004, SJIS, SQL_ASCII, UHC, UTF8, WIN1250, WIN1251, WIN, WIN1252, WIN1253, WIN1254, WIN1255, WIN1256, WIN1257, WIN1258, TCVN, WIN866, ALT, WIN874.
An integer value can be used for the CP, e.g. 1252 instead of WIN1252.
The following user(s) said Thank You: ernani.silva
Please Log in or Create an account to join the conversation.
- ernani.silva
- Topic Author
- Offline
- User
-
Less
More
- Thank you received: 0
2 years 7 months ago #14601
by ernani.silva
Replied by ernani.silva on topic Unidentified character type when importing data from PG 12 to DTS SQL
Thank you very much! This solved my problem

Please Log in or Create an account to join the conversation.
Time to create page: 0.154 seconds