When to use PITR and Geo-Restore in Azure SQL MI or SQL DB
When designing a business continuity and disaster recovery (BCDR) strategy in Microsoft Azure, protecting your data from corruption, human error, …
SQLManagedInstance
PITR vs LTR differences in Azure SQL Managed Instance or SQL DB
Point-in-Time Restore (PITR) is designed for operational recovery and short-term resilience, and Long-Term Retention (LTR) is for storing or retaining …
Entra ID Connection Strings for Azure SQL Managed Instance
Moving away from legacy SQL authentication and adopting Microsoft Entra ID (formerly Azure Active Directory) is one of the best …
What is the difference between SQL Server and SQL Managed Instance?
In this blogpost, I will explain about the differences between the on prem SQL Server and the SQL Managed Instance …
Different database restore methods in Azure SQL MI
In the world of cloud-native databases, “Backup” is only half the story. The true value lies in Restoring the database …
Step-by-Step Guide: Creating an Azure SQL Managed Instance (Pay-As-You-Go & Free Offer)
Azure SQL Managed Instance (SQL MI) is the ideal “bridge” for organizations looking to move their on-premises SQL Server workloads …
Azure SQL MI Standby replica and Read replica functionality
Assume you have created Azure SQL Managed Instance in two regions (One is Primary region for read/write workloads, and another …
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 …
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. …