Symptoms

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.

Resolution

This fix is included in Cumulative Update 1 for SQL Server 2017.

About SQL Server 2017 builds

Each new build for SQL Server 2017 contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build for SQL Server 2017.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×