Bump dbup-sqlserver and Microsoft.Data.SqlClient

[dependabot]

Updated dbup-sqlserver from 6.0.16 to 7.2.0.

Release notes

Sourced from dbup-sqlserver's releases.

7.2.0

What's Changed

• Accept a Func instead of a pre-created connection by @​droyad in Accept a Func<SqlConnection> instead of a pre-created connection DbUp/dbup-sqlserver#34

Full Changelog: DbUp/dbup-sqlserver@7.1.0...7.2.0

7.1.0

What's Changed

• Breaking Change (only due to third party major version bump) Update Microsoft.Data.SqlClient from 5.2.2 to 6.1.2 by @​droyad in Update Microsoft.Data.SqlClient from 5.2.2 to 6.1.2 DbUp/dbup-sqlserver#27
• Allow use of an existing SQL Connection by @​droyad in Allow use of an existing SQL Connection DbUp/dbup-sqlserver#31
• Updated DbUp to 6.1.1 and patches to other libraries by @​droyad in Updated DbUp to 6.1.1 and patches to other libraries DbUp/dbup-sqlserver#30

Full Changelog: DbUp/dbup-sqlserver@6.0.16...7.1.0

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 6.1.1 to 6.1.4.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

6.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.
  ... (truncated)

6.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)

Target Platform Support

• .NET Framework 4.6.2+ (Windows ARM64, Windows x86, Windows x64)
• .NET 8.0+ (Windows x86, Windows x64, Windows ARM64, Windows ARM, Linux, macOS)

Dependencies

.NET Framework 4.6.2+

• Azure.Core 1.47.1
• Azure.Identity 1.14.2
• Microsoft.Bcl.Cryptography 8.0.0
• Microsoft.Data.SqlClient.SNI 6.0.2
• Microsoft.Extensions.Caching.Memory 8.0.1
• Microsoft.IdentityModel.JsonWebTokens 7.7.1
• Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
• System.Buffers 4.5.1
• System.Data.Common 4.3.0
• System.Security.Cryptography.Pkcs 8.0.1
• System.Text.Encodings.Web 8.0.0
  ... (truncated)

6.1.2

This update brings the below changes over the previous stable release:

Fixed

• Fixed an issue where initializing PerformanceCounters would throw System.InvalidOperationException #​3629
• Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. #​3651
• Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. #​3653

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.

[bgard68]

Closing as superseded.

Microsoft.Data.SqlClient on main is already 6.1.6 via the grouped minor/patch update (#24), which is newer than the 6.1.4 proposed here - so the only remaining change in this PR is dbup-sqlserver 6.0.16 -> 7.2.0, a major.

That major deserves its own PR and its own verification: DbUp 7.x is where the migration runner's API can shift, and our migrations run at application startup. Dependabot will re-propose it separately.

Note for whoever picks it up: NuGet updates here also require regenerating the committed packages.lock.json (dotnet restore --force-evaluate) or CI's locked-mode restore fails with NU1004 - see SECURITY-POSTURE.md.

🤖 Generated with Claude Code