FIX: AFTER DELETE triggers occur in the wrong order in the ON DELETE CASCADE action chain in SQL Server 2014


Consider the following scenario:

  • In SQL Server 2014, 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.


The fix for this issue is included in Cumulative Update 11 for SQL Server 2014 Service Pack 1.

About cumulative updates for SQL Server 2014 


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


Learn about the terminology Microsoft uses to describe software updates.


Article ID: 4009823 - Last Review: 21 Feb 2017 - Revision: 10

Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Enterprise Core, Microsoft SQL Server 2014 Standard