Automating database migration - Amazon DMS tutorial
summary
AWS Database Migration Service (DMS) plus the Schema Conversion Tool (SCT) automates moving and modernizing databases with concrete results: launched March 2016, the service reports ~23,000 migrations and supports Oracle/SQL Server/Teradata → MySQL/Postgres/Aurora/Redshift, plus MongoDB, DynamoDB and S3 targets. SCT generates a conversion report and SCT converts schema while DMS performs logical replication table-by-table using a replication instance, running full load + CDC to reach near-zero downtime; limitations include stored-procedure code not converted and extra configuration for large LOBs, multi-AZ provides high availability.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:14DB Freedom is a powerful thing...
- 3:21How can I get to the cloud? How will my on-premises data migrate to the cloud?
- 5:32What are DMS and SCT?
- 11:53When to use DMS and SCT?
- 18:47New SCT Data Extractors
- 22:37Split Migration
- 23:46AWS database migration partners
- 27:02Database migration process Step 1: Convert or Copy your Schema
- 27:58Keep your apps running during the migration
- 29:51Load is table by table
- 30:28Change data capture (CDC) and apply
- 32:27Samples and Recipes
related talks
35mBest practices for migrating with databases
31mModernizing a megascale database
28mMove to Managed Databases
26mIntroduction to AWS databases: Modernize your data infrastructure
25mMigrate to an AWS database: The freedom to save, grow, and innovate
21mSave, Grow and Innovate using AWS Databases
24mMigrating from Oracle to Azure Database for PostgreSQL, Seamlessly
32mMigrate to an AWS database: The freedom to save, grow, and innovate