The Business Critical tier of Azure SQL Managed Instance offers the read-scale out feature enabling you to distribute read-only workloads such as reporting and analytics across built-in replicated secondary replicas within the same region. You can use this by specifying ApplicationIntent=ReadOnly in your connection string, your queries are then automatically routed to these replicas.
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?
One of the features Microsoft wants us to use for Azure SQL Database is Automatic Tuning. Automatic Tuning is a feature where you can think of it as entering the world of self-running and self-tuning databases.
It is said to be safe, reliable and proven using complex algorithms and built-in intelligence where it can do the following (see this link for more details: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automatic-tuning)
It is always a good idea to test your failover processes when you have setup failover groups in Azure. I have the following setup:
I was creating some demo non-clustered indexes in one of my Azure SQL Databases and received the following warning when I executed this code:
All About Tech 