Update ODBC driver references to latest version

David-Engel · David-Engel · commit 926ae16bf443 · 2020-09-01T10:19:57.000-07:00
diff --git a/docs/connect/odbc/linux-mac/connection-string-keywords-and-data-source-names-dsns.md b/docs/connect/odbc/linux-mac/connection-string-keywords-and-data-source-names-dsns.md
@@ -2,7 +2,7 @@
 title: "Connecting using ODBC"
 description: "Learn how to create a connection to a database from Linux or macOS using the Microsoft ODBC Driver for SQL Server."
 ms.custom: ""
-ms.date: "05/11/2020"
+ms.date: 09/01/2020
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -82,7 +82,7 @@ Regardless of the settings for **Encrypt** and **TrustServerCertificate**, the s
 By default, encrypted connections always verify the server's certificate. However, if you connect to a server that has a self-signed certificate, also add the `TrustServerCertificate` option to bypass checking the certificate against the list of trusted certificate authorities:  
 
 ```
-Driver={ODBC Driver 13 for SQL Server};Server=ServerNameHere;Encrypt=YES;TrustServerCertificate=YES  
+Driver={ODBC Driver 17 for SQL Server};Server=ServerNameHere;Encrypt=YES;TrustServerCertificate=YES  
 ```  
   
 TLS uses the OpenSSL library. The following table shows the minimum supported versions of OpenSSL and the default Certificate Trust Store locations for each platform:
diff --git a/docs/connect/odbc/linux-mac/data-access-tracing-with-the-odbc-driver-on-linux.md b/docs/connect/odbc/linux-mac/data-access-tracing-with-the-odbc-driver-on-linux.md
@@ -2,7 +2,7 @@
 title: "Data Access Tracing with the ODBC Driver on Linux and macOS"
 description: "Learn how to enable tracing on Linux and macOS with the Microsoft ODBC Driver for SQL Server to output a log file when troubleshooting application behavior."
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: 09/01/2020
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -40,7 +40,7 @@ Tracing applies to all applications that use the driver in `odbcinst.ini`. To no
 $ ODBCSYSINI=/home/myappuser myapp
 ```
 
-In this case, you can add `Trace=Yes` to the `[ODBC Driver 13 for SQL Server]` section of `/home/myappuser/odbcinst.ini`.
+In this case, you can add `Trace=Yes` to the `[ODBC Driver 17 for SQL Server]` section of `/home/myappuser/odbcinst.ini`.
 
 ## Determining which odbc.ini File the Driver is Using
 
diff --git a/docs/connect/odbc/linux-mac/known-issues-in-this-version-of-the-driver.md b/docs/connect/odbc/linux-mac/known-issues-in-this-version-of-the-driver.md
@@ -1,7 +1,7 @@
 ---
 title: Known issues for the ODBC driver on Linux and macOS
 description: "Learn about known issues with the Microsoft ODBC Driver for SQL Server on Linux and macOS and steps for troubleshooting connectivity issues."
-ms.date: 05/06/2020
+ms.date: 09/01/2020
 ms.prod: sql
 ms.reviewer: ""
 ms.technology: connectivity
@@ -53,7 +53,7 @@ If you get another connection failure and do not see a log file, there (possibly
         Entry:  
             Connection = 0x17c858e0  
             Window Hdl = (nil)  
-            Str In = [DRIVER={ODBC Driver 13 for SQL Server};SERVER={contoso.com};Trusted_Connection={YES};WSID={mydb.contoso.com};AP...][length = 139 (SQL_NTS)]  
+            Str In = [DRIVER={ODBC Driver 17 for SQL Server};SERVER={contoso.com};Trusted_Connection={YES};WSID={mydb.contoso.com};AP...][length = 139 (SQL_NTS)]  
             Str Out = (nil)  
             Str Out Max = 0  
             Str Out Ptr = (nil)  
diff --git a/docs/connect/odbc/linux-mac/using-integrated-authentication.md b/docs/connect/odbc/linux-mac/using-integrated-authentication.md
@@ -1,9 +1,8 @@
 ---
-description: "Using Integrated Authentication"
 title: "Using Integrated Authentication"
-descrption: "The Microsoft ODBC Driver for SQL Server on Linux and macOS supports connections that use Kerberos integrated authentication."
+description: The Microsoft ODBC Driver for SQL Server on Linux and macOS supports connections that use Kerberos integrated authentication.
 ms.custom: ""
-ms.date: "01/20/2017"
+ms.date: 09/01/2020
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -27,7 +26,7 @@ As of version 17.6, the driver also supports integrated authentication with Azur
 You can enable Kerberos integrated authentication by specifying **Trusted_Connection=yes** in the connection string of **SQLDriverConnect** or **SQLConnect**. For example:  
 
 ```
-Driver='ODBC Driver 13 for SQL Server';Server=your_server;Trusted_Connection=yes  
+Driver='ODBC Driver 17 for SQL Server';Server=your_server;Trusted_Connection=yes  
 ```
   
 When connecting with a DSN, you can also add **Trusted_Connection=yes** to the DSN entry in `odbc.ini`.
diff --git a/docs/connect/odbc/using-always-encrypted-with-the-odbc-driver.md b/docs/connect/odbc/using-always-encrypted-with-the-odbc-driver.md
@@ -2,7 +2,7 @@
 title: "Using Always Encrypted with the ODBC Driver"
 description: "Learn how to develop ODBC applications using Always Encrypted and the Microsoft ODBC Driver for SQL Server."
 ms.custom: ""
-ms.date: 05/06/2020
+ms.date: 09/01/2020
 ms.prod: sql
 ms.technology: connectivity
 ms.topic: conceptual
@@ -35,7 +35,7 @@ Configure Always Encrypted in your database. This involves provisioning Always E
 The easiest way to enable both parameter encryption and resultset encrypted column decryption is by setting the value of the `ColumnEncryption` connection string keyword to **Enabled**. The following is an example of a connection string which enables Always Encrypted:
 
 ```
-SQLWCHAR *connString = L"Driver={ODBC Driver 13 for SQL Server};Server={myServer};Trusted_Connection=yes;ColumnEncryption=Enabled;";
+SQLWCHAR *connString = L"Driver={ODBC Driver 17 for SQL Server};Server={myServer};Trusted_Connection=yes;ColumnEncryption=Enabled;";
 ```
 
 Always Encrypted may also be enabled in the DSN configuration, using the same key and value (which will be overridden by the connection string setting, if present), or programmatically with the `SQL_COPT_SS_COLUMN_ENCRYPTION` pre-connection attribute. Setting it this way overrides the value set in the connection string or DSN:
@@ -406,13 +406,13 @@ The following connection strings show how to authenticate to Azure Key Vault wit
 **ClientID/Secret**:
 
 ```
-DRIVER=ODBC Driver 13 for SQL Server;SERVER=myServer;Trusted_Connection=Yes;DATABASE=myDB;ColumnEncryption=Enabled;KeyStoreAuthentication=KeyVaultClientSecret;KeyStorePrincipalId=<clientId>;KeyStoreSecret=<secret>
+DRIVER=ODBC Driver 17 for SQL Server;SERVER=myServer;Trusted_Connection=Yes;DATABASE=myDB;ColumnEncryption=Enabled;KeyStoreAuthentication=KeyVaultClientSecret;KeyStorePrincipalId=<clientId>;KeyStoreSecret=<secret>
 ```
 
 **Username/Password**:
 
 ```
-DRIVER=ODBC Driver 13 for SQL Server;SERVER=myServer;Trusted_Connection=Yes;DATABASE=myDB;ColumnEncryption=Enabled;KeyStoreAuthentication=KeyVaultPassword;KeyStorePrincipalId=<username>;KeyStoreSecret=<password>
+DRIVER=ODBC Driver 17 for SQL Server;SERVER=myServer;Trusted_Connection=Yes;DATABASE=myDB;ColumnEncryption=Enabled;KeyStoreAuthentication=KeyVaultPassword;KeyStorePrincipalId=<username>;KeyStoreSecret=<password>
 ```
 
 **Managed Identity (system-assigned)**
@@ -639,7 +639,7 @@ See [Migrate Sensitive Data Protected by Always Encrypted](../../relational-data
 
 |IPD Field|Size/Type|Default Value|Description|
 |-|-|-|-|  
-|`SQL_CA_SS_FORCE_ENCRYPT` (1236)|WORD (2 bytes)|0|When 0 (default): decision to encrypt this parameter is determined by availability of encryption metadata.<br><br>When nonzero: if encryption metadata is available for this parameter, it is encrypted. Otherwise, the request fails with error [CE300] [Microsoft][ODBC Driver 13 for SQL Server]Mandatory encryption was specified for a parameter but no encryption metadata was provided by the server.|
+|`SQL_CA_SS_FORCE_ENCRYPT` (1236)|WORD (2 bytes)|0|When 0 (default): decision to encrypt this parameter is determined by availability of encryption metadata.<br><br>When nonzero: if encryption metadata is available for this parameter, it is encrypted. Otherwise, the request fails with error [CE300] [Microsoft][ODBC Driver 17 for SQL Server]Mandatory encryption was specified for a parameter but no encryption metadata was provided by the server.|
 
 ### bcp_control Options
 
diff --git a/docs/connect/odbc/using-azure-active-directory.md b/docs/connect/odbc/using-azure-active-directory.md
@@ -2,7 +2,7 @@
 title: "Using Azure Active Directory with the ODBC Driver"
 description: "The Microsoft ODBC Driver for SQL Server allows ODBC applications to connect to an instance of Azure SQL Database using Azure Active Directory."
 ms.custom: ""
-ms.date: "08/06/2020"
+ms.date: 09/01/2020
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -139,14 +139,14 @@ The `ACCESSTOKEN` is a variable-length structure consisting of a 4-byte _length_
 The following sample shows the code required to connect to SQL Server using Azure Active Directory with connection keywords. Note that there is no need to change the application code itself; the connection string, or DSN if one is used, is the only modification needed to use Azure AD for authentication:
 ~~~
     ...
-    SQLCHAR connString[] = "Driver={ODBC Driver 13 for SQL Server};Server={server};UID=myuser;PWD=myPass;Authentication=ActiveDirectoryPassword"
+    SQLCHAR connString[] = "Driver={ODBC Driver 17 for SQL Server};Server={server};UID=myuser;PWD=myPass;Authentication=ActiveDirectoryPassword"
     ...
     SQLDriverConnect(hDbc, NULL, connString, SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT);    
     ...
 ~~~
 The following sample shows the code required to connect to SQL Server using Azure Active Directory with access token authentication. In this case, it is necessary to modify application code to process the access token and set the associated connection attribute.
 ~~~
-    SQLCHAR connString[] = "Driver={ODBC Driver 13 for SQL Server};Server={server}"
+    SQLCHAR connString[] = "Driver={ODBC Driver 17 for SQL Server};Server={server}"
     SQLCHAR accessToken[] = "eyJ0eXAiOi..."; // In the format extracted from an OAuth JSON response
     ...
     DWORD dataSize = 2 * strlen(accessToken);
diff --git a/docs/connect/odbc/windows/asynchronous-execution-notification-method-sample.md b/docs/connect/odbc/windows/asynchronous-execution-notification-method-sample.md
@@ -2,7 +2,7 @@
 title: "Asynchronous Execution (Notification Method) Sample"
 description: "Example code demonstrating how to use asynchronous execution (using the notification method) in the Microsoft ODBC Driver for SQL Server."
 ms.custom: ""
-ms.date: "01/19/2017"
+ms.date: 09/01/2020
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -312,7 +312,7 @@ int _tmain(int argc, _TCHAR* argv[])
     for(int i = 0; i < g_nConnection; i++)  
     {  
         SQLDriverConnect(g_hDbcs[i],NULL,
-            (SQLCHAR*)"DRIVER={ODBC Driver 13 for SQL Server};Server=your_server;database=your_database;uid=usr;pwd=your_password",
+            (SQLCHAR*)"DRIVER={ODBC Driver 17 for SQL Server};Server=your_server;database=your_database;uid=usr;pwd=your_password",
             SQL_NTS, (SQLCHAR*)g_connOut[i].szOutConnectionString, 500, &g_connOut[i].iLen, SQL_DRIVER_NOPROMPT);  
     }
 
diff --git a/docs/connect/odbc/windows/driver-aware-connection-pooling-in-the-odbc-driver-for-sql-server.md b/docs/connect/odbc/windows/driver-aware-connection-pooling-in-the-odbc-driver-for-sql-server.md
@@ -2,7 +2,7 @@
 title: "Driver-Aware Connection Pooling in the ODBC Driver"
 description: "Learn about enhancements made to driver-aware connection pooling in the Microsoft ODBC Driver for SQL Server on Windows."
 ms.custom: ""
-ms.date: "05/06/2020"
+ms.date: 09/01/2020
 ms.prod: sql
 ms.prod_service: connectivity
 ms.reviewer: ""
@@ -37,7 +37,7 @@ If one of the following connection-attribute IDs or connection string keywords i
   
 -   If there is a difference in any of the following connection keywords between your connection string and a pooled connection string, a pooled connection is not used.  
   
-    |Keyword|ODBC Driver 13|ODBC Driver 11|
+    |Keyword|ODBC Driver 17/13|ODBC Driver 11|
     |-|-|-|
     |`Address`|Yes|Yes|
     |`AnsiNPW`|Yes|Yes|
@@ -62,7 +62,7 @@ If one of the following connection-attribute IDs or connection string keywords i
     
 - If there is a difference in any of the following connection attributes between your connection string and a pooled connection string, a pooled connection is not used.  
   
-    |Attribute|ODBC Driver 13|ODBC Driver 11|  
+    |Attribute|ODBC Driver 17/13|ODBC Driver 11|  
     |-|-|-|  
     |`SQL_ATTR_CURRENT_CATALOG`|Yes|Yes|
     |`SQL_ATTR_PACKET_SIZE`|Yes|Yes|
@@ -88,7 +88,7 @@ If one of the following connection-attribute IDs or connection string keywords i
   
      These connection keywords are not considered when the Driver Manager tries to match your connection with a connection in the pool. (Even if you change one of these parameters, an existing connection can be reused. The driver will reset the options, as needed.) These attributes can be reset in the client side without making an extra network call.  
   
-    |Keyword|ODBC Driver 13|ODBC Driver 11|  
+    |Keyword|ODBC Driver 17/13|ODBC Driver 11|  
     |-|-|-|  
     |`AutoTranslate`|Yes|Yes|
     |`Description`|Yes|Yes|
@@ -102,7 +102,7 @@ If one of the following connection-attribute IDs or connection string keywords i
   
      If you change one of the following connection attributes, an existing connection can be reused.  The driver will reset the value, as needed. The driver can reset these attributes in the client without making an extra network call.  
   
-    |Attribute|ODBC Driver 13|ODBC Driver 11|  
+    |Attribute|ODBC Driver 17/13|ODBC Driver 11|  
     |-|-|-|  
     |All statement attributes|Yes|Yes|
     |`SQL_ATTR_AUTOCOMMIT`|Yes|Yes|
