Multisubnet failover does not support on client side, what we can do next ?

Question

Hi,

I've a plan to deploy mssql 2019 (standard) at DC & DR site (different subnet). And I need to set up always on for both database by using multisubnet failover, but our application does not support multisubnet failover. [our app using JDBC, but it does not support multisubnet]

So if we enable always on without multisubnet failover, what will happen in case of fail-over ? Do we need to change a DNS record when primary DB goes down ?

Thank you.

Answer 1

Hi @wcsky ,

Agree with Tom.
Please see this link about SQL Server Multi-Subnet Clustering:
https://learn.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/sql-server-multi-subnet-clustering-sql-server?redirectedfrom=MSDN&view=sql-server-ver15
There are some examples of SQL Server FCIs that use multiple subnets at the front of this document which may help you understand.
If you're using client libraries that support the MultiSubnetFailover connection option in the connection string, you can optimize availability group failover to a different subnet by setting MultiSubnetFailover to "True".

Best regards,
Seeya

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

You should be able to upgrade to the current JDBC driver which supports multi-subnet failover.

https://learn.microsoft.com/en-us/sql/connect/jdbc/jdbc-driver-support-for-high-availability-disaster-recovery?view=sql-server-ver15