SSMS ODBC Linked Server Issue

From: Dulanic <dulanic(at)gmail(dot)com>
To: pgsql-odbc(at)lists(dot)postgresql(dot)org
Subject: SSMS ODBC Linked Server Issue
Date: 2021-08-17 18:36:01
Message-ID: CAMiuOHUZt1sFV10ytMBGabHCf6qksb5LZ3ryKhktN_+FtkxW2Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Hello,

I have reviewed a few different examples of SQL Server/Postgres ODBC linked
server connections. I have gotten some to work, but some tables refuse.
This is the query I am attempting to run and the methods I have tried so
far.

select *
from POSTGRES.teslamate.[public].addresses

and

select * from openquery(POSTGRES,'
select *
from public.addresses
')

but both error out /w this error:

Msg 7356, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "POSTGRES" supplied
inconsistent metadata for a column. The column "display_name" (compile-time
ordinal 2) of object "
select *
from public.addresses
" was reported to have a "LENGTH" of 512 at compile time and 174 at run
time. It seems like it is saying it's a 512 length field, and it is. It is
a character varying(512). However, when the query runs, it comes back
saying it's a 174 length field which is the current max length. These are
the settings I am using for ODBC, though I have tried every
possible variation of these that I could find to solve.

These are my options in SSMS:
https://dulanic.com/img/ssms.png

These are my options in ODBC.
https://dulanic.com/img/odbc.png
https://dulanic.com/img/odbc1.png
https://dulanic.com/img/odbc2.png

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message David Parenteau 2021-08-17 18:48:45 RE: SSMS ODBC Linked Server Issue
Previous Message Joris Wit 2021-08-13 16:58:14 SQLSpecialColumns result set column names should change for ODBC 3 compatibility