2

We have 2 SQL Servers on premises, combined into Availability Group. We want to install Windows updates, which will most likely require a reboot of virtual machines, and we are going to use the rolling update technique (update secondary replica; fail over to secondary so it becomes primary; update former primary)

Applications that are located on the on-premises web server, are going to be fine, since web-servers' connection strings are pointed to AG Listener

But we also have apps running in Azure, which are connecting to the on-premises database (to the primary replica directly) using hybrid connections. Azure Apps are going to be down if the primary replica is down.

Question: is there any way that we can point Azure hybrid connections to AG listener ? Or at least redirect hybrid connection to secondary replica if primary is not available for 1-2 mins ?

1

1 Answer 1

1

You should be able to connect to the AG listener from Azure to On-premises or vice versa--though it's not as straight forward as you might think. Here's one of the best article's I've ready today on how to do it.

https://www.concurrency.com/blog/w/creating-a-listener-for-a-multi-subnet-hybrid-or-a

When the AG primary node is on-premises (or in Azure), you should be able to connect to the listener. So you're relying on Azure DNS to do it's job properly and resolve your SQL Azure node correctly. Haven't tried it myself--sounds awesome!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.