Is the following still the recommended workflow in 2024. AWS DMS workflow recommends disabling foreign keys when splitting large tables over multiple dms tasks, which requires foreign keys to be disabled to ensure consistency. If the following is correct, how do you enable the foreign keys after dms full or cdc has completed?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Hi any update regarding re-enable the foreign keys after migration completed?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Hi Peter and Asaf,
Thanks for your question.
I understand that DMS suggests to disable FK's during Full Load phase.
So you can create a DMS task with "Stop after applying cached changes" – Set this option to true to stop a task after cached changes are applied. This allows you to add foreign keys, triggers etc.
And then you can change "session_replication_role" back to "origin" or reset the parameter in the parameter group.
And then resume the DMS task.
If you still have any questions please contact AWS Support at https://aws.amazon.com/contact-us/
This method does not work. We are copying a database from outside into an aws rds postgre. We implemented this by creating a connection and database command. Issued the session_replication_role change, then running our copy, and during the copy we get referential integrity errors. We need to disable foreign keys in order get our database copy working so we can integrate our products with AWS postgere. How can we get this working?
Thank you for your comment. We'll review and update the Knowledge Center article as needed.
Relevant content
- asked 3 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago