FIX: Stack dump occurs when table type has a user-defined constraint in SQL Server 2016, 2017 and 2019

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you use Microsoft SQL Server 2016, 2017 or 2019. When you create a table type by using these different constraints (default column values, computed columns, check constraints, primary key), you may notice that the cloned database that's created by DBCC CLONEDATABASE always triggers a stack dump that resembles the following: 
Msg 596, Level 21, State 1, Line LineNumber 
Cannot continue the execution because the session is in the kill state.
Msg 0, Level 20, State 0, Line LineNumber 
A severe error occurred on the current command. The results, if any, should be discarded.


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


This issue is fixed in the following cumulative updates for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:


Learn about the terminology that Microsoft uses to describe software updates.