Feedback
Did this article resolve your question/issue?

   

Article

Does the 5.1 Connect for JDBC SQL Server Driver support Always ON and Multisubnet failover?

Information

 
TitleDoes the 5.1 Connect for JDBC SQL Server Driver support Always ON and Multisubnet failover?
URL Namedoes-the-5-1-connect-for-jdbc-sql-server-driver-support-always-on-and-multisubnet-failover
Article Number000159338
EnvironmentProduct: Connect for JDBC SQL Server Driver
Version: 5.1
O/S: All Supported
Databaes: SQL Server
Application: N/A
Question/Problem Description
Does the 5.1 Connect for JDBC SQL Server Driver support Always ON and Multisubnet failover?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Support Always On and Multisubnet failover is NOT implemented in version 5.1 of the Connect for JDBC SQL Server Driver.  

Upgrade to version 6.0.
Workaround
Notes
Last Modified Date7/15/2019 3:20 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.