Consider the following scenario:
- In SQL Server 2014 or 2016, you have several tables, each of which has a PRIMARY KEY constraint specified.
- You create a cascading chain for those tables by using the FOREIGN KEY constraint together with the ON DELETE CASCADE action.
- You create an AFTER DELETE trigger for each table.
- You delete a row from the parent table. This triggers the AFTER DELETE triggers and the ON DELETE CASCADE action chain.
In this scenario, the triggers may occur in the wrong order.
This issue is fixed in the following cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.