Re: SQL Server 2016 support
Frediano Ziglio <[email protected]> Wed, 10 Aug 2016 17:22:57 +0100
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <CAHt6W4f8EkAdkHe=LFqw=D7bHDWw6oc_3ErOG_F-w9ASwa1GOw@mail.gmail.com> |
2016-08-09 16:48 GMT+01:00 Sebastien FLAESCH <[email protected]>: > In fact from time to time the connection to SQL Server 2016 fails. > > No idea if this is a server issue or FreeTDS bug, but it occurs only with > FreeTDS. > > We do the same tests with Easysoft's ODBC driver for SQL Server and no > problem with that one. > > Attached the TDSDUMP... hopefully this can help. > > Seb > Quite a mystery I would say. Looks like that during TLS initialization (just before saying ok) server drop the connection. The TLS packets looks the same, the content obviously is not as contains keys and encrypted data. Could be that the library (either OpenSSL or GnuTLS) you are using on the client craft some not so secure keys and server refuse them? Does the server report some error in the log? How often does this happen? I checked and the flag the client/server agree on is the same (0). Frediano > > On 08/09/2016 09:48 AM, Sebastien FLAESCH wrote: >> >> Hi all, >> >> What is the status of SQL Server 2016 support? >> >> I could not find any thread with "FreeTDS" + "SQL Server 2016" on the net. >> >> Is there any doc / howto available? >> >> For example, what is the TDS protocol version to be used? >> >> We have executed our SQL regressions tests. >> >> FreeTDS 1.0 seems to work fine with SQL Server 2016 using: >> >> TDS_Version = 7.3 >> >> Thanks, >> Seb