Hi,
Azure SQL Databases on the Business Critical tier come with a 'built-in' readable secondary replica.
To connect to this replica, one must connect to the regular database, but specify ApplicationIntent=ReadOnly as part of the connection properties.
That is the only way to connect to this replica. It's not possible to connect to this replica by directly connecting to an alternative server (node) name. It has to be the same server name as the primary, like one does with an AG listener.
This brings us to the fact that currently SQL Sentry is not supporting this use case, as it's impossible to specify the ApplicationIntent=ReadOnly connection property.
Additionally, there could be an issue when adding both the primary and secondary replica of an Azure SQL Database, as it may cause a duplicate target issue.
Please add support for this use case to be able to monitor both the primary and the secondary replica of an Azure SQL Database on the Business-Critical tier.
Thanks
