Tailspin Toys is the developer of several popular online video games. Founded in 2010, the company has experienced exponential growth since releasing the first installment of their most popular game franchise to include online multiplayer gameplay. They have since built upon this success by adding online capabilities to the majority of their game portfolio.
To facilitate online gameplay, they host gaming services on-premises using rented hardware. Adding online gameplay has dramatically increased the popularity of their games, but the rapid increase in demand for their services has made supporting the current setup problematic.
Tailspin Toys is hoping that migrating their services from on-premises to the cloud. They are looking for a proof-of-concept (PoC) for migrating the VMs and databases of a single game into the cloud. Their end goal is to migrate their whole service to Azure, so they would also like to understand better what the overall architecture might look after migrating to the cloud.
February 2020
- Database administrators
- SQL/Database developers
- Application developers
In this workshop, you learn how to develop a plan for migrating on-premises VMs and SQL Server 2008 R2 databases into a combination of IaaS and PaaS services in Azure. You perform assessments to reveal any feature parity and compatibility issues between the customer's SQL Server 2008 R2 databases and the managed database offerings in Azure. You then design a solution for migrating their existing on-premises services, including VMs and databases, into Azure, with minimal or no down-time. Finally, you demonstrate some of the advanced SQL features available in Azure to improve security and performance in the customer's applications.
At the end of this workshop, you will be better able to design and implement a cloud migration solution for business-critical applications and databases.
In this whiteboard design session, you work in a group to develop a plan for migrating on-premises VMs and SQL Server 2008 R2 databases into a combination of IaaS and PaaS services in Azure. You provide guidance on performing assessments to reveal any feature parity and compatibility issues between the customer's SQL Server 2008 R2 databases and the managed database offerings in Azure. You then design a solution for migrating their on-premises services, including VMs and databases, into Azure, with minimal or no down-time. Finally, you provide guidance on how to enable some of the advanced SQL features available in Azure to improve security and performance in the customer's applications.
At the end of this whiteboard design session, you will be better able to design a cloud migration solution for business-critical applications and databases.
In this hands-on lab, you implement a proof-of-concept (PoC) for migrating an on-premises SQL Server 2008 R2 database into Azure SQL Database Managed Instance (SQL MI). You perform assessments to reveal any feature parity and compatibility issues between the on-premises SQL Server 2008 R2 database and the managed database offerings in Azure. You then migrate the customer's on-premises gamer information web application and database into Azure, with minimal to no down-time. Finally, you enable some of the advanced SQL features available in SQL MI to improve security and performance in the customer's application.
At the end of this hands-on lab, you will be better able to implement a cloud migration solution for business-critical applications and databases.
- Azure SQL Database Managed Instance (SQL MI)
- Azure SQL Database (SQL DB)
- Azure Database Migration Service (DMS)
- Microsoft Data Migration Assistant (DMA)
- Azure App Service
- SQL Server
- SQL Server on VM
- SQL Server Management Studio (SSMS)
- Azure virtual machines
- Visual Studio 2019
- Azure virtual network
- Azure virtual network gateway
- Azure Blob Storage account
We welcome feedback and comments from Microsoft SMEs & learning partners who deliver MCWs.
Having trouble?
- First, verify you have followed all written lab instructions (including the Before the Hands-on lab document).
- Next, submit an issue with a detailed description of the problem.
- Do not submit pull requests. Our content authors will make all changes and submit pull requests for approval.
If you are planning to present a workshop, review and test the materials early! We recommend at least two weeks prior.