Configure your destination AlloyDB for PostgreSQL database

Database Migration Service supports continuous migrations from Oracle source databases to the following AlloyDB for PostgreSQL destination databases:

Before you can use Database Migration Service to migrate data into your destination database, you must configure the database by:

Creating an AlloyDB for PostgreSQL cluster and a primary instance. We recommend that your primary instance has at least 4vCPU and 32GB of memory.
If you connect to the destination instance using a private IP address, Database Migration Service uses Private Service Connect to connect to the instance. For more information, see Configure Private Service Connect for a destination instance.
Creating a user account and database in the instance with the same name. For example, if you're using Database Migration Service to migrate data into the myapp database, then the name of the user account should also be myapp.
Setting the following permissions for the user on the database:
- CREATE SCHEMA
- CREATE TABLE
- SELECT
- INSERT
- UPDATE
- DELETE
- TRUNCATE (for all tables)

We recommend performing the following steps to avoid performance and data integrity issues:

Disable all foreign key constraints and indexes in the destination AlloyDB for PostgreSQL database, and enable them back when the migration is completed. Foreign keys don't block the migration but they affect its overall performance.
Disable all triggers in the destination AlloyDB for PostgreSQL database, and enable them back when the migration is completed. Triggers enabled in the destination database might result in data differences between the source and destination.