Azure SQL Managed Instance

Overview

We use SQL Managed Instance when the workload needs SQL Server compatibility that Azure SQL Database does not provide: SQL Agent jobs, cross-database queries, or a lift-and-shift with limited code change. Instance size, networking, and collation are fixed before migration starts.

We move Agent jobs, logins, and linked servers in a documented order, and we compare checksums or row counts before cutover. The instance is placed on a subnet that your network team has already agreed.

What we deliver

• Managed instance sized and placed on an agreed subnet
• Migration of databases, Agent jobs, and logins
• Row-count or checksum comparison before cutover
• Backup, patching, and failover settings written into the runbook

Business benefits

• SQL Server workloads move with fewer application code changes
• Agent jobs keep their schedules instead of being rewritten as pipelines on day one
• The network path is agreed before the instance is built, not after