AZ-305 Question 63
Single answerYour organization currently runs a Microsoft SQL Server environment on-premises that uses cross-database queries, SQL Agent jobs, and stored procedures. You want to migrate this environment to Azure, but you need to retain these features with minimal refactoring or code changes. Which Azure service should you choose to host your relational data?
- A
Azure SQL Database
- B
Azure SQL Managed Instance
- C
Azure Database for PostgreSQL
- D
Azure Cosmos DB (SQL API)
Show answer and explanation
Correct answer: B
Explanation
When migrating complex SQL Server workloads to Azure with requirements like cross-database queries, SQL Agent jobs, and stored procedures, Azure SQL Managed Instance is the recommended choice. It offers near full compatibility with the SQL Server engine, enabling minimal refactoring. For more details, refer to the official Microsoft documentation on Azure SQL Managed Instance: https://docs.microsoft.com/azure/azure-sql/managed-instance/
- A. Incorrect.
Azure SQL Database is a fully managed service designed for modern cloud applications, but it has certain limitations compared to a full SQL Server instance. It does not support some features like cross-database queries and SQL Agent jobs natively, so it may require more code refactoring.
- B. Correct.
Azure SQL Managed Instance is nearly 100% compatible with the on-premises SQL Server engine, supporting cross-database queries, SQL Agent jobs, and stored procedures. This makes it the best choice for migrating existing SQL Server workloads with minimal changes.
- C. Incorrect.
Azure Database for PostgreSQL is a managed service for PostgreSQL databases. While it’s a strong open-source relational platform, migrating a SQL Server environment to PostgreSQL would typically require significant schema and code modifications, which does not suit the minimal-change requirement.
- D. Incorrect.
Azure Cosmos DB with the SQL API is a NoSQL database that uses a SQL-like query language. It is not intended for traditional relational SQL features (e.g., cross-database transactions, T-SQL stored procedures) and would require a major redesign of your data model.