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: CHANGELOG.md
+60-26Lines changed: 60 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,31 +88,6 @@ This update brings the following changes since [7.0.0-preview1.25257.1]
88
88
- Updated `System.Security.Cryptography.Pkcs` to v9.0.9 (net9)
89
89
- Updated `System.Text.Json` to v8.0.6 (net8), v9.0.9 (net9)
90
90
91
-
## [Stable Release 6.1.2] - 2025-10-07
92
-
93
-
This update brings the below changes over the previous stable release:
94
-
95
-
### Fixed
96
-
97
-
- Fixed an issue where initializing PerformanceCounters would throw `System.InvalidOperationException`[#3629](https://github.com/dotnet/sqlclient/pull/3629)
98
-
- Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. [#3651](https://github.com/dotnet/SqlClient/pull/3651)
99
-
- Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. [#3653](https://github.com/dotnet/SqlClient/pull/3653)
100
-
101
-
## [Stable release 6.0.3] - 2025-10-07
102
-
103
-
This update brings the below changes over the previous stable release:
104
-
105
-
### Fixed
106
-
107
-
- Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. [#3652](https://github.com/dotnet/SqlClient/pull/3652)
108
-
- Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. [#3654](https://github.com/dotnet/SqlClient/pull/3654)
109
-
110
-
### Changed
111
-
112
-
- Updated MSAL usage as per code compliance requirements [#3360](https://github.com/dotnet/SqlClient/pull/3360)
113
-
- Updated `SqlDecimal` implementation to improve code compliance [#3466](https://github.com/dotnet/SqlClient/pull/3466)
114
-
- Updated Azure.Identity and related dependencies [#3553](https://github.com/dotnet/SqlClient/pull/3553)
This update includes the following changes since the [6.1.2](release-notes/6.1/6.1.2.md) release:
156
+
157
+
### Added
158
+
159
+
#### App Context Switch for Ignoring Server-Provided Failover Partner
160
+
161
+
*What Changed:*
162
+
163
+
- A new app context switch `Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner` was introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR [#3702](https://github.com/dotnet/SqlClient/pull/3702).
164
+
165
+
*Who Benefits:*
166
+
167
+
- Applications connecting to SQL Server BAGs using TCP and custom ports, especially where the server's provided partner name lacks the protocol, host, or port. This avoids connection failures when the server-provided partner is incompatible or incomplete.
168
+
- Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.
169
+
170
+
*Impact:*
171
+
172
+
- If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:
- Then, ensure your connection string includes your preferred failover partner (with correct `tcp:host,port`) so that the client uses that instead of the server's suggestion.
179
+
- Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.
180
+
181
+
### Fixed
182
+
183
+
- Fixed an issue to ensure reliable metrics initialization during startup,
184
+
preventing missed telemetry when EventSource is enabled early.
This update includes the following changes since the [6.1.1](release-notes/6.1/6.1.1.md) release:
190
+
191
+
### Fixed
192
+
193
+
- Fixed an issue where initializing PerformanceCounters would throw `System.InvalidOperationException`[#3629](https://github.com/dotnet/sqlclient/pull/3629)
194
+
- Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. [#3651](https://github.com/dotnet/SqlClient/pull/3651)
195
+
- Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. [#3653](https://github.com/dotnet/SqlClient/pull/3653)
196
+
178
197
## [Stable Release 6.1.1] - 2025-08-14
179
198
180
-
This update includes the following changes since the [6.1.0](6.1.0.md) release:
199
+
This update includes the following changes since the [6.1.0](release-notes/6.1/6.1.0.md) release:
181
200
182
201
### Fixed
183
202
@@ -440,6 +459,21 @@ This update brings the following changes over the previous release:
- Test improvements include updates to test references, removal of hardcoded certificates, improved stability, and better coverage ([#3041](https://github.com/dotnet/sqlclient/pull/3041), [#3034](https://github.com/dotnet/sqlclient/pull/3034), [#3130](https://github.com/dotnet/sqlclient/pull/3130), [#3128](https://github.com/dotnet/sqlclient/pull/3128), [#3181](https://github.com/dotnet/sqlclient/pull/3181), [#3060](https://github.com/dotnet/sqlclient/pull/3060), [#3184](https://github.com/dotnet/sqlclient/pull/3184), [#3033](https://github.com/dotnet/sqlclient/pull/3033), [#3186](https://github.com/dotnet/sqlclient/pull/3186), [#3025](https://github.com/dotnet/sqlclient/pull/3025), [#3230](https://github.com/dotnet/sqlclient/pull/3230), [#3237](https://github.com/dotnet/sqlclient/pull/3237), [#3059](https://github.com/dotnet/sqlclient/pull/3059), [#3061](https://github.com/dotnet/sqlclient/pull/3061)).
442
461
462
+
## [Stable release 6.0.3] - 2025-10-07
463
+
464
+
This update brings the below changes over the previous stable release:
465
+
466
+
### Fixed
467
+
468
+
- Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. [#3652](https://github.com/dotnet/SqlClient/pull/3652)
469
+
- Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. [#3654](https://github.com/dotnet/SqlClient/pull/3654)
470
+
471
+
### Changed
472
+
473
+
- Updated MSAL usage as per code compliance requirements [#3360](https://github.com/dotnet/SqlClient/pull/3360)
474
+
- Updated `SqlDecimal` implementation to improve code compliance [#3466](https://github.com/dotnet/SqlClient/pull/3466)
475
+
- Updated Azure.Identity and related dependencies [#3553](https://github.com/dotnet/SqlClient/pull/3553)
476
+
443
477
## [Stable release 6.0.2] - 2025-04-25
444
478
445
479
This update brings the below changes over the previous release:
This update includes the following changes since the [6.1.2](6.1.2.md) release:
6
+
7
+
### Added
8
+
9
+
#### App Context Switch for Ignoring Server-Provided Failover Partner
10
+
11
+
*What Changed:*
12
+
13
+
- A new app context switch `Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner` was introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR [#3702](https://github.com/dotnet/SqlClient/pull/3702).
14
+
15
+
*Who Benefits:*
16
+
17
+
- Applications connecting to SQL Server BAGs using TCP and custom ports, especially where the server's provided partner name lacks the protocol, host, or port. This avoids connection failures when the server-provided partner is incompatible or incomplete.
18
+
- Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.
19
+
20
+
*Impact:*
21
+
22
+
- If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:
- Then, ensure your connection string includes your preferred failover partner (with correct `tcp:host,port`) so that the client uses that instead of the server's suggestion.
29
+
- Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.
30
+
31
+
### Fixed
32
+
33
+
- Fixed an issue to ensure reliable metrics initialization during startup,
34
+
preventing missed telemetry when EventSource is enabled early.
0 commit comments