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/big-data-cluster/release-notes-big-data-cluster.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: This article describes the latest updates and known issues for SQL
5
5
author: WilliamDAssafMSFT
6
6
ms.author: wiassaf
7
7
ms.reviewer: dacoelho
8
-
ms.date: 01/27/2022
8
+
ms.date: 01/31/2022
9
9
ms.topic: conceptual
10
10
ms.prod: sql
11
11
ms.technology: big-data-cluster
@@ -81,6 +81,22 @@ To install updates, see [How to upgrade [!INCLUDE[big-data-clusters-nover](../in
81
81
82
82
## Known issues
83
83
84
+
### HDFS copy of large files using azdata with random failures
85
+
86
+
-**Affected releases**: CU14
87
+
88
+
-**Issue and customer effect**: This was a bug causing random failures on `azdata bdc cp` commands between HDFS paths. The bug affects larger file copies more often.
89
+
90
+
-**Solution**: Update to Cumulative Update 15 (CU15).
91
+
92
+
### Log4j security
93
+
94
+
-**Affected releases**: None
95
+
96
+
-**Issue and customer effect**: After a thorough assessment of the SQL Server 2019 Big Data Clusters codebase, no risk associated with the log4j vulnerability reported in December was identified. CU15 includes an updated version of log4j (2.17) for the ElasticSearch instance in the control plane to ensure that image scan alerts are not triggered by static code analysis of Big Data Cluster containers.
97
+
98
+
-**Solution**: Always keep your big data cluster updated to the lastest release.
99
+
84
100
### Cluster upgrade from a CU8 and previous release to a post-CU9 release is not supported
Copy file name to clipboardExpand all lines: docs/big-data-cluster/release-notes-cumulative-updates-history.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,19 +5,30 @@ description: This article describes the updates and known issues for SQL Server
5
5
author: WilliamDAssafMSFT
6
6
ms.author: wiassaf
7
7
ms.reviewer: melqin,dacoelho
8
-
ms.date: 11/18/2021
8
+
ms.date: 01/31/2022
9
9
ms.topic: conceptual
10
10
ms.prod: sql
11
11
ms.technology: big-data-cluster
12
12
---
13
13
14
-
# SQL Server Big Data Clusters cumulative updates history
14
+
# SQL Server 2019 Big Data Clusters cumulative updates history
15
15
16
16
[!INCLUDE[SQL Server 2019](../includes/applies-to-version/sqlserver2019.md)]
17
17
18
18
The following release notes apply to [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ver15.md)]. The article lists cumulative update information for all the releases of [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)].
19
19
20
-
For the latest release notes, see [SQL Server Big Data Clusters platform release notes](release-notes-big-data-cluster.md).
20
+
For the latest release notes, see [SQL Server 2019 Big Data Clusters platform release notes](release-notes-big-data-cluster.md).
21
+
22
+
## <aid="cu15"></a> CU15 (January 2022)
23
+
24
+
Cumulative Update 15 (CU15) release for SQL Server 2019 Big Data Clusters.
25
+
26
+
|Package version | Image tag | Contents |
27
+
|-----|-----| ----- |
28
+
|15.0.4198.2|[2019-CU15-ubuntu-20.04]|[SQL Server Big Data Clusters Cumulative Update 15](release-notes-cumulative-update-15.md)|
29
+
30
+
> [!WARNING]
31
+
> On Cumulative Update 15, __the upgrade order is critical__. Upgrade your big data cluster to CU15 __before__ upgrading the Kubernetes cluster to version 1.21. If the Kubernetes cluster is upgraded to version 1.21 before BDC is upgraded to CU14 or CU15 then the cluster will end up in error state and the BDC upgrade will not succeed. In this case, reverting back to Kubernetes version 1.20 will fix the problem.
Copy file name to clipboardExpand all lines: docs/connect/odbc/bug-fixes.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "List of bugs fixed"
3
3
description: "This page contains a listing of bugs fixed in each release, starting with Microsoft ODBC Driver 17 for SQL Server."
4
4
ms.custom: ""
5
-
ms.date: "07/30/2021"
5
+
ms.date: "02/15/2022"
6
6
ms.prod: sql
7
7
ms.prod_service: connectivity
8
8
ms.reviewer: v-davidengel
@@ -19,6 +19,14 @@ manager: kenvh
19
19
20
20
This page contains a listing of bugs fixed in each release, starting with [!INCLUDE[msCoName](../../includes/msconame_md.md)] ODBC Driver 17 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
21
21
22
+
### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame_md.md)] ODBC Driver 18.0 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
23
+
24
+
- Fix UI issues where text was cut off and position of items was off.
25
+
- Fix issue with Active Directory Interactive login where attempting to login after closing the window of the first failure would automatically succeed if cached credentials were available.
26
+
- Fixed use of XADTC with Azure SQL Managed Instance.
27
+
- Fixed loss of Azure Active Directory authentication mode when reconnecting an idle connection.
28
+
- Fix an issue with federated authentication when using PingFed.
29
+
22
30
### Bug fixes in the [!INCLUDE[msCoName](../../includes/msconame_md.md)] ODBC Driver 17.8 for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]
23
31
24
32
- Fix for restrictions on connection string regarding usage of `UID` and `PWD` keywords
Copy file name to clipboardExpand all lines: docs/connect/odbc/data-classification.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ For managing sensitive data, SQL Server and Azure SQL Server introduced the abil
25
25
26
26
For more information on how to assign classification to columns, see [SQL Data Discovery and Classification](../../relational-databases/security/sql-data-discovery-and-classification.md).
27
27
28
-
Microsoft ODBC Driver 17.2 allows the retrieval of this metadata via SQLGetDescField using the SQL_CA_SS_DATA_CLASSIFICATION field identifier.
28
+
Microsoft ODBC Driver 17.2 or later allows the retrieval of this metadata via SQLGetDescField using the SQL_CA_SS_DATA_CLASSIFICATION field identifier.
Copy file name to clipboardExpand all lines: docs/connect/odbc/download-odbc-driver-for-sql-server.md
+13-12Lines changed: 13 additions & 12 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: Download ODBC Driver for SQL Server
3
3
description: Download the Microsoft ODBC Driver for SQL Server to develop native-code applications that connect to SQL Server and Azure SQL Database.
4
-
ms.date: 07/30/2021
4
+
ms.date: 02/15/2022
5
5
ms.prod: sql
6
6
ms.prod_service: connectivity
7
7
ms.reviewer: ""
@@ -16,21 +16,21 @@ ms.author: v-davidengel
16
16
17
17
[!INCLUDE[SQL Server Azure SQL Database Synapse Analytics PDW](../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
18
18
19
-
Microsoft ODBC Driver for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to SQL Server. Use Microsoft ODBC Driver 17 for SQL Server to create new applications or enhance existing applications that need to take advantage of newer SQL Server features.
19
+
Microsoft ODBC Driver for SQL Server is a single dynamic-link library (DLL) containing run-time support for applications using native-code APIs to connect to SQL Server. Use Microsoft ODBC Driver 18 for SQL Server to create new applications or enhance existing applications that need to take advantage of newer SQL Server features.
20
20
21
21
## Download for Windows
22
22
23
-
The redistributable installer for Microsoft ODBC Driver 17 for SQL Server installs the client components, which are required during run time to take advantage of newer SQL Server features. It optionally installs the header files needed to develop an application that uses the ODBC API. Starting with version 17.4.2, the installer also includes and installs the Microsoft Active Directory Authentication Library (ADAL.dll).
23
+
The redistributable installer for Microsoft ODBC Driver 18 for SQL Server installs the client components, which are required during run time to take advantage of newer SQL Server features. It optionally installs the header files needed to develop an application that uses the ODBC API. Starting with version 17.4.2, the installer also includes and installs the Microsoft Active Directory Authentication Library (ADAL.dll).
24
24
25
-
Version 17.8.1 is the latest general availability (GA) version. If you have a previous version of Microsoft ODBC Driver 17 for SQL Server installed, installing 17.8.1 upgrades it to 17.8.1.
25
+
Version 18.0.1.1 is the latest general availability (GA) version. The Microsoft ODBC Driver 18 for SQL Server will install side by side with Microsoft ODBC Driver 17 for SQL Server.
26
26
27
-
**[ Download Microsoft ODBC Driver 17 for SQL Server (x64)](https://go.microsoft.com/fwlink/?linkid=2168524)**
28
-
**[ Download Microsoft ODBC Driver 17 for SQL Server (x86)](https://go.microsoft.com/fwlink/?linkid=2168713)**
27
+
**[ Download Microsoft ODBC Driver 18 for SQL Server (x64)](https://go.microsoft.com/fwlink/?linkid=2186919)**
28
+
**[ Download Microsoft ODBC Driver 18 for SQL Server (x86)](https://go.microsoft.com/fwlink/?linkid=2187028)**
29
29
30
30
### Version information
31
31
32
-
- Release number: 17.8.1.1
33
-
- Released: July 30, 2021
32
+
- Release number: 18.0.1.1
33
+
- Released: February 15, 2022
34
34
35
35
> [!Note]
36
36
> If you are accessing this page from a non-English language version, and want to see the most up-to-date content, please select **Read in English** at the top of this page. You can download different languages from the US-English version site by selecting [available languages](#available-languages).
@@ -39,11 +39,11 @@ Version 17.8.1 is the latest general availability (GA) version. If you have a pr
39
39
40
40
This release of Microsoft ODBC Driver for SQL Server can be installed in the following languages:
41
41
42
-
Microsoft ODBC Driver 17.8.1 for SQL Server (x64):
Copy file name to clipboardExpand all lines: docs/connect/odbc/dsn-connection-string-attribute.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,12 +40,15 @@ The following table lists the available keywords and the attributes for each pla
40
40
|[Failover_Partner](../../relational-databases/native-client/applications/using-connection-string-keywords-with-sql-server-native-client.md)|[SQL_COPT_SS_FAILOVER_PARTNER](../../relational-databases/native-client-odbc-api/sqlsetconnectattr.md#sqlcoptssfailoverpartner)| W |
41
41
|[FailoverPartnerSPN](../../relational-databases/native-client/applications/using-connection-string-keywords-with-sql-server-native-client.md)|[SQL_COPT_SS_FAILOVER_PARTNER_SPN](../../relational-databases/native-client/odbc/service-principal-names-spns-in-client-connections-odbc.md)| W |
@@ -230,6 +233,10 @@ Specifies a file location of the private key for PEM or DER certificates that ar
230
233
231
234
In case if private key file is password protected then password keyword is required. If the password contains any "`,`" characters, an extra "`,`" character is added immediately after each one. For example, if the password is "`a,b,c`", the escaped password present in the connection string is "`a,,b,,c`".
232
235
236
+
### HostnameInCertificate
237
+
238
+
Specifies the hostname to be expected in the server's certificate when [encryption](../../database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine.md) is negotiated, if it is different from the default value derived from Addr/Address/Server.
239
+
233
240
### SQL_COPT_SS_ACCESS_TOKEN
234
241
235
242
Allows the use of an Azure Active Directory access token for authentication. For more information, see [Using Azure Active Directory](using-azure-active-directory.md).
For more information about XA transactions, see [Using XA Transactions](use-xa-with-dtc.md).
279
286
287
+
288
+
### SQL_COPT_SS_LONGASMAX
289
+
290
+
Allows long type data to be sent to servers as max type data.
291
+
292
+
| Attribute Value | Description |
293
+
|-|-|
294
+
|No|(Default) Don't convert long types to max types when sending. |
295
+
|Yes| Converts data from long types to max types when sending. |
296
+
297
+
280
298
### SQL_COPT_SS_SPID
281
299
282
300
Retrieves the server process ID of the connection. This property is equivalent to the T-SQL [@@SPID](../../t-sql/functions/spid-transact-sql.md) variable, except that it doesn't incur an extra round trip to the server.
Copy file name to clipboardExpand all lines: docs/connect/odbc/linux-mac/connecting-with-bcp.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Connecting with bcp
3
3
description: Learn the options and commands available in the bcp utility, available in the mssql-tools package on Linux and macOS.
4
4
ms.custom: ""
5
-
ms.date: 09/30/2021
5
+
ms.date: 02/15/2022
6
6
ms.prod: sql
7
7
ms.prod_service: connectivity
8
8
ms.reviewer: ""
@@ -121,6 +121,9 @@ Specifies the field terminator.
121
121
**-T**
122
122
Specifies that the `bcp` utility connect to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] with a trusted connection (integrated security).
123
123
124
+
**-u**
125
+
Trust server certificate. (available since `bcp` version 18)
126
+
124
127
**-U***login_id*
125
128
Specifies the login ID used to connect to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].
126
129
@@ -132,6 +135,9 @@ Uses Unicode characters to do the bulk copy operation.
132
135
133
136
In this release, Latin-1 and UTF-16 characters are supported.
134
137
138
+
**-Y**[s|m|o]
139
+
Specifies the connection encryption mode. The options are Strict, Mandatory, and Optional. Using -Y without any parameters uses the Mandatory encryption mode, and is equivalent to -Ym. (available since `bcp` version 18)
140
+
135
141
## Unavailable options
136
142
137
143
In the current release, the following syntax and options aren't available:
0 commit comments