Skip to content

Add support for MultiSubnetFailover connection property - #357

Closed
tylerclendenin wants to merge 1 commit into
tiberius-rs:mainfrom
tylerclendenin:mssql-multi-subnet-failover-connection-option
Closed

tylerclendenin wants to merge 1 commit into
tiberius-rs:mainfrom
tylerclendenin:mssql-multi-subnet-failover-connection-option

Conversation

@tylerclendenin

Copy link
Copy Markdown

When the MultiSubnetFailover=Yes property is added to the connection string, the TCP connection should be attempted for each resolved IP address in parallel rather than in sequence. This creates a race where the first connection to be established wins and becomes the target server.

https://learn.microsoft.com/en-us/sql/relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery?view=sql-server-ver15#connecting-with-multisubnetfailover

#356

When the MultiSubnetFailover=Yes property is added to the connection string, the TCP connection should be attempted for each resolved IP address in parallel rather than in sequence. This creates a race where the first connection to be established wins and becomes the target server.

https://learn.microsoft.com/en-us/sql/relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery?view=sql-server-ver15#connecting-with-multisubnetfailover
@MattJackson

Copy link
Copy Markdown
Contributor

Duplicate of #378 — MultiSubnetFailover landed in #442, shipped in tiberius v0.13.0. Thanks! Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants