There is a setting / feature in Managed Instance worth talking about, it is called SQL Trust Groups.
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.
If you have been following me for a while you will know that I really like the Fail over groups within Azure SQL DB and it is no different to when applying it to Managed Instances. If you want a rock-solid DR plan, this is the way forward.
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.
So in the last blog we confirmed that we could move to SQL MI via some analysis, this is now time to actually do a backup and restore via URLs to move data.
Now that we have a Managed Instance built, the next question is how do we get data across? I will break this up into separate posts but the lesson for this blog post is ANALYSIS FIRST!
Honestly, there will probably be less work needed to make the data compatible for Managed Instance, this is very true if comparing to the true PaaS offering of Azure SQL DB, but we should always check before migrating.
First step login into the Azure portal and find SQL Managed Instance and click create. Yes you can find these tutorials all online but this is my thinking and opinions on some key areas.
After many years working with different “flavours” of SQL server in Azure from its true PaaS form to SQL server in AKS (Azure Kubernetes Service) it’s time to look at SQL Managed Instances – you will notice that I call it SQL MI.