Applying constraints after the migration is finalized v1.3.4

At the beginning of your data migration journey with EDB Data Migration Service (EDB DMS), you prepared and imported the schema of your source database. Now, connect to the destination database and reapply the constraints that were excluded from the schema and data migration.

Primary key and unique constraints

For primary key and unique constraints, you already created the tables and constraints in the destination Postgres database. This allowed EDB DMS to map them to the source objects and migrate data successfully. You don't need do to anything else.

The same applies to not null constraints if you included them in your schema import.

Foreign key, check, and exclusion constraints

You can now reapply any foreign key, check, or exclusion constraints you excluded during the schema preparation and import.

Ensuring data integrity

Rows in tables that don't have primary key or unique constraints were migrated with at-least-once delivery, Therefore, it's possible that these rows are duplicates.

Deduplication can be performed as part of the verification.

Verification

To verify that all data was migrated, compare the source and destination databases.

You can use LiveCompare.