Consolidating databases best practices

Posted by / 21-Jun-2019 08:32

Consolidating databases best practices

Our source databases contained a representative amount of relatively evenly distributed data with a few large tables containing up to 250 GB of data.

Your migration's performance can be limited by one or more bottlenecks long the way.

However, at some point increasing this parallelism reduces performance.

If your replication server is relatively small, such as a dms.t2.medium, you'll want to reduce this number.

In our tests, we've migrated a terabyte of data in approximately 12 to 13 hours under ideal conditions.

If you find you are overburdening your source database you can reduce the number of tasks and/or tables per task for your migration.Therefore, it is important to review the task log when migrating a database. You can use tools such as Oracle SQL Developer, My SQL Workbench, or pg Admin III to move your schema if your source and target are the same database engine.If you want to convert an existing schema to a different database engine, you can use the AWS Schema Conversion Tool.When migrating to an Amazon RDS database, it’s a good idea to disable backups and Multi-AZ on the target until you’re ready to cut-over.Similarly, when migrating to non-Amazon RDS systems, disabling any logging on the target until cut over is usually a good idea.

consolidating databases best practices-12consolidating databases best practices-85consolidating databases best practices-31