Open ghassett opened 1 year ago
Hi @ghassett,
i face the same issue under wsl2. Under wsl2 with sqlcmd I can only connect with the option "-C".
e.g. sqlcmd -S localhost -U sa -P xxxx -C
This option is the same in the connection string "TrustServerCertificate=True".
I can only assume, I didn't had the time to dig in more deeply, it may not connect because the certficate which is installed on the SQL Server is not thrusted. I think we have to go with installing a thrusted certificate or (I'm only thinking loud...) adapt the usage of the sybase client lib
https://github.com/archimag/cl-mssql/blob/045602a19a32254108f2b75871049293f49731eb/src/mssql.lisp
to add in the communication protocoll the option "TrustServerCertificate=True" or change it with something like FreeTDS from http://www.freetds.org
Hi Guys,
Not sure where else to post/ask this. I am trying to migrate from a MSSQL database to Postgres. The MSSQL server is at host 10.1.10.251, on port 49214. I can connect to this server from my Mac using both SQLPro and Azure Data Studio (just to try a couple of native Mac MSSQL clients), as in the screen shots.
But if I try to connect using
pg_loader
I get a failure for an "unknown reason." I've tried many (many) permutations of the connection string, including settingTDSPORT
variable to 49124 and referencing the server by its Windows-y DOMAIN\SERVERNAME syntax, but always get this same error. I'm also attaching the TDS log. Am I missing something obvious?The TDS Log:
The screen shots from clients that successfully connect: