Cristiano

Today I got a foreign table returning error related to charset below: ``` NOTE: DB-Library notice: Msg #: 5701, Msg state: 2, Msg: Changed database context to 'SIARM'., Server: WINDOWS-0CMIFUI,...

Yes, this is my freetds.conf ``` # $Id: freetds.conf,v 1.12 2007/12/25 06:02:36 jklowden Exp $ # # This file is installed by FreeTDS if no file by the same #...

Relative to postgresql conversions, there are iconv like functions on strings: http://www.postgresql.org/docs/9.3/static/functions-string.html#FUNCTIONS-STRING-OTHER convert_from will convert to database encoding.

The configured server ``` sql CREATE SERVER siarm FOREIGN DATA WRAPPER tds_fdw OPTIONS (servername '192.168.2.30',port '1433'); ``` The table mapping system_information tables, here I also noted a weird caracter ASCII(2)...

Humm, updated the freetds.conf as suggested ``` ini [global] # TDS protocol version tds version = 7.0 client charset = UTF-8 [duquedecaxias] host = 192.168.2.30 port = 1433 tds version...

Yes, the postgresql server has been restarted after each change since I do not known when those parameters are reread by the fdw_tds driver. I trying to discover the 2403...

When I executed a select statement on that system information table(this is a database internal table) I got the following result in psql ``` sql table_catalog | table_schema | table_name...

Found 2403 error code defined at freetds as an constant called SYBEICONVI define in file https://github.com/FreeTDS/freetds/blob/master/include/sybdb.h. Do not need to catch this "error code" as an warning and allow normal...

I followed yours sugestions and found that the failing column is on second query ``` sql SELECT * FROM cliente."MV_IPTU_Contribuintes_CadastroHistoricos_Historico"; ``` beyond 10000 rows fetched.

Digging into MSSQL information_schema.columns table, I found that the type used on column is text(max??) using iso_1 and COLLATION Latin1_General_CI_AI. The following attempt to translate the character to a binary...