Fix Azure SQL MI to SQL DB Linked Server Errors Using Entra ID

Welcome back to another deep dive on Cloud Nerchuko. If you have ever tried setting up a Linked Server from an Azure SQL Managed Instance (MI) to an Azure SQL Database using a System-Assigned Managed Identity, you know that Azure networking can sometimes feel like navigating a maze of invisible walls. Recently, I went through … Read more

How to Create Linked Servers in SQL MI Using Entra ID

When migrating to Azure SQL Managed Instance (SQL MI), Linked Servers often become a critical requirement for maintaining cross-environment connectivity. They act as a vital bridge, allowing you to execute queries or call stored procedures across diverse environments whether that is an on-premises database, Azure SQL DB, SQL Server on an Azure VM, or another … Read more

Azure SQL Managed Instance RTO and RPO details

In the modern digital landscape, applications rely on databases to remain functional at all times. However, unforeseen events such as hardware failures, regional power outages, or accidental human errors can disrupt normal operations. To protect data and ensure business continuity, Microsoft Azure SQL Managed Instance offers a robust set of recovery tools. Here are the … Read more

Scaling Downtime in SQL Managed Instance

In this post, I am going to share my hands-on experience measuring the actual downtime you can expect when scaling an Azure SQL Managed Instance (SQL MI) up or down. Specifically, I will be walking you through a real-world test of scaling storage size and vCores using a free-tier SQL Managed Instance. I will append … Read more

Check Replication status between SQL MI Primary and Secondary

Ensuring that SQL Managed Instance (SQL MI) replication is properly synchronized between the primary and secondary instances is critical for maintaining high availability, disaster recovery, and data integrity. Replication allows your databases to stay consistent across environments, but if synchronization fails, it can lead to downtime or data loss. The actual article where Microsoft published … Read more

You need to create a pair of azure sql managed instances in an auto-failover group. Where do you deploy the primary and secondary instance?

To deploy a pair of Azure SQL Managed Instances (MI) in an auto-failover group, you must deploy the primary and secondary instances in different Azure regions. While technically you can choose any two regions, the standard best practice is to use Azure Paired Regions (e.g., East US and West US). Failover Groups Overview & Best … Read more

Azure SQL MI Failover Group Pre-Requisites

In this blogpost, you will understand about the pre-requisites to create a failover group successfully in Azure SQL Managed Instance. If you are designing a Disaster Recovery (DR) strategy for Azure SQL Managed Instance (SQL MI), you have likely settled on Auto-Failover Groups as your solution. It’s the gold standard: it gives you a read-write … Read more