You manage an application instance. The application consumes data from multiple databases. Application code references database tables using a combination of the server, database, and table name.
You need to migrate the application instance to Azure.
What are two possible ways to achieve this goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Click on the arrows to vote for the correct answer
A. B. C. D.AD
A: Access your SQL Server data seamlessly regardless of whether it's on-premises or stretched to the cloud. You set the policy that determines where data is stored, and SQL Server handles the data movement in the background. The entire table is always online and queryable. And, Stretch Database doesn't require any changes to existing queries or applications - the location of the data is completely transparent to the application.
D: The managed instance deployment model is designed for customers looking to migrate a large number of apps from on-premises or IaaS, self-built, or ISV provided environment to fully managed PaaS cloud environment, with as low migration effort as possible. Using the fully automated Data Migration Service (DMS) in Azure, customers can lift and shift their on-premises SQL Server to a managed instance that offers compatibility with SQL Server on-premises and complete isolation of customer instances with native VNet support.
https://docs.microsoft.com/en-us/sql/sql-server/stretch-database/stretch-database https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instanceThere are multiple ways to migrate an application that consumes data from multiple databases to Azure. Two possible solutions are:
A. SQL Server Stretch Database: This solution allows you to migrate part of your on-premises database to Azure SQL Database. Specifically, you can stretch your database to Azure SQL Database without changing the application code. With this solution, you can keep your most important and frequently accessed data on-premises and move historical or less frequently accessed data to Azure SQL Database. This can help you reduce the storage and maintenance cost of your on-premises database. Additionally, you can still use your current SQL Server tools and management practices to manage your database.
B. SQL Server in an Azure virtual machine: With this solution, you can create a virtual machine in Azure and install SQL Server on it. You can then migrate your on-premises database to the SQL Server instance running on the Azure virtual machine. The advantage of this solution is that you have full control over the SQL Server instance, including the version, configuration, and maintenance. Additionally, you can use your existing SQL Server management tools to manage the SQL Server instance. However, you will need to manage the virtual machine, including the operating system and patches.
C. Azure SQL Database: This solution provides a fully managed, scalable, and secure relational database service in Azure. You can create an Azure SQL Database and migrate your on-premises database to it. Azure SQL Database supports most of the SQL Server features, including Transact-SQL, stored procedures, and triggers. Additionally, Azure SQL Database provides built-in high availability and disaster recovery capabilities, automatic backup and patching, and monitoring and alerting. However, you may need to modify your application code to use Azure SQL Database.
D. SQL Managed Instance: This solution provides a fully managed, compatibility-level preserving instance of SQL Server in Azure. With SQL Managed Instance, you can migrate your on-premises SQL Server instance to Azure without changing your application code. SQL Managed Instance supports most of the SQL Server features, including cross-database queries, SQL Server Agent, and Distributed Transaction Coordinator (DTC). Additionally, SQL Managed Instance provides built-in high availability and disaster recovery capabilities, automatic backup and patching, and monitoring and alerting. However, you may need to adjust your database configuration and migration approach to work with SQL Managed Instance.