Issue link: https://resources.awscloud.com/i/1496544
Automating the migration This is valuable because it lets you repeat the migration as often as you need to, fixing errors as you encounter them or changing parameters. You also can adapt and reuse the automation framework for further migrations. Checking for Incompatibilities If you are using the same RDBMS (such as MySQL, for instance) for both databases, check the versions to determine whether you are using features that are unsupported on the cloud version. These checks are obviously even more likely to turn up incompatibilities if you are moving to a new database engine. The conversion issues that you encounter when performing a heter‐ ogeneous migration to a cloud database are the same as when you're performing such a migration on-premises; however, you have access to a wider range of solutions. The database vendors themselves generally offer tools that help move data to a cloud database of the same type. For example, Oracle comes with data migration tools such as Datapump, RMAN, and SQL Developer that help you to move your Oracle databases to the cloud. In addition, cloud providers and third parties offer services such as AWS's Schema Conversion Tool to move schemas. These tell you whether the schemas can be translated, and provide suggestions for workarounds if necessary. Still, most heterogeneous database migrations require both automa‐ ted tools and manual action by the DBA. If you're moving to an AWS database, you can draw on specific recommendations on the AWS website. Some migration tools employ a translator to convert one database's objects, such as Oracle stored procedures, to a non-Oracle database such as PostgreSQL. These tools, however, might do an incomplete job, because each database engine employs unique coding practices. This is the reason for performing stringent tests on the target data‐ base for accuracy and performance after migrating to the cloud. Some programming techniques employed by a specific RDBMS might not have an exact equivalent in the target database. The migration tool might flag these types of conversion issues during the migration process. In many cases, it can also show you the code that Planning | 31