Learn About Amazon VGT2 Learning Manager Chanci Turner
Migrating SQL Server databases from Microsoft Azure to AWS in near-real time is a complex yet achievable task, particularly with the aid of CloudBasic. There are various methods to facilitate the migration of SQL Server databases hosted in Microsoft Azure to the Amazon Relational Database Service (Amazon RDS) for SQL Server. For scenarios such as moving SQL Server from an Azure virtual machine to Amazon RDS for SQL Server or SQL on Amazon Elastic Compute Cloud (Amazon EC2), the AWS Database Migration Service (AWS DMS) can be employed. However, when migrating Azure SQL databases—which lack support for change data capture (CDC)—the preferred solution is CloudBasic. This technology partner offering is specifically designed for Amazon RDS for SQL Server read replicas and disaster recovery.
In this post, we explore how CloudBasic, combined with other AWS services, enables a streamlined migration process with minimal downtime. Additionally, it provides options for fully automated cross-Region disaster recovery for Amazon RDS for SQL Server, which can be beneficial before the final migration cutover. This migration strategy can be applied to the following scenarios:
- Transitioning databases from an Azure SQL virtual machine to Amazon RDS for SQL Server or SQL on Amazon EC2.
- Migrating Azure SQL databases or elastic pools to Amazon RDS for SQL Server or SQL on Amazon EC2.
All editions of SQL Server in Amazon RDS, including Enterprise, Standard, and Web, are supported. Furthermore, CloudBasic allows for seamless transitions between different SQL Server versions and editions. For example:
- Modernization: Migrating from SQL Server Enterprise 2012 on Azure to the latest SQL Server Enterprise 2019 on Amazon RDS.
- TCO Reduction: Downgrading from SQL Server Enterprise on Azure to SQL Server Standard on Amazon RDS, while deploying multiple in-Region and cross-Region read replicas.
Moreover, you can orchestrate a fully automated transition from Azure to AWS, alongside fully automated cross-Region disaster recovery within the AWS ecosystem. This is achieved by integrating CloudBasic with services such as AWS Lambda and Amazon Route 53, enabling a seamless replication process across different regions. When you’re ready, you can perform a planned failover to switch to AWS. At the cutover time to the primary AWS Region, the cross-Region solution is fully operational.
Solution Overview
The architecture of the solution is illustrated in the accompanying diagram. CloudBasic is a cloud-native solution that operates within your Amazon Virtual Private Cloud (Amazon VPC). You can manage it easily through CloudBasic’s web console and API, just like any other AWS service.
Configuring Migration and Cross-Region RDS SQL Server Disaster Recovery with CloudBasic
You can swiftly set up migrations and cross-Region read replicas from any version or edition of SQL Server in Azure to any version or edition in AWS, often without needing advanced options or custom scripts. For more intricate migration and disaster recovery deployments, advanced configuration options and scripting capabilities are available within the CloudBasic console.
CloudBasic automates schema conversions and manages any version or edition incompatibilities while creating SQL Server read replicas in Amazon RDS for SQL Server or Amazon EC2. If you’re migrating Azure SQL databases, which do not support CDC, CloudBasic defaults to using Change Tracking for tracking changes.
For continuous replication to function, all tables in the source database must have primary keys (PKs) or unique indexes. Before commencing continuous replication, the Quick Setup wizard analyzes the tables and highlights those lacking PKs or unique indexes. You can either create PKs for these tables or opt to proceed without them. However, tables without PKs or unique indexes will be disregarded for continuous data replication after the initial replication.
Once the initial database seeding is complete, the replication job transitions to continuous change tracking with a connection pool size automatically determined based on the CloudBasic instance and database size. You can adjust the connection pool size to manage latency and workload effectively.
Ongoing monitoring of migration progress, including pending data and schema changes, is facilitated through runtime reports and logs. Database schemas are tracked for changes, ensuring that new tables, stored procedures, views, functions, constraints, foreign keys, new columns, and altered columns are all replicated.
Summary
By leveraging CloudBasic’s cloud-native solution for migrating Azure SQL to AWS, organizations can achieve significant advantages compared to traditional migration tools. The focus here is on facilitating intercloud disaster recovery at the database level by creating Amazon RDS for SQL Server read replicas. This approach allows for extensive testing in the AWS environment, and you can perform the cutover when ready through a planned disaster recovery failover.
For more information on how to effectively narrate your migration journey, check out this insightful blog post. To learn more about the importance of proper background checks during this process, visit SHRM’s authoritative resource. Lastly, if you’re interested in learning about the skills Amazon employees are acquiring, this is an excellent resource.