Обсуждение: data migration using EXTENSION tds_fdw

Поиск
Список
Период
Сортировка

data migration using EXTENSION tds_fdw

От
Eyüp Liste
Дата:

 

Hello,

I have worked on migrate a table from sql server 2017 to postgresql 15 . İ have completed all steps. But when i try to migrate some columns , i got error;

 

NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting results ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?'), OS #: 0, OS Msg: Success, Level: 4 SQL state: HV00L

 

Please help me about this issue.

 

Best regards

turknet-logo

Eyüp Liste
Technology
System And Infrastructure

 

Re: data migration using EXTENSION tds_fdw

От
Adrian Klaver
Дата:
On 1/14/24 10:55, Eyüp Liste wrote:
> Hello,
> 
> I have worked on migrate a table from sql server 2017 to postgresql 15 . 
> İ have completed all steps. But when i try to migrate some columns , i 
> got error;
> 
> NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting 
> results ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s) 
> could not be converted into client's character set. Unconverted bytes 
> were changed to question marks ('?'), OS #: 0, OS Msg: Success, Level: 4 
> SQL state: HV00L

This "Some character(s) could not be converted into client's character 
set." would seem to be the issue.

Therefore what is the character set used in the?:

1) The SQL Server database.

2) The Postgres database

> 
> Please help me about this issue.
> 
> Best regards
> 
> *turknet-logo* <https://turk.net/>**
> 
>     
> 
> *Eyüp Liste*
> Technology
> System And Infrastructure
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




RE: data migration using EXTENSION tds_fdw

От
Eyüp Liste
Дата:
Hello,

1)TURKISH_CI_AS at sql server database

2)Encoding : UTF8 Collate: en_US.UTF-8  at Postgresql

Thank u for fast response 

Best Regards

Eyup Liste
Senior Database Administrator
___________________________________________________________

TurkNet Iletisim







M: +905452120762
E: eyup.liste@turk.net

-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com> 
Sent: Monday, January 15, 2024 7:10 PM
To: Eyüp Liste <eyup.liste@turk.net>; pgsql-general@lists.postgresql.org
Subject: Re: data migration using EXTENSION tds_fdw


[UYARI] Bu ileti TurkNet dışından gönderildi. Lütfen gönderen adresleri kontrol edin ve ekleri açmadan önce dikkatli
olun.
Spam/phishing olduğunu düşündüğünüz mailler için spambildir@turknet.net.tr<mailto:spambildir@turknet.net.tr> adresine
bilgiverebilirsiniz.
 


On 1/14/24 10:55, Eyüp Liste wrote:
> Hello,
>
> I have worked on migrate a table from sql server 2017 to postgresql 15 .
> İ have completed all steps. But when i try to migrate some columns , i 
> got error;
>
> NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting 
> results ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s) 
> could not be converted into client's character set. Unconverted bytes 
> were changed to question marks ('?'), OS #: 0, OS Msg: Success, Level: 
> 4 SQL state: HV00L

This "Some character(s) could not be converted into client's character set." would seem to be the issue.

Therefore what is the character set used in the?:

1) The SQL Server database.

2) The Postgres database

>
> Please help me about this issue.
>
> Best regards
>
> *turknet-logo* <https://turk.net/>**
>
>
>
> *Eyüp Liste*
> Technology
> System And Infrastructure
>

--
Adrian Klaver
adrian.klaver@aklaver.com


Re: data migration using EXTENSION tds_fdw

От
Adrian Klaver
Дата:
On 1/15/24 11:03 AM, Eyüp Liste wrote:
> Hello,
>
> 1)TURKISH_CI_AS at sql server database
>
> 2)Encoding : UTF8 Collate: en_US.UTF-8  at Postgresql

I don't use tds_fdw, so the best I can do is point you at information

Hopefully someone with practical experience will chime in with more 
specific information.

The information I could find is:

https://www.freetds.org/userguide/configs.html#Localization










>
> Thank u for fast response
>
> Best Regards
>
> Eyup Liste
> Senior Database Administrator
> ___________________________________________________________
>
> TurkNet Iletisim
>
>
>
>
>
>
>
> M: +905452120762
> E: eyup.liste@turk.net
>
> -----Original Message-----
> From: Adrian Klaver <adrian.klaver@aklaver.com>
> Sent: Monday, January 15, 2024 7:10 PM
> To: Eyüp Liste <eyup.liste@turk.net>; pgsql-general@lists.postgresql.org
> Subject: Re: data migration using EXTENSION tds_fdw
>
>
> [UYARI] Bu ileti TurkNet dışından gönderildi. Lütfen gönderen adresleri kontrol edin ve ekleri açmadan önce dikkatli
olun.
> Spam/phishing olduğunu düşündüğünüz mailler için spambildir@turknet.net.tr<mailto:spambildir@turknet.net.tr> adresine
bilgiverebilirsiniz.
 
>
>
> On 1/14/24 10:55, Eyüp Liste wrote:
>> Hello,
>>
>> I have worked on migrate a table from sql server 2017 to postgresql 15 .
>> İ have completed all steps. But when i try to migrate some columns , i
>> got error;
>>
>> NOTICE: tds_fdw: Query executed correctly NOTICE: tds_fdw: Getting
>> results ERROR: DB-Library error: DB #: 2403, DB Msg: Some character(s)
>> could not be converted into client's character set. Unconverted bytes
>> were changed to question marks ('?'), OS #: 0, OS Msg: Success, Level:
>> 4 SQL state: HV00L
> This "Some character(s) could not be converted into client's character set." would seem to be the issue.
>
> Therefore what is the character set used in the?:
>
> 1) The SQL Server database.
>
> 2) The Postgres database
>
>> Please help me about this issue.
>>
>> Best regards
>>
>> *turknet-logo* <https://turk.net/>**
>>
>>
>>
>> *Eyüp Liste*
>> Technology
>> System And Infrastructure
>>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>



Re: data migration using EXTENSION tds_fdw

От
Jim Nasby
Дата:
On 1/15/24 1:17 PM, Adrian Klaver wrote:
> 
> I don't use tds_fdw, so the best I can do is point you at information
> 
> Hopefully someone with practical experience will chime in with more 
> specific information.
> 
> The information I could find is:
> 
> https://www.freetds.org/userguide/configs.html#Localization

One other UTF8 "gotcha" in Postgres that may or may not be relevant 
here: UTF8 considers the value 0 (as in a 0 byte; not the glyph "0") to 
be a legit character, but for various reasons Postgres can't actually 
support that, so trying to insert into a text/varchar/char field in PG 
will give you an error (not sure what exact error you'd get though).
-- 
Jim Nasby, Data Architect, Austin TX