You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/connect/jdbc/feature-dependencies-of-microsoft-jdbc-driver-for-sql-server.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Feature dependencies of the Microsoft JDBC Driver for SQL Server | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "02/10/2020"
4
+
ms.date: "03/24/2020"
5
5
ms.prod: sql
6
6
ms.prod_service: connectivity
7
7
ms.reviewer: ""
@@ -38,7 +38,7 @@ Specific projects that require either of the preceding features need to explicit
38
38
<dependency>
39
39
<groupId>com.microsoft.sqlserver</groupId>
40
40
<artifactId>mssql-jdbc</artifactId>
41
-
<version>8.2.1.jre11</version>
41
+
<version>8.2.2.jre11</version>
42
42
<scope>compile</scope>
43
43
</dependency>
44
44
@@ -61,7 +61,7 @@ Specific projects that require either of the preceding features need to explicit
61
61
<dependency>
62
62
<groupId>com.microsoft.sqlserver</groupId>
63
63
<artifactId>mssql-jdbc</artifactId>
64
-
<version>8.2.1.jre11</version>
64
+
<version>8.2.2.jre11</version>
65
65
<scope>compile</scope>
66
66
</dependency>
67
67
@@ -88,7 +88,7 @@ Specific projects that require either of the preceding features need to explicit
88
88
89
89
### Working with the Azure Key Vault provider:
90
90
91
-
- JDBC driver version 8.2.1 - Dependency versions: Azure-Keyvault (version 1.2.2), Adal4j (version 1.6.4), Client-Runtime-for-AutoRest (1.7.0), and their dependencies ([sample application](../../connect/jdbc/azure-key-vault-sample-version-7.0.md))
91
+
- JDBC driver version 8.2.2 - Dependency versions: Azure-Keyvault (version 1.2.2), Adal4j (version 1.6.4), Client-Runtime-for-AutoRest (1.7.0), and their dependencies ([sample application](../../connect/jdbc/azure-key-vault-sample-version-7.0.md))
92
92
- JDBC driver version 7.4.1 - Dependency versions: Azure-Keyvault (version 1.2.1), Adal4j (version 1.6.4), Client-Runtime-for-AutoRest (1.6.10), and their dependencies ([sample application](../../connect/jdbc/azure-key-vault-sample-version-7.0.md))
93
93
- JDBC driver version 7.2.2 - Dependency versions: Azure-Keyvault (version 1.2.0), Azure-Keyvault-Webkey (version 1.2.0), Adal4j (version 1.6.3), Client-Runtime-for-AutoRest (1.6.5), and their dependencies ([sample application](../../connect/jdbc/azure-key-vault-sample-version-7.0.md))
94
94
- JDBC driver version 7.0.0 - Dependency versions: Azure-Keyvault (version 1.0.0), Adal4j (version 1.6.0), and their dependencies ([sample application](../../connect/jdbc/azure-key-vault-sample-version-7.0.md))
@@ -103,7 +103,7 @@ Specific projects that require either of the preceding features need to explicit
103
103
104
104
### Working with Azure Active Directory authentication:
105
105
106
-
- JDBC Driver version 8.2.1 - Dependency versions: Adal4j (version 1.6.4), Client-Runtime-for-AutoRest (1.7.0), and their dependencies. In this version of the driver, 'sqljdbc_auth.dll' has been renamed to 'mssql-jdbc_auth-\<version>-\<arch>.dll'.
106
+
- JDBC Driver version 8.2.2 - Dependency versions: Adal4j (version 1.6.4), Client-Runtime-for-AutoRest (1.7.0), and their dependencies. In this version of the driver, 'sqljdbc_auth.dll' has been renamed to 'mssql-jdbc_auth-\<version>-\<arch>.dll'.
107
107
- JDBC Driver version 7.4.1 - Dependency versions: Adal4j (version 1.6.4), Client-Runtime-for-AutoRest (1.6.10), and their dependencies
108
108
- JDBC Driver version 7.2.2 - Dependency versions: Adal4j (version 1.6.3), Client-Runtime-for-AutoRest (1.6.5), and their dependencies
109
109
- JDBC Driver version 7.0.0 - Dependency versions: Adal4j (version 1.6.0) and its dependencies
@@ -115,7 +115,7 @@ From driver version 6.4.0 onward, applications don't necessarily require using A
115
115
116
116
For *Windows operating systems*, the driver looks for sqljdbc_auth.dll by default and doesn't require Kerberos ticket setup or Azure library dependencies. If sqljdbc_auth.dll isn't available, the driver looks for the Kerberos ticket for authenticating to Active Directory as on other operating systems.
117
117
118
-
From driver version 8.2.1 onward, 'sqljdbc_auth.dll' is renamed to 'mssql-jdbc_auth-\<version>-\<arch>.dll'. E.g. 'mssql-jdbc_auth-8.2.1.x64.dll'.
118
+
From driver version 8.2.2 onward, 'sqljdbc_auth.dll' is renamed to 'mssql-jdbc_auth-\<version>-\<arch>.dll'. E.g. 'mssql-jdbc_auth-8.2.2.x64.dll'.
119
119
120
120
You can get a [sample application](../../connect/jdbc/connecting-using-azure-active-directory-authentication.md) that uses this feature.
The Microsoft JDBC Driver 7.4 supports the JDBC 4.2, and 4.3 (partially) specifications and includes three JAR class libraries in the installation package as follows:
Copy file name to clipboardExpand all lines: docs/connect/jdbc/release-notes-for-the-jdbc-driver.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Release notes for the JDBC Driver"
3
3
ms.custom: ""
4
-
ms.date: "03/13/2020"
4
+
ms.date: "03/24/2020"
5
5
ms.prod: sql
6
6
ms.prod_service: connectivity
7
7
ms.reviewer: ""
@@ -20,8 +20,8 @@ This article lists the releases of the _Microsoft JDBC Driver for SQL Server_. F
20
20
**[ Download Microsoft JDBC Driver 8.2 for SQL Server (zip)](https://go.microsoft.com/fwlink/?linkid=2122433)**
21
21
**[ Download Microsoft JDBC Driver 8.2 for SQL Server (tar.gz)](https://go.microsoft.com/fwlink/?linkid=2122536)**
22
22
23
-
Version number: 8.2.0
24
-
Released: January 31, 2020
23
+
Version number: 8.2.2
24
+
Released: March 24, 2020
25
25
26
26
If you need to download the driver in a language other than the one detected for you, you can use these direct links.
27
27
For the driver in a zip file: [Chinese (Simplified)](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x804) | [Chinese (Traditional)](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x404) | [English (United States)](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x409) | [French](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x40c) | [German](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x407) | [Italian](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x410) | [Japanese](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x411) | [Korean](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x412) | [Portuguese (Brazil)](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x416) | [Russian](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x419) | [Spanish](https://go.microsoft.com/fwlink/?linkid=2122433&clcid=0x40a)
@@ -31,8 +31,8 @@ For the driver in a tar.gz file: [Chinese (Simplified)](https://go.microsoft.com
31
31
32
32
| Compliance change | Details |
33
33
| :---------------- | :------ |
34
-
| Download the latest updates for JDBC Driver 8.2. |• [GitHub, 8.2.0](https://github.com/Microsoft/mssql-jdbc/releases/tag/v8.2.0)<br/>• [Maven Central](https://search.maven.org/search?q=g:com.microsoft.sqlserver)|
35
-
| Fully compliant with JDBC API Specification 4.2. | The jars in the 8.2 package are named according to Java version compatibility.<br/><br/>For example, the mssql-jdbc-8.2.0.jre11.jar file from the 8.2 package should be used with Java 11. |
34
+
| Download the latest updates for JDBC Driver 8.2. |• [GitHub, 8.2.2](https://github.com/Microsoft/mssql-jdbc/releases/tag/v8.2.2)<br/>• [Maven Central](https://search.maven.org/search?q=g:com.microsoft.sqlserver)|
35
+
| Fully compliant with JDBC API Specification 4.2. | The jars in the 8.2 package are named according to Java version compatibility.<br/><br/>For example, the mssql-jdbc-8.2.2.jre11.jar file from the 8.2 package should be used with Java 11. |
36
36
| Compatible with Java Development Kit (JDK) version 13.0, 11.0, and 1.8. | Microsoft JDBC Driver 8.2 for SQL Server is now compatible with Java Development Kit (JDK) version 13.0 in addition to JDK 11.0 and 1.8. |
Copy file name to clipboardExpand all lines: docs/connect/jdbc/system-requirements-for-the-jdbc-driver.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "System requirements for the JDBC driver | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "02/10/2020"
4
+
ms.date: "03/24/2020"
5
5
ms.prod: sql
6
6
ms.prod_service: connectivity
7
7
ms.reviewer: ""
@@ -41,17 +41,17 @@ ms.author: genemi
41
41
42
42
**Microsoft JDBC Driver 8.2 for SQL Server:**
43
43
44
-
The JDBC Driver 8.2 includes three JAR class libraries in each installation package: **mssql-jdbc-8.2.1.jre8.jar**, **mssql-jdbc-8.2.1.jre11.jar**, and **mssql-jdbc-8.2.1.jre13.jar**.
44
+
The JDBC Driver 8.2 includes three JAR class libraries in each installation package: **mssql-jdbc-8.2.2.jre8.jar**, **mssql-jdbc-8.2.2.jre11.jar**, and **mssql-jdbc-8.2.2.jre13.jar**.
45
45
46
46
The JDBC Driver 8.2 is designed to work with and be supported by all major Java virtual machines, but is tested only on OpenJDK 1.8, OpenJDK 11.0, OpenJDK 13.0, Azul Zulu JRE 1.8, Azul Zulu JRE 11.0, and Azul Zulu JRE 13.0.
47
47
48
48
The following summarizes support provided by the two JAR files included with Microsoft JDBC Drivers 8.2 for SQL Server:
49
49
50
50
|JAR|JDBC Version Compliance|Recommended Java Version|Description|
|mssql-jdbc-8.2.1.jre8.jar|4.2|8|Requires a Java Runtime Environment (JRE) 1.8. Using JRE 1.7 or lower throws an exception.<br /><br /> New Features in 8.2 include: JDK 13 support, Always Encrypted with Secure Enclaves, and temporal datatype performance improvements. |
53
-
|mssql-jdbc-8.2.1.jre11.jar|4.3|11|Requires a Java Runtime Environment (JRE) 11.0. Using JRE 10.0 or lower throws an exception.<br /><br /> New Features in 8.2 include: JDK 13 support, Always Encrypted with Secure Enclaves, and temporal datatype performance improvements. |
54
-
|mssql-jdbc-8.2.1.jre13.jar|4.3|13|Requires a Java Runtime Environment (JRE) 13.0. Using JRE 11.0 or lower throws an exception.<br /><br /> New Features in 8.2 include: JDK 13 support, Always Encrypted with Secure Enclaves, and temporal datatype performance improvements. |
52
+
|mssql-jdbc-8.2.2.jre8.jar|4.2|8|Requires a Java Runtime Environment (JRE) 1.8. Using JRE 1.7 or lower throws an exception.<br /><br /> New Features in 8.2 include: JDK 13 support, Always Encrypted with Secure Enclaves, and temporal datatype performance improvements. |
53
+
|mssql-jdbc-8.2.2.jre11.jar|4.3|11|Requires a Java Runtime Environment (JRE) 11.0. Using JRE 10.0 or lower throws an exception.<br /><br /> New Features in 8.2 include: JDK 13 support, Always Encrypted with Secure Enclaves, and temporal datatype performance improvements. |
54
+
|mssql-jdbc-8.2.2.jre13.jar|4.3|13|Requires a Java Runtime Environment (JRE) 13.0. Using JRE 11.0 or lower throws an exception.<br /><br /> New Features in 8.2 include: JDK 13 support, Always Encrypted with Secure Enclaves, and temporal datatype performance improvements. |
55
55
56
56
57
57
The JDBC Driver 8.2 is also available on the Maven Central Repository and can be added to a Maven project by adding the following code in the POM.XML:
Copy file name to clipboardExpand all lines: docs/connect/jdbc/understanding-java-ee-support.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Understanding Java EE support | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "02/10/2020"
4
+
ms.date: "03/24/2020"
5
5
ms.prod: sql
6
6
ms.prod_service: connectivity
7
7
ms.reviewer: ""
@@ -33,7 +33,7 @@ For JDBC Driver 7.2, the driver is contained in **mssql-jdbc-7.2.2.jre8.jar**, o
33
33
34
34
For JDBC Driver 7.4, the driver is contained in **mssql-jdbc-7.4.1.jre8.jar**, **mssql-jdbc-7.4.1.jre11.jar**, or **mssql-jdbc-7.4.1.jre12.jar**.
35
35
36
-
For JDBC Driver 8.2, the driver is contained in **mssql-jdbc-8.2.1.jre8.jar**, **mssql-jdbc-8.2.1.jre11.jar**, or **mssql-jdbc-8.2.1.jre13.jar**.
36
+
For JDBC Driver 8.2, the driver is contained in **mssql-jdbc-8.2.2.jre8.jar**, **mssql-jdbc-8.2.2.jre11.jar**, or **mssql-jdbc-8.2.2.jre13.jar**.
37
37
38
38
The class name is used whenever you load the driver with the JDBC DriverManager class, and whenever you specify the class name of the driver in any driver configuration. For example, configuring a data source within a Java EE application server might require you enter the driver class name.
Copy file name to clipboardExpand all lines: docs/connect/jdbc/using-always-encrypted-with-the-jdbc-driver.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Using Always Encrypted with the JDBC driver | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "01/29/2020"
4
+
ms.date: "03/24/2020"
5
5
ms.prod: sql
6
6
ms.prod_service: connectivity
7
7
ms.reviewer: ""
@@ -53,6 +53,8 @@ All of these keystore providers are described in more detail in the sections tha
53
53
### Using Azure Key Vault provider
54
54
Azure Key Vault is a convenient option to store and manage column master keys for Always Encrypted (especially if your application is hosted in Azure). The Microsoft JDBC Driver for SQL Server includes a built-in provider, SQLServerColumnEncryptionAzureKeyVaultProvider, for applications that have keys stored in Azure Key Vault. The name of this provider is AZURE_KEY_VAULT. In order to use the Azure Key Vault store provider, an application developer needs to create the vault and the keys in Azure Key Vault and create an App registration in Azure Active Directory. The registered application must be granted Get, Decrypt, Encrypt, Unwrap Key, Wrap Key, and Verify permissions in the Access policies defined for the key vault created for use with Always Encrypted. For more information on how to set up the key vault and create a column master key, see [Azure Key Vault - Step by Step](https://blogs.technet.microsoft.com/kv/2015/06/02/azure-key-vault-step-by-step/) and [Creating Column Master Keys in Azure Key Vault](../../relational-databases/security/encryption/create-and-store-column-master-keys-always-encrypted.md#creating-column-master-keys-in-azure-key-vault).
55
55
56
+
When using Azure Key Vault provider, the JDBC driver validates the column master key path against the list of trusted endpoints. Starting with driver version 8.2.2, this list is configurable: create "mssql-jdbc.properties" file in the working directory of the application, set the `AKVTrustedEndpoints` property to a semicolon-delimited list. If the value begins with a semicolon, it extends the default list; otherwise, it replaces the default list.
57
+
56
58
For the examples on this page, if you've created an Azure Key Vault based column master key and column encryption key by using SQL Server Management Studio, the T-SQL script to re-create them might look similar to this example with its own specific **KEY_PATH** and **ENCRYPTED_VALUE**:
0 commit comments