Features of the Microsoft ODBC Driver for SQL Server on Windows
Microsoft ODBC Driver 17.4 for SQL Server on Windows
The ODBC Driver 17.4 includes the ability to adjust TCP Keep-Alive settings. They can be modified by adding values to the Driver or DSN registry keys. The keys are located in
HKEY_LOCAL_MACHINE\Software\ODBC\ for system data sources, and in
HKEY_CURRENT_USER\Software\ODBC\ for user data sources. For DSN the values need to be added to
...\Software\ODBC\ODBC.INI\<DSN Name> and for the Driver to
...\Software\ODBC\ODBCINST.INI\ODBC Driver 17 for SQL Server.
See Registry Entries for ODBC Components for more information.
The values are
REG_SZ and are as follows:
KeepAlivecontrols how often TCP attempts to verify that an idle connection is still intact by sending a keep-alive packet. The default is 30 seconds.
KeepAliveIntervaldetermines the interval separating keep-alive retransmissions until a response is received. The default is 1 second.
Microsoft ODBC Driver 13.1 for SQL Server on Windows
The ODBC Driver 13.1 for SQL Server contains all the functionality of the previous version (11) and adds support for Always Encrypted and Azure Active Directory authentication when used in conjunction with Microsoft SQL Server 2016.
Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to SQL Server. An Always Encrypted enabled driver installed on the client computer achieves this by automatically encrypting and decrypting sensitive data in the SQL Server client application. The driver encrypts the data in sensitive columns before passing the data to SQL Server, and automatically rewrites queries so that the semantics to the application are preserved. Similarly, the driver transparently decrypts data stored in encrypted database columns that are contained in query results. For more information, see Using Always Encrypted with the ODBC Driver.
Azure Active Directory allows users, DBA's, and application programmers to use Azure Active Directory authentication as a mechanism of connecting to Microsoft Azure SQL Database and Microsoft SQL Server 2016 by using identities in Azure Active Directory (Azure AD). For more information, see Using Azure Active Directory with the ODBC Driver, and Connecting to SQL Database or SQL Data Warehouse By Using Azure Active Directory Authentication.
Microsoft ODBC Driver 11 for SQL Server on Windows
The ODBC Driver for SQL Server contains all the functionality of the SQL Server Native Client ODBC driver that shipped in SQL Server 2012 (11.x). For more information, see SQL Server Native Client Programming. The SQL Server Native Client ODBC driver is based on the ODBC driver that ships in the Windows operating system. For more information, see Windows Data Access Components SDK.
This release of the ODBC Driver for SQL Server contains the following new features:
bcp.exe -l option for specifying a login timeout
The -l option specifies the number of seconds before a
bcp.exe login to SQL Server times out when you try to connect to a server. The default login timeout is 15 seconds. The login timeout must be a number between 0 and 65534. If the value supplied is not numeric or does not fall into that range,
bcp.exe generates an error message. A value of 0 specifies an infinite timeout. A login timeout of less than (approximately) 10 seconds is not reliable.
Driver-Aware Connection Pooling
The ODBC Driver for SQL Server supports Driver-Aware Connection Pooling. For more information, see Driver-Aware Connection Pooling in the ODBC Driver for SQL Server.
Asynchronous Execution (Notification Method)
The ODBC Driver for SQL Server supports Asynchronous Execution (Notification Method). For a usage sample, see Asynchronous Execution (Notification Method) Sample.
To ensure that applications remain connected to a Microsoft Azure SQL Database, the ODBC driver on Windows can restore idle connections. For more information, see Connection Resiliency in the Windows ODBC Driver.
In SQL Server Native Client, the
-y0 option for
sqlcmd.exe caused output to be truncated at 1 MB if the display width was 0.
Beginning in the ODBC Driver 11 for SQL Server, there is no limit on the amount of data that can be retrieved in a single column when
-y0 is specified.
sqlcmd.exe now streams columns as large as 2 GB ( SQL Server data type maximum).
Another difference is that specifying both
-y0 now produces an error reporting that the options are incompatible.
-h, which specifies the number of rows to print between the column headings and has never been compatible with
-y0, was ignored although no headers were printed.
-y0 can cause performance issues on both the server and the network, depending on the size of the data returned.