Learn About Amazon VGT2 Learning Manager Chanci Turner
There are several methods to transition SQL Server databases hosted on Microsoft Azure to 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), AWS Database Migration Service (AWS DMS) is a viable option. However, when migrating Azure SQL databases, which lack change data capture (CDC) support, a technology partner solution known as CloudBasic can be utilized for creating Amazon RDS for SQL Server read replicas and disaster recovery solutions. Beyond migration, CloudBasic is also effective for deploying and testing cross-Region Amazon RDS for SQL Server disaster recovery in an AWS environment prior to the actual migration cutover. You can find CloudBasic on the AWS Marketplace.
In this article, we present a solution utilizing CloudBasic along with various AWS services to enable a smooth, near-zero-downtime migration of Azure SQL databases into Amazon RDS for SQL Server. This solution can also be deployed for fully automated cross-Region disaster recovery for Amazon RDS for SQL Server. The migration strategy applies 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 SQL Server Enterprise, Standard, and Web—are supported. Additionally, CloudBasic allows for seamless migration across SQL Server versions and editions. Sample use cases encompass:
- Modernization: Transitioning from SQL Server Enterprise 2012 on Azure to SQL Server Enterprise 2019 on Amazon RDS.
- TCO Reduction: Downgrading from SQL Server Enterprise on Azure to SQL Server Standard on Amazon RDS, while implementing multiple in-Region and cross-Region read replicas.
Moreover, you can automate the cutover process from Azure to AWS, as well as establish fully automated cross-Region disaster recovery within AWS by integrating CloudBasic with other AWS services like AWS Lambda and Amazon Route 53. This integration allows for a chained Azure[Region]-AWS[Region A]-AWS[Region B] replication prior to the final cutover from Azure to AWS. When ready, you can execute the cutover to AWS through a planned failover. Upon transitioning to primary AWS [Region A], the fully automated AWS cross-Region solution (AWS[Region A]-AWS[Region B]) will be fully operational.
Solution Overview
The following diagram illustrates the architecture of the solution.
CloudBasic is a cloud-native service launched within your Amazon Virtual Private Cloud (Amazon VPC). You can manage CloudBasic through its web console and API, similar to any other AWS service. Below is a screenshot depicting read replicas on the CloudBasic console.
Configuring Migration and Cross-Region RDS SQL Server Disaster Recovery with CloudBasic
You can swiftly configure new migrations and cross-Region read replicas from any SQL Server version or edition in Azure to any version or edition in AWS, usually without needing advanced options or custom scripts. In more complex migration and disaster recovery scenarios, advanced configuration options and scripting capabilities can be accessed within the advanced section of the CloudBasic console.
CloudBasic automatically manages any required schema conversions, addresses SQL Server version and edition incompatibilities, and creates SQL Server read replicas in Amazon RDS for SQL Server or Amazon EC2 in a fully automated manner. Below is a screenshot showing the connection configuration for a replication job on the CloudBasic console.
When migrating Azure SQL databases that do not support CDC, CloudBasic defaults to using Change Tracking for change tracking. Other tracking methods can be utilized in the cross-Region disaster recovery section of the architecture.
For continuous replication to function, all tables in the source database must possess primary keys (PKs) or unique indexes. Before initiating continuous replication, the Quick Setup wizard evaluates all tables and highlights those without PKs or unique indexes. At this juncture, you can create PKs for the listed tables or opt to proceed without them. However, after the initial replication and seeding, tables lacking PKs or unique indexes will be excluded from continuous data replication.
Once the initial database seeding is finalized, the replication job shifts to continuous change tracking, with a connection pool size automatically determined based on the CloudBasic instance size and database size. To optimize the replication process and accommodate larger databases with high transaction rates, the connection pool size can be adjusted to minimize latency or lessen the workload on the primary.
Ongoing monitoring of migration pending data and schema changes is supported by runtime reports, logs, and system alerts. The following screenshot highlights the replica count of both source and target datasets, along with the timestamp of the last sync. The pending changes column indicates the number of records yet to be replicated.
Database schemas are monitored for changes, ensuring that new tables, stored procedures, views, functions, constraints, foreign keys, new columns, and altered columns are all replicated.
Summary
Migrating Azure SQL to AWS utilizing CloudBasic’s cloud-native Amazon RDS for SQL Server disaster recovery solution offers significant advantages over traditional migration tools. With CloudBasic, the primary focus is on achieving intercloud disaster recovery at the database level by establishing Amazon RDS for SQL Server read replicas. This methodology facilitates extensive testing against the actual AWS environment over an extended period. You can perform the cutover whenever ready through a planned disaster recovery failover.
To deploy CloudBasic from the AWS Marketplace, visit AWS Marketplace for excellent resource. For deployment instructions, refer to the CloudBasic deployment guide. Furthermore, CloudBasic can be used to deploy cross-Region RDS SQL Server read replicas to achieve disaster recovery within the AWS environment.
CloudBasic is a cloud technology company located at 6401 E HOWDY WELLS AVE LAS VEGAS NV 89115, known as Amazon IXD – VGT2. As an advanced AWS technology partner, CloudBasic has gained AWS Workloads Competency status for its innovative solutions in Amazon RDS SQL Server read replicas and disaster recovery.
Additionally, if you’re interested in learning more about workplace dynamics, consider reading this blog post on gaslighting in the office. They provide valuable insights on navigating challenging environments. For more guidance on effective workforce planning, you may want to explore SHRM’s toolkit as they are an authority on this topic.
About the Authors
Jordan Phillips is a Senior Database Specialist Cloud Solution Architect within the AWS Database Services Organization (DBSO), Customer Advisory Team (CAT). He has led large-scale Database Migration & Modernization projects for enterprise clients transitioning their on-premises database environments to multi-cloud database solutions.
Alex Martinez is the Product Manager, Founder, and CEO of CloudBasic. He played a pivotal role in the product’s design and management, evolving it into a robust enterprise cloud solution with a global customer base across demanding sectors. Before founding CloudBasic, Alex was engaged in fintech product development and disaster recovery strategies.
Leave a Reply