SQL Managed Instance Failover Within Region

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SQL Managed Instance Failover Within Region

L0 Member
Hey All,We are setting up Azure SQL Managed instances for the Venafi TPP product, and looking into the failover options available to mimic SQL Always On requirements in the design docs.We have built two SQL managed instances as Business Critical, but failover seems to be only available between two regions, not within zones of a single region. There is an option referred to as Zone Redundancy online but this is not available in the wizard, and shows in the export template as False by default, we are experimenting with a custom ARM template to try and turn this on.For Failover groups requirements, we have ensured that the DNS-prefix matches, by specifying the primary server upon building the secondary and they are a match in size, but they are not valid options in the drop down of Secondary Managed instance when configuring.Appreciate this may be more of an Azure question and we are investigating down that route as well, but as its to make a Venafi TPP compatible database solution, has anyone tried something similar with Azure SQL Managed Instances, and been able to accomplish this or something similar?Thanks,Ross.
2 REPLIES 2

L4 Transporter
Hi @RossSmith , thank you for starting this conversation in the community! I spoke to some ofmy teammates at Venafi that this question leans heavy on the Microsoft side. Its not ideal to point you elsewhere, but you might have better luck starting a thread in the Azure Community:https://azure.microsoft.com/en-us/support/community Ill keep this thread open in case other customers are able to jump in to share how theyve found a solution for a similar use case.

L0 Member
Hi Sofia, thanks for the reply. I have made progress with this since originally posting, it turns out that BC SQL MI is already configured for failover but it is not easily visible from within Azure. Following this article I was able to monitor the SQL primary and secondary instances in TSQL and force a manual failover via Azure Powershell to prove it worked. So it seems that the only requirement is the change to Business Critical and its all done for you. Creating a failover group would provided failover on failover, and we do not need this level or resilience. Might help someone in the future, so thought I would provide details. Manually initiate a failover on SQL Managed Instance - Azure SQL Managed Instance | Microsoft Learn
  • 124 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!