Symptoms
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.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative updates for SQL Server:
Cumulative Update 1 for SQL Server 2019
Cumulative Update 17 for SQL Server 2017
Cumulative Update 10 for SQL Server 2016 SP2
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:
Latest cumulative update for SQL Server 2019
Latest cumulative update for SQL Server 2017
Latest cumulative update for SQL Server 2016
References
Learn about the terminology that Microsoft uses to describe software updates.
