SQL Server is not the only database you build and deploy into Azure. Another very popular option is MySQL. Going back many years, this was actually my first database technology that I ever used so its great seeing it within the Azure eco-system, it has always been a popular choice as seen below.
This is our current setup shown below.
There is not much to failing over with Managed Instances, from experience it is similar to that of Azure SQL Database.
In case you are not aware Microsoft have now deployed a new change to SQL Managed Instances within the tier types. In certain regions ( shown later) you can select something different to that of gen 5 hardware now called standard – more specifically premium series where you have 2 options as shown below – a much wanted request!
With SQL Managed Instance you will need to consider your configuration requirements in terms of core count for the CPU and memory, which we all know that the MIN/MAX settings for SQL is so important.
No doubt there will be times where you need to scale up the actual instance in terms of vCores but also you may want to move across tiers (for example General Purpose to Business Critical). If you remember a few blog posts ago I said it was really important to plan for these activities during the build phase, more specifically get the subnet range right. If you done that then you will be fine.
So how do you do this? Easy. Let’s start with the Azure Portal.
All About Tech 