A common setup when leveraging the cloud is to use the cloud for Disaster recovery (DR) purposes, some say it becomes a logical extension of your on-prem / data centre (makes more sense if you use express route and private endpoints).
You can use this approach for DR of your SQL based systems, look at the below image and you can see how. (Assume the left-hand side SQL icon is a VM on prem)
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.
In the last post we built an image of SQL server 2019 Linux hosted in Azure Container Instance for fast access to SQL server. So, your next question is probably, lets see some database action?
It is quite a common requirement to restore a copy of a database to the same Azure SQL server, you just issue a COPY OF command. What if you need to restore a copy to a different target Azure SQL server? Well its similar, just with a slight difference in that you need to refer back to the source server within your code.
When moving to a cloud model for your database stack no doubt you will be involved in a costing exercise. The good news is if you have Software Assurance with your existing licenses then expect some cost savings when moving to the cloud. You can save up to 70% cost when compared to a pay as you go model.
All About Tech 