Migrate SQL Server Instances to Azure
Question
You deploy Azure App Service Web Apps that connect to on-premises Microsoft SQL Server instances by using Azure ExpressRoute. You plan to migrate the
SQL Server instances to Azure.
Migration of the SQL Server instances to Azure must:
-> Support automatic patching and version updates to SQL Server.
-> Provide automatic backup services.
-> Allow for high-availability of the instances.
-> Provide a native VNET with private IP addressing.
-> Encrypt all data in transit.
-> Be in a single-tenant environment with dedicated underlying infrastructure (compute, storage)
You need to migrate the SQL Server instances to Azure.
Which Azure service should you use?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.E
Azure SQL Database Managed Instance configured for Hybrid workloads. Use this topology if your Azure SQL Database Managed Instance is connected to your on-premises network. This approach provides the most simplified network routing and yields maximum data throughput during the migration.
https://docs.microsoft.com/en-us/azure/dms/resource-network-topologiesBased on the requirements listed in the question, the best option for migrating the on-premises SQL Server instances to Azure is to use Azure SQL Database Managed Instance (Option E).
Here's why:
Support automatic patching and version updates to SQL Server: Azure SQL Database Managed Instance is a fully managed database service that is built on top of SQL Server technology. As such, it receives automatic patching and version updates from Microsoft.
Provide automatic backup services: Azure SQL Database Managed Instance provides automated backups with a configurable retention period. You can also create manual backups and restore to any point in time within the retention period.
Allow for high-availability of the instances: Azure SQL Database Managed Instance provides automatic failover between multiple replicas for high availability. It also provides a service-level agreement (SLA) of 99.99% availability.
Provide a native VNET with private IP addressing: Azure SQL Database Managed Instance is deployed within a virtual network (VNET) that you can customize. You can use private IP addresses within the VNET to secure communication between the Managed Instance and other resources within the VNET.
Encrypt all data in transit: Azure SQL Database Managed Instance encrypts all data in transit using SSL/TLS. It also supports transparent data encryption (TDE) for encrypting data at rest.
Be in a single-tenant environment with dedicated underlying infrastructure (compute, storage): Azure SQL Database Managed Instance is a single-tenant service that provides dedicated compute and storage resources for each instance.
Option A (Azure SQL Database with elastic pools) is a good choice if you need a database-as-a-service (DBaaS) solution that can scale horizontally to support multiple databases with varying resource requirements. However, it does not provide the same level of control over the underlying infrastructure as Managed Instance.
Option B (SQL Server in Docker containers running on AKS) and Option D (SQL Server in a Docker container running on ACI) are both container-based solutions that provide some level of portability and flexibility. However, they require more management overhead and may not be the best choice if you need a fully managed service.
Option C (SQL Server Infrastructure-as-a-Service (IaaS) virtual machine) provides more control over the underlying infrastructure than Managed Instance, but it also requires more management overhead and may not be as scalable or cost-effective.
In summary, based on the requirements listed in the question, Azure SQL Database Managed Instance is the best option for migrating the on-premises SQL Server instances to Azure.
