chore(deps): update dependency microsoft.data.sqlclient to 6.1.4

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.Data.SqlClient (source)	6.1.2 → 6.1.4

---

Release Notes

dotnet/sqlclient (Microsoft.Data.SqlClient)

v6.1.4

This update brings the following changes since the 6.1.3 release:

Fixed

• Fixed NullReferenceException issue with SqlDataAdapter when processing batch scenarios where certain SQL RPC calls may not include system parameters.
  (#​3877)
• Fixed connection pooling issue where extra connection deactivation was causing active connection counts to go negative.
  (#​3776)

Added

AppContext Switch for enabling MultiSubnetFailover

What Changed:

• Added new AppContext switch Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault to set MultiSubnetFailover=true by default in connection string.
  (#​3851)

Who Benefits:

• Applications that need MultiSubnetFailover enabled globally without modifying connection strings.

Impact:

• Applications can now enable MultiSubnetFailover globally using one of the following methods:

// In application code
AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault", true);

// In runtimeconfig.json
{
  "configProperties": {
    "Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault": true
  }
}

<!-- In App.Config -->
<runtime>
  <AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault=true" />
</runtime>

Changed

• Optimized SqlStatistics execution timing by using Environment.TickCount instead of more expensive timing mechanisms.
  (#​3830)
• Updated dependencies (#​3843):
  • .NET Framework 4.6.2:
    • Azure.Core 1.47.1 -> 1.50.0
    • Azure.Identity 1.14.2 -> 1.17.1
    • Microsoft.Identity.Client 4.80.0 - Added
    • System.Buffers 4.5.1 -> 4.6.1
    • System.Diagnostics.DiagnosticSource 8.0.1 - Added
    • System.IdentityModel.Tokens.Jwt 7.7.1 - Added
    • System.Memory 4.6.3 - Added
    • System.Text.Json 8.0.5 -> 8.0.6
    • System.Text.RegularExpressions 4.3.1 - Added
    • Microsoft.Bcl.Cryptography - Removed
    • System.Text.Encodings.Web - Removed
  • .NET 8.0:
    • Azure.Core 1.47.1 -> 1.50.0
    • Azure.Identity 1.14.2 -> 1.17.1
    • Microsoft.Identity.Client 4.80.0 - Added
    • System.Diagnostics.DiagnosticSource 8.0.1 - Added
    • System.IdentityModel.Tokens.Jwt 7.7.1 - Added
    • Microsoft.Bcl.Cryptography - Removed
    • System.Text.Json - Removed
  • .NET 9.0:
    • Azure.Core 1.47.1 -> 1.50.0
    • Azure.Identity 1.14.2 -> 1.17.1
    • Microsoft.Extensions.Caching.Memory 9.0.4 -> 9.0.11
    • Microsoft.Identity.Client 4.80.0 - Added
    • System.Configuration.ConfigurationManager 9.0.4 -> 9.0.11
    • System.Diagnostics.DiagnosticSource 9.0.11 - Added
    • System.IdentityModel.Tokens.Jwt 7.7.1 - Added
    • System.Security.Cryptography.Pkcs 9.0.4 -> 9.0.11
    • Microsoft.Bcl.Cryptography - Removed
    • System.Text.Json - Removed
  • .NET Standard 2.0:
    • Azure.Core 1.47.1 -> 1.50.0
    • Azure.Identity 1.14.2 -> 1.17.1
    • Microsoft.Extensions.Caching.Memory 9.0.4 -> 8.0.1
    • Microsoft.Identity.Client 4.80.0 - Added
    • System.Configuration.ConfigurationManager 9.0.4 -> 8.0.1
    • System.Diagnostics.DiagnosticSource 8.0.1 - Added
    • System.IdentityModel.Tokens.Jwt 7.7.1 - Added
    • System.Security.Cryptography.Pkcs 9.0.4 -> 8.0.1
    • System.Text.Json 9.0.5 -> 8.0.6
    • Microsoft.Bcl.Cryptography - Removed

v6.1.3

This update includes the following changes since the 6.1.2 release:

Added

App Context Switch for Ignoring Server-Provided Failover Partner

What Changed:

• 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.

Who Benefits:

• 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.
• Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.

Impact:

• 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:

AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner", true);

• 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.
• Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.

Fixed

• Fixed an issue to ensure reliable metrics initialization during startup,
  preventing missed telemetry when EventSource is enabled early.
  (#​3718)

---

Configuration

📅 Schedule: Branch creation - "before 8am" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the Microsoft.Data.SqlClient library to its latest version, 6.1.4. This update is crucial for incorporating recent bug fixes, performance enhancements, and new configuration options that improve the stability and flexibility of SQL Server connections. Key improvements include resolving data adapter and connection pooling issues, and providing new AppContext switches for better control over failover behavior and multi-subnet configurations.

Highlights

• Dependency Update: The Microsoft.Data.SqlClient package has been updated from version 6.1.2 to 6.1.4.
• Bug Fixes: This update includes fixes for a NullReferenceException issue with SqlDataAdapter during batch processing and a connection pooling issue that could lead to negative active connection counts.
• New AppContext Switches: Two new AppContext switches have been introduced: one to enable MultiSubnetFailover by default (Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault) and another (from 6.1.3) to ignore server-provided failover partners (Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner).
• Performance Optimization: The SqlStatistics execution timing has been optimized by using Environment.TickCount.

Changelog

• cloud-sql/sql-server/CloudSql.csproj
  • Updated the Microsoft.Data.SqlClient package reference from 6.1.2 to 6.1.4.

Activity

• This pull request was automatically generated by Renovate Bot to update a dependency. No human activity has been recorded yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the Microsoft.Data.SqlClient dependency from version 6.1.2 to 6.1.4. This is a beneficial maintenance update that, according to the release notes, includes several bug fixes related to SqlDataAdapter and connection pooling. The change is straightforward and I see no issues with it.