tds-fdw / tds_fdw

A PostgreSQL foreign data wrapper to connect to TDS databases (Sybase and Microsoft SQL Server)
Other
381 stars 102 forks source link

Foreign Data Wrapper (FDW) to connect to a read-only secondary server on SQL Server #354

Open aviadco11 opened 9 months ago

aviadco11 commented 9 months ago

Issue report

I'm attempting to utilize Foreign Data Wrapper (FDW) to connect to a read-only secondary server on SQL Server. When connecting from a third-party tool, you can simply add the 'read-only' flag, for example, with SQLCMD: sqlcmd -S "SQL01-AG1-list" -d WideWorldImporters-E -q "SELECT @@SERVERNAME;" -Kreadonly This can also be achieved using ODBC. I try to explore if is it possible with tds_fdw ?

Operating system

LINUX / WINDOWS

Replace this with the content

Version of tds_fdw

every version : tds_fdw

If you built the package from Git sources, also paste the output of running git log --source -n 1 on your git clone from a console

Replace this with the output

Version of PostgreSQL

15.0 +

Replace this with the output

Version of FreeTDS

How to get it will depend on your Operating System and how you installes FreeTDS

From a console:

Replace this with the output

Logs

Please capture the logs when the error you are reporting is happening, as well as commands with their outputs if you are reporting a problem build or installing

_For problems using tdsfdw on PostgreSQL how to do it will depend on your system, but if your PostgreSQL is installed on GNU/Linux, you will want to use tail -f with the log of the PostgreSQL cluster

For MSSQL you will need to use the SQL Server Audit Log

Replace this with the commands and outputs

Sentences, data structures, data

This will depend on the exact problem you are having and data privacy restrictions

However the more data you provide, the more likely we will be able to help

As a bare minimum, you should provide

Replace this with the SQL sentences, data structures, etc
juliogonzalez commented 9 months ago

Did you give it a try?

As the README.md file says:

The current version does not yet support JOIN push-down, or write operations.

So it should work, and if that secondary server on SQL Server is read-only, then IMHO there's no risk :-)