Visitar URL original
Switch MultiSubnetFailover on by default · Issue #4876 · dotnet/SqlClient · GitHub
Skip to content

Switch MultiSubnetFailover on by default #4876

Closed

Description

@mdaigle
No description provided.

Activity

  1. added this to the 7.1.0 milestone on Oct 20, 2026
  2. modified the milestones: 7.1.0, 8.0.0 on Oct 20, 2026
  3. github-actions commented on Oct 20, 2026

    @github-actions

    🔍 Triage Summary

    Check Result
    Issue type Task (sub-issue of #4494)
    Environment N/A, not a bug report
    Area Area\Azure Connectivity (connection/network behavior; also touches Area\Managed SNI / Area\Native SNI)
    Duplicates Potentially related: #4494 (parent issue)
    Regression Not indicated

    Analysis

    This tracks making MultiSubnetFailover=true the default, as the sub-task of #4494, which also deprecates TransparentNetworkIPResolution. It affects connection string defaults and the EnableMultiSubnetFailoverByDefault AppContext switch. Behavior-change risk is moderate (parallel connection attempts, interaction with failover partner and TNIR), so it needs a compatibility opt-out. Severity: P2.

    Next Steps

    Note: This triage summary is auto-generated by an AI agent. The analysis and suggestions above have not been verified by a human maintainer. Please treat as preliminary guidance only.

    Generated by SqlClient Issue Auto-Triage for #4876 · copilot · auto · 23 AIC · ⌖ 11.4 AIC · ⊞ 13.6K · ◷

  4. modified the milestones: 8.0.0, 8.1.0-preview1 on Oct 20, 2026
  5. moved this from To triage to In progress in SqlClient Boardon Oct 26, 2026
  6. moved this from In progress to Done in SqlClient Boardon Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Breaking Change 🔨Issues/PRs that are related with breaking API changes in the driver.

Type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions