We would to implemented MS SQL 2012 with AlwaysOn Availability Group for PAM 4.2 SP2 databases to have HA of these databases across two datacenters . Can we expect that jtds-1.3.1.jar driver will work correctly in such environment?
Unfortunately it does not appear that the jtds driver will support this.
From a quick review it appears that the AlwaysOn Availability Group was introduced recently, and is only available through their JDBC 4.0 driver: JDBC Driver Support for High Availability, Disaster Recovery
Where the jtds driver is built with the 3.0 MS JDBC driver as the baseline and does not have the option to set the required options: multiSubnetFailover, and applicationIntent
jTDS JDBC Driver
I am going to verify this internally and will let you know.
Do you have any new information?
I am sorry Milan, I have asked the engineering team to take a look at this, but I have not gotten any feedback that indicates we could support this functionality in the current jTDS JDBC driver we use for our SQL database connection.
I will follow up with them to see if they have had a chance to complete their research.
I have confirmed with the SE team that this is not a feature we can support with the JTDS Driver we ship with Process Automation.
Please open an IDEA for this to be considered for a future release of PAM; IDEA Board
thank you for the information.
Is this still the case with no support for Always on PAM 4.3.1? I know if a few clients who say they are using AWO with PAM.
But not sure if they used alternative jdbc drivers or if PAM node is passive untill SQL node 2 is activated.
We have our PAM cluster configured to use Always-On and have never had an issue with it. The PAM servers are configured to use the SQL Server listener, when we migrate the listener to another node the service is able to reconnect on its own. We used the provided drivers.
Thanks Grant that is great news. Very helpful.
Retrieving data ...