Skip to content

Commit

Permalink
"MultiSubnetfailover" is no longer required (dotnet#3992)
Browse files Browse the repository at this point in the history
* "MultiSubnetfailover" is no longer required

See this blog post https://blogs.msdn.microsoft.com/dotnet/2015/11/30/net-framework-4-6-1-is-now-available/

* Resspond to review feedback
  • Loading branch information
ErikEJ authored and Ron Petrusha committed Jan 18, 2018
1 parent fa229ae commit ce9771b
Showing 1 changed file with 3 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,9 @@ This topic discusses SqlClient support (added in [!INCLUDE[net_v45](../../../../
1. <xref:System.Data.SqlClient.SqlConnectionStringBuilder.ApplicationIntent%2A>

2. <xref:System.Data.SqlClient.SqlConnectionStringBuilder.MultiSubnetFailover%2A>

> [!NOTE]
> Setting `MultiSubnetFailover` to `true` isn't required with [!INCLUDE[net_v461](../../../../../includes/net-v461-md.md)]) or later versions.
## Connecting With MultiSubnetFailover
Always specify `MultiSubnetFailover=True` when connecting to a [!INCLUDE[ssNoVersion](../../../../../includes/ssnoversion-md.md)] 2012 availability group listener or [!INCLUDE[ssNoVersion](../../../../../includes/ssnoversion-md.md)] 2012 Failover Cluster Instance. `MultiSubnetFailover` enables faster failover for all Availability Groups and or Failover Cluster Instance in [!INCLUDE[ssNoVersion](../../../../../includes/ssnoversion-md.md)] 2012 and will significantly reduce failover time for single and multi-subnet AlwaysOn topologies. During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, will aggressively retry the TCP connection.
Expand Down

0 comments on commit ce9771b

Please sign in to comment.