How One Engineer Chose Azure SQL Managed Instance Over Azure SQL Database in Production
A software engineer documented the real-world reasoning behind choosing Azure SQL Managed Instance (SQL MI) over Azure SQL Database when migrating two enterprise applications from on-premises SQL Server to Azure. The production database was approximately 200 GB and supported three backend services while running over 25 SQL Server Agent jobs for scheduled batch and housekeeping tasks. A key requirement mandated that the database remain inaccessible from the public internet, accessible only via a private network on port 1433. The migration path proved decisive: SQL MI supports native .bak backup restores directly from Azure Blob Storage, whereas Azure SQL Database does not accept .bak files, requiring more complex alternatives like BACPAC imports. The engineer acknowledged formally defending the SQL MI choice during architecture review, citing compatibility, migration fidelity, and operational constraints as the primary factors over cost or familiarity.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in