Consider the following scenario:
- You have tables that contain a foreign key constraint in SQL Server 2017.
- The foreign key constraints are a temporal table that supports cascade operations.
- The column IDs of the temporal table do not match the corresponding column IDs of the history table. For example, the temporal table has column IDs 1, 2, 3, and 4, but the history table has column IDs 1, 2, 10, and 11.
In this scenario, any DML statements that use cascading operations fail to execute.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.