Skip to main content
Database Administrators

Return to Answer

Grammar and clarification
Source Link
edit approved Dec 7, 2018 at 16:23
Tony Hinkle
edit approved Dec 7, 2018 at 16:23
Tony Hinkle
  • 8k
  • 1
  • 22
  • 46

When MultiSubnetFailover=True is set, the sql server native clientSQL Server Native Client will aggressively retry the TCP connection.

So in

  • a multi subnet-subnet scenario, it will attempt connections in parallel. Which, which you already know.

  • a Single Subnetsingle subnet scenario, it will aggressively retry the tcpTCP connection faster than the OS default TCP retransmit intervals. Sointerval, so your AG failover and reconnect time after an AG failover will be improved.

When MultiSubnetFailover=True is set, the sql server native client will aggressively retry the TCP connection.

So in

  • a multi subnet scenario, it will attempt connections in parallel. Which you already know.

  • a Single Subnet scenario, it will aggressively retry the tcp connection faster than the OS default TCP retransmit intervals. So your AG failover and reconnect time will be improved.

When MultiSubnetFailover=True is set, SQL Server Native Client will aggressively retry the TCP connection.

So in

  • a multi-subnet scenario, it will attempt connections in parallel, which you already know.

  • a single subnet scenario, it will aggressively retry the TCP connection faster than the OS default TCP retransmit interval, so your reconnect time after an AG failover will be improved.

Source Link
Kin Shah
Kin Shah
  • 62.4k
  • 6
  • 122
  • 240

When MultiSubnetFailover=True is set, the sql server native client will aggressively retry the TCP connection.

So in

  • a multi subnet scenario, it will attempt connections in parallel. Which you already know.

  • a Single Subnet scenario, it will aggressively retry the tcp connection faster than the OS default TCP retransmit intervals. So your AG failover and reconnect time will be improved.