Sign in with Microsoft
New to Microsoft? Create an account.


Consider the following scenario:

  • You try to run a query by using default Cardinality Estimation while histogram amendment is enabled.

  • The query includes expressions on a column that is used in one of the predicates.

In this scenario, an access violation occurs. Additionally, you receive the following error message:

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.

Note Histogram amendment can be enabled by using the USE HINT(‘ENABLE_HIST_AMENDMENT_FOR_ASC_KEYS’) query option or trace flag 4139.


This problem is fixed in the following updates for SQL Server:

Cumulative Update 8 for SQL Server 2017

Cumulative Update 5 for SQL Server 2016 Service Pack 2

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

Latest cumulative update for SQL Server 2016


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


DBCC TRACEON - Trace Flags (Transact-SQL)

Learn about the standard terminology 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!