Allow support for adding multisubnet=true to sql connection string in sql always on scenarios
This is with respect to setting up the K2 Database for automatic failover via the SQL Always on feature:
In a scenario where both the primary and secondary replica are in different subnets we will configure the listener to have two IP addresses, one for each subnet. However, due to SQL configuration, once we failover to the secondary replica and need to hit secondary subnet, we will hit the SQL Availability group listener and try the subnet IPs configured for the listener in a serial manner. This causes the K2 product to run into connection timeout issues after a failover has occurred. Adding the MultiSubnet=True to the SQL connection string on K2 can resolve this and allow the connection to hit both of the IPs in parallel instead so we do not hit a connection timeout error. Per this MS Documentation (https://docs.microsoft.com/en-us/sql/relational-databases/native-client/features/sql-server-native-client-support-for-high-availability-disaster-recovery) . At this time in K2 we can add this parameter, but it requires modification of K2 Config files and can be easily overwritten by an upgrade or reconfigure. Request here is to make this a supported and configurable addition to how K2 product connects to it's SQL Database.
Evan Marcus
shared this idea