FAQ

Frequently Asked Questions:
Database Migration Service (DMS) for MS SQL Server

  1. Will Database Migration Service (DMS) migrate my MS SQL Server from On-Premise to AWS RDS or EC2 SQL Server?
  2. Will the applications be able to continue using/updating the source SQL Server during the migration?
  3. Is migration to RDS Multi-AZ supported?
  4. Can DMS be used for creating RDS or EC2 SQL Server Read-Replicas after I am done with the migration?
  5. Can DMS be used to migrate RDS or EC2 SQL Server to Azure or Google?
  6. How do I get started with the migration of my MS SQL Servers?

Q: Will Database Migration Service (DMS) migrate my MS SQL Server from On-Premise to AWS RDS or EC2 SQL Server?

A: DMS was designed to handle MS SQL Server migrations to AWS RDS and EC2 SQL Server migrations.  It is capable to migrate MS SQL Server Enterprise to RDS or EC2 SQL Server Standard and even to Web Edition. It can be also used to migrate MS SQL Server databases from RDS to RDS, zone-to-zone, or region-to-region.

Top of Page

Q: Will the applications be able to continue using/updating the source MS SQL Server during the migration?

A: Yes, migration of MS SQL Server database with no downtime is supported. After the initial replication (seeding) is completed, the process will transition to continuous change tracking. You can run the replication over extended time (i.e. 1-3 months), while configuring your AWS environment and conduct testing against the Read-Replicas. Cut-over whenever ready.

Top of Page

Q: Is migration to RDS Multi-AZ supported?

A: Yes, however note that if the reason for considering to use RDS Multi-AZ is to create Read-Replicas (to be used for HA, Reporting, or to off-load your primary RDS SQL Servers, or to fail-over in another AWS region), Multi-AZ does NOT create MS SQL Server Read-Replicas. It mirrors the database without providing you access to the replica. The replicas are located in same region, cross region mirroring is not supported by RDS Multi-AZ for MS SQL Server.

CloudBasic DMS can be used as an alternative to Multi-AZ. Creating RDS SQL Server Web Edition Read-Replicas from RDS SQL Server Enterprise/Standard is a common use case. The Read-Replicas can be created in another zone or in another region (cross-region replication for true DR and data-locality). The RDS-to-RDS solution based on CloudBasic Replication delivers more functionality and costs 1/2 of Multi-AZ. Review the benchmarks and the TCO comparison tables below for more information:

http://cloudbasic.net/aws/rds/alwayson/benchmark/
http://cloudbasic.net/aws/rds/alwayson/aws-multi-az-vs-cloudbasic-multi-az-ar/

Sample configuration:

  • RDS Source in US-Virginia: r3.XLarge, MS SQL Server EE w/ Encryption and Multi-Zone Mirroring
  • RDS Destination #1 in EU-Ireland: m3.Large, MS SQL Server Web Edition
  • RDS Destination #2 in Asia-Singapore: m3.Large, MS SQL Server Web Edition

Top of Page

Q: Can DMS be used for creating RDS or EC2 SQL Server Read-Replicas after I am done with the migration?

A: Yes, using CloudBasic DMS or CloudBasic RDS AlwaysOn/Geo-Replicate (both are based on same replication engine) to create RDS SQL Server Web Edition Read-Replicas from RDS SQL Server Enterprise/Standard is a common use case. The Read-Replicas can be created in another zone or in another region (cross-region replication for true DR and data-locality).

Important: If you are considering to use RDS Multi-AZ, note that Multi-AZ does NOT create MS SQL Server Read-Replicas. It mirrors the database without providing you access to the replica. The replicas are located in same region, cross region mirroring is not supported by RDS Multi-AZ for MS SQL Server.

CloudBasic DMS or Geo-Replicate can be used as an alternative to Multi-AZ. The RDS-to-RDS solution based on CloudBasic Replication delivers more functionality and costs 1/2 of Multi-AZ. Review the benchmarks and the TCO comparison tables below for more information:

http://cloudbasic.net/aws/rds/alwayson/benchmark/
http://cloudbasic.net/aws/rds/alwayson/aws-multi-az-vs-cloudbasic-multi-az-ar/

Sample configuration:

  • RDS Source in US-Virginia: r3.XLarge, MS SQL Server EE w/ Encryption and Multi-Zone Mirroring
  • RDS Destination #1 in EU-Ireland: m3.Large, MS SQL Server Web Edition
  • RDS Destination #2 in Asia-Singapore: m3.Large, MS SQL Server Web Edition

 

Top of Page

Q: Can DMS be used to migrate RDS or EC2 SQL Server to Azure or Google?

A: Yes, this is a common use case. The replication is handled asynchronously; replication over long distance internet connections to remote region is possible.

Top of Page

Q: How do I get started with the migration of my MS SQL Servers?

A: Getting started with CloudBasic DMS migration of MS SQL Server is quick and simple. Most migration tasks can be set up in less than 10 minutes. Once you sign up for the service on http://cloudbasic.net/aws/rds/dms/, you will receive an AMI ID over email. Locate the AMI ID in the list of Community AMIs and launch as an EC2 server within or outside of your VPC. Once the instance is running, and port 80 opened in the security group, connect to it by pointing a browser to the public DNS root URL (or IP) at default www port 80 (it might take a while for all services to initialize). Register and you will receive an activation key, which you need to enter on the next step to activate the instance. Login with user: admin, initial temporary password: {EC2 Instance ID} (required for security reasons) Upon successful login, you will land on the wizard page, which will allow you to initiate RDS/SQL Server replication in various scenarios, in just a few clicks. For more information, visit the Get Started section of the documentation.

Top of Page