Skip to main content
TrustRadius
AWS Database Migration Service

AWS Database Migration Service

Overview

What is AWS Database Migration Service?

AWS Database Migration Service helps users migrate databases to AWS. The source database remains fully operational during the migration to minimize downtime to applications that rely on the database. The vendor states that AWS Database Migration Service can migrate data…

Read more
Recent Reviews
Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is AWS Database Migration Service?

AWS Database Migration Service helps users migrate databases to AWS. The source database remains fully operational during the migration to minimize downtime to applications that rely on the database. The vendor states that AWS Database Migration Service can migrate data to and from most widely used…

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

2 people also want pricing

Alternatives Pricing

N/A
Unavailable
What is Astera Centerprise?

Centerprise Data Integrator is an integration platform that includes tools for data integration, data transformation, data quality, and data profiling.

What is Cloudiway Migration Platform?

Founded in 2010, Cloudiway is a cloud migration and enterprise coexistence SaaS that help to migrate mailboxes, documents, groups, sites, archives, teams between different productivity and collaboration systems such as Google Workspace and Microsoft 365. Cloudiway supports cross-tenant, on-premises…

Return to navigation

Product Details

What is AWS Database Migration Service?

AWS Database Migration Service Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(14)

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Chien Huey | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We have two use cases for AWS Database Migration Service.
  • AWS Database Migration Service is used to replicate certain critical data relationships between the production and lower environment databases. The business problem is keeping data consistency between the environments. An example is an equipment association with job sites. Equipment moves between job sites and those associations have to be updated.
  • We use AWS Database Migration Service to populate our lower environment databases with production-like data. AWS Database Migration Service replicates and transforms production data into our dev and QA databases. In so doing, AWS Database Migration Service provides production-like data for our engineering and QA teams. It does not work too well for this purpose. The task and mapping settings are limited so we end up having to manually de-duplicate data which prevents this from being a continual and near real-time process. AWS Database Migration Service helps with the initial replication but because we have to do many manual tasks it's not ideal. Our schema design contributes to this and had we considered replication our experience may have been better.
  • Replicating specific data elements on a continuous basis
  • Replicating entire databases - making a carbon copy
  • Managing many simultaneously running replication tasks
  • More extensive task and mapping settings
  • De-duplication support
As stated previously, AWS Database Migration Service excels when replicating very specific data elements between environments. AWS Database Migration Service handles replication tasks to load equipment assets or customer job sites from production to QA databases very well.

Full load replication - e.g., we need an exact copy of the production database in another region - works well. But when we need to load the QA database with the latest production data - it does work as well. AWS Database Migration Service comes up short because we do not want to wipe the QA database completely and make an exact copy. We want to keep what's already in the QA database and add production data so that we can QA with that level of volume. And at least with our database design, we end up having to do a lot of manual data manipulation and de-duplication.
  • Ongoing replication of data between environments to maintain consistency
  • Bulk loading data between databases
  • Single dashboard to manage multiple replication tasks
  • Set it and forget it for maintaining data consistency - moderate cost, zero to minimal maintenance
  • High touch production data loads into QA - negative ROI engineering time investment far exceeded our predictions
Return to navigation