Support for Availability Groups in multisubnet environments?

Great question.  The details on the workaround get a little involved and I'd suggest you submit a support ticket so we can help you out with the details.  Essentially though, we use a jTDS driver (not MS jdbc driver) for SQL Server connections.  There were some fixes put in place to accommodate the multisubnet failover and applicationintent readonly scenarios to support them with the jTDS driver.  It will require us to send you the new updated driver and swap it out for the current one.  This new driver is packaged (though still not configured) with version 9.2 which is in RC currently.  Is there any possibility of upgrading DPA to the newest version?  GA is likely to happen shortly, so you may want to wait for that to occur?  Hope this helps.

Thanks for the quick and informative reply. We can wait for GA of 9.2. When you say it's not configured in 9.2, will that mean at the point we do upgrade there will be some manual non-standard setup for us to do to get it working?

Thanks

That's correct. 9.2 will ship still using the old jTDS driver. However, the jTDS with the fixes mentioned will be included in the bits, so a simple rename will be required and a restart of DPA.  There will be a KB article going live with 9.2 with details on how to accomplish this.

Hi.  Could you provide a link to the KB article please?  We'd like to enable the new jTDS driver so that we can connect to a listener publishing multiple IPs on different subnets.

Cheers

Here's the article I was referring to:  SolarWinds Knowledge Base :: Update to the latest jTDS driver for DPA 9.2

Wanted to update this thread and add some clarification.

First, the above KB link no longer works. It was removed. Before and up to DPA version 9.2 the flags you would set for applicationIntent=Readonly were not honored in DPA's out of the box driver. DPA 9.2 was where we shipped with a new version of jTDS that was not on by default. The steps told how to enable this driver that was not the default for DPA. DPA 9.2 is no longer supported and the steps are not required more modern versions of DPA in order to use this flag. For monitored SQL server instances you can add this property to the connection. In the options menu -> monitor setup tab -> update connection information -> Select the instance -> next -> Check the box next to "JDBC URL properties" applicationIntent=ReadOnly -> click next.

No changes to the driver are needed. Note:the jtds jdbc driver doesn't seem to handle applicationIntent=ReadOnly properly If a user tries to register an AG listener with ApplicationIntent=Readonly, DPA will still connect to the primary replica instead of a secondary read-only replica. So setting the applicationIntent=ReadOnly allows DPA to connect to an instance where read-only databases exist when you have connected to the instance directly not the listener.

Also mentioned in this thread is another property  MultiSubnetFailover=True DPA currently still does not work with this property it also didn't with the above listed jTDS driver. I have added a feature request for anyone needing this property here. Please upvote it.