AWS Database Migration Service vs. Help Desk Migration

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.

Incentivized

Thanks to the quick response from the support team, I was able to maintain an ongoing dialogue and get questions answered promptly throughout the project. Their responsiveness made it easy to request and implement specific changes, such as disabling comments on all migrated articles, without delaying our migration timeline.

• Very responsive support team.
• Great step by step instructions.
• Ability to rerun the migration.

• There is little room for improvement in the GUI

It was very simple to use.

• 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

Incentivized

• Tool consolidation
• Cost reduction
• Ease of maintenance