Welcome to last post from series about SQL Server migration to Azure SQL.
Previous posts covered following topics:
Post 1:
- Why migrate SQL Server to Azure SQL?
- Migration strategy
- Azure SQL family
- Migration paths
Post 2:
- Migration process and steps (Discover, Asses, Migrate, Cutover, Optimize)
The last episode focus on costs optimization i.e. Azure Hybrid Benefit, Reserved Instance and briefly describes tools and services which supports migration process.
Optimize the costs
After migrating SQL Server to Azure SQL, two additional cost optimization options are worth considering: Azure Hybrid Benefit and Reserved Instances.
Azure Hybrid Benefit
Already acquired SQL Server licenses should not prevent you from migration. Microsoft offers Azure Hybrid Benefit, which allows you to use your existing SQL Server licenses and Software Assurance benefits to move your workloads to Azure SQL and reduce costs.
The most important key points of Azure Hybrid Benefit include:
- Cost savings, simplified licensing, flexibility, compatibility
- Up to 180 days of dual-use rights between on-premises and Azure.
- Move licenses to IAAS (Azure SQL VM) or PAAS (Azure SQL Managed Instance or Azure SQL Database)
- License conversion ratio up to 1:4
The exact number of Eligible Azure SQL VMs or Azure SQL instances can be estimated used dedicated calculator. Additional information about the potential monthly and annual savings that can be achieved with Azure Hybrid Benefit is also provided.
Reserved Instance
Azure Reserved Instances (RI) allow you to reserve Azure SQL VMs, Azure SQL Managed Instance*, Azure SQL Database* in advance for a one- or three-year term, providing significant cost savings compared to pay-as-you-go pricing. Key benefits of RI include price predictability, flexible usage, and capacity assurance.
*Important: RI option is only available only for vCore purchase model only
For Azure SQL, RI can optimize costs by providing discounted pricing for reserved capacity. With an RI, you can reserve a specific amount of vCore for a SQL database, allowing you to save up to 33% compared to pay-as-you-go pricing. This helps you manage and forecast costs more effectively, while still providing the flexibility to adjust your usage as needed. Overall, Azure RIs can help you achieve significant cost savings and better control of your Azure resources.
It is possible to calculate potential savings by using the Azure pricing calculator.
Tools
There are many tools and services available to support the migration process, and it can be challenging to understand their respective purposes. Here’s a brief summary of each tool and service.
- Azure Migrate – A central service (hub) responsible for coordinating and tracking migrations in Azure. It supports not only migrations of SQL Server but also migrating VMware virtual machines and physical servers to Azure, as well as migrating web applications to Azure App Service etc.
- Azure Database Migration Service (ADMS) – is a fully managed service designed to help you migrate your on-premises databases to Azure data platforms with minimal downtime. It provides a guided workflow to simplify the migration process and supports a wide range of source databases, including SQL Server, Oracle, MySQL etc.
- Azure SQL migration extension for Azure Data Studio – extension for assessing readiness and performing migrations to Azure SQL. Integrates with Azure Migrate and Azure Database Migration Service.
- Database Migration Assistant (DMA) – SQL Server tool for assessing readiness and performing migrations to Azure SQL.
- SQL Server Migration assistant – Tool for automating database migrations from Access, DB2, MySQL, Oracle, SAP ASE to SQL Server (on-premise)
- Database Experimentation Assistant (DEA) – Tool for assessing the load/behavior of a database before upgrading to a higher version of SQL Server.
For the purpose of migration mostly you use Azure Migrate, Azure Database Migration Service (ADMS) or Azure SQL migration extension for Azure Data Studio
Azure Migrate: https://learn.microsoft.com/en-us/azure/migrate/
Azure Database Migration Service (ADMS): https://learn.microsoft.com/en-us/azure/dms/dms-overview
Azure SQL migration extension for Azure Data Studio: https://learn.microsoft.com/en-us/sql/azure-data-studio/extensions/azure-sql-migration-extension?view=sql-server-ver16
Database Migration Assistant (DMA): https://learn.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-ver16
SQL Server Migration assistant: https://learn.microsoft.com/en-us/sql/ssma/sql-server-migration-assistant?view=sql-server-ver16
Database Experimentation Assistant (DEA): https://learn.microsoft.com/en-us/sql/dea/database-experimentation-assistant-overview?view=sql-server-ver16
Conclusion
Migration process does not end with cutover and switch to Azure SQL. „Optimize” step is ongoing process which is part of daily tasks. It is worth to consider and use available options for cost optimization i.e. Azure Hybrid Benefit and Reserved Instances during migration planning. Acquired licenses does not prevent from migration and can be efficiently used during application migration or modernization. In mid and long term it is worth to monitor and review suggestions generated by Azure Advisor service.
Migration process is supported by several services and tools which might cause confusion. Read documentation carefully and use proper one during migration process. In case of migration to Azure SQL three of them will be used i.e. Azure Migrate, Azure Database Migration Service, extension form Azure Data Studio.
Key takeaways
- Acquired licenses can be moved to Azure
- Use transition period to run SQL Server and Azure SQL during and minimalize the costs
- Consider Reserved instance (IAAS and PAAS)
- Understand and choose right tools during migration
Check out our previous articles in this series:
Part 1: https://www.onex-group.com/blog/data-and-analytics/sql-server-migration-to-azure-sql/
Part 2: https://www.onex-group.com/blog/data-and-analytics/sql-server-migration-to-azure-sql-part-2/
