Blog Post

SQL Server Blog
1 MIN READ

ODBC Driver 17.4 for SQL Server Released

David-Engel's avatar
David-Engel
Iron Contributor
Aug 01, 2019

Version 17.4 of the Microsoft ODBC Driver 17 for SQL Server has been released. Version 17.4 brings several added features and fixed issues.

 

Added

  • Support for Always Encrypted with Secure Enclaves
  • Support for dynamic loading of OpenSSL (on Linux/macOS)
  • Support for insertion of UTF-8 data against SQL Server 2019
  • Support for configuring TCP Keep Alive settings
  • Support for Debian 10
  • Support for RedHat 8
  • Support for Ubuntu 19.04
  • Support for connecting to named instances on Linux and macOS

Fixed

  • Intermittent hang when Multiple Active Results Sets (MARS) is enabled
  • Connection resiliency hang when async notification is enabled
  • Crash when retrieving diagnostic records for multithreaded connection attempts
  • 'Encryption not supported' upon reconnect after calling SQLGetInfo() with SQL_USER_NAME and SQL_DATA_SOURCE_READ_ONLY
  • COM initialization error during Azure Active Directory Interactive Authentication
  • SQLGetData() for multi-byte UTF-8 data
  • Retrieving length of sql_variant columns using SQLGetData()
  • Importing of sql_variant columns containing more than 7992 bytes using bcp
  • Sending of correct encoding to server for narrow character data

Next steps

For Windows installations, you can directly download the Microsoft ODBC Driver 17 for SQL Server.

Linux and macOS packages are also being made available. For installation details see the online instructions.

 

Roadmap

We are committed to improving quality and bringing more feature support for connecting to SQL Server Azure SQL Database Azure SQL DW, and Azure SQL Managed Instance through regular driver releases. We invite you to explore the latest the Microsoft Data Platform has to offer via a trial of Microsoft Azure SQL Database or by evaluating Microsoft SQL Server.

David Engel

Updated Feb 19, 2020
Version 3.0

12 Comments

  • David-Engel's avatar
    David-Engel
    Iron Contributor

    rpodric Do you happen to know which 17.x version you upgraded from? I recall there was an issue with one of the first 17.x releases that basically required an uninstall/reinstall to fix the upgrade for any subsequent 17.x install.

  • rpodric's avatar
    rpodric
    Bronze Contributor

    This may or may not be expected, but I saw it on two unrelated systems (Win10, Server 2016), so it couldn't have been a fluke. I chose the upgrade method, over a v17 from 2018. It completed fine. However, the system DSN I had no longer worked. Furthermore, when I went to create a new one (with odbcad32.exe), the UI to do so after clicking System/Add/driver never actually appeared.

     

    Clearly, something was wrong. So I ran the installer again, this time choosing repair. In both installations, that worked.