AWS DMS best practices for moving large tables with table parallelism settings
Database Blog
The article discusses AWS Database Migration Service (AWS DMS) best practices for migrating large tables using table parallelism settings. It highlights different parallelism options available in AWS DMS and provides guidance on when to use each option.
Specifically, the article covers:
- Source filter: Useful for migrating a subset of table data, but cannot be combined with parallelism settings.
- Parallel load with partitions-auto: Recommended for migrating complete table data with partitions.
- Parallel load with subpartitions-auto: Recommended for tables with limited partitions but huge subpartitions.
- Parallel load with partition-list and subpartitions-auto: Suitable for migrating selected partitions with subpartitions in parallel.
- Parallel load with partitions-list: Recommended for migrating specific partitions from a table.
- Parallel load with ranges: Recommended for unpartitioned tables or tables with fewer partitions but a large amount of data.
- Conclusion: Summarizes the best practices and provides additional resources.
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Aug 12
2025
2025
Improve AWS DMS continuous replication performance by using column filters to parallelize high-volume tables
Nov 15
2024
2024
Optimize your database storage for Oracle workloads on AWS, Part 2: Using hybrid partitioning and ILM data movement policies
Apr 21
2025
2025
Best practices to handle AWS DMS tasks during PostgreSQL upgrades
Feb 7
2024
2024
Cost optimize database migrations with AWS DMS: Part 1
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.