Symptoms

When you use the dm_db_stats_histogram Dynamic Management Function to query statistics information about a table that contains one or more Timestamp or HierarchyId columns in an instance of Microsoft SQL Server 2017, an assertion error may occur. Additionally, you receive the following error message:

Msg 3624, Level 20, State 1, Line 6

A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.

Msg 596, Level 21, State 1, Line 4

Cannot continue the execution because the session is in the kill state.

Msg 0, Level 20, State 0, Line 4

A severe error occurred on the current command. The results, if any, should be discarded.

Resolution

This fix is included in the following update for SQL Server:

Cumulative Update 8 for SQL Server 2017

About SQL Server builds

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

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 standard terminology that 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?

Thank you for your feedback!

×