FK extract script fails if FK goes over multiple columns

[upstream-dmahlberg]

In Step 4 of the Migrate the sample schema section of this page, a lengthy SQL statement is used to extract the statements used to drop and re-add the Foreign Keys from the destination database. Sadly, re-adding the FKs failes if the FKs go over multiple columns:

ALTER TABLE <table> ADD CONSTRAINT <fk_name> FOREIGN KEY ("column1,column2,column3") should really be

ALTER TABLE <table> ADD CONSTRAINT <fk_name> FOREIGN KEY ("column1","column2","column3") since the former statements throws an SQL-Exception like

ERROR: "column "column1,column2,column3" referenced in foreign key constraint does not exist".

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 00403cac-9788-3966-2c23-696748b9379b
• Version Independent ID: db980aa3-68e9-98d0-724c-030ab3fd68ff
• Content: Tutorial: Migrate Azure DB for PostgreSQL to Azure DB for PostgreSQL online via the Azure portal - Azure Database Migration Service
• Content Source: articles/dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal.md
• Service: dms
• GitHub Login: @arunkumarthiags
• Microsoft Alias: arthiaga

[AnuragSharma-MSFT]

@upstream-dmahlberg Thank you for the feedback. We are actively investigating and will get back to you soon.

[KalyanChanumolu-MSFT]

@upstream-dmahlberg This is being assigned to the content author to evaluate and update the documentation as appropriate.