Database migrations need to happen frequently to apply changes in database applications. Those migrations can be small, like adding new objects or changing some procedures or functions. Migrations can also be more extensive, like migrating large tables. In both cases, the database migrations need to be robust and repeatable if something goes wrong. In this PL/SQL Office Hours, we will explore practices to ensure high quality in your PL/SQL database migrations. We will have a look which elements make your database migrations repeatable and give an introduction on how to get started with automated database migrations if you have never done any before.