Symptoms

Assume that you have a table that has an integer column in SQL Server 2017 and Microsoft SQL Server 2016 and 2014, and the column has the following features:

  • The column is declared as NOT NULL.

  • The column has a CHECK constraint defined on it, and the constraint only allows the column to have the value of 1.

  • The column participates in the partition scheme that does not have zero partitions defined yet (schemes like this may be defined for future partition splitting that have not yet been set up).

In this scenario, when you try to query the table, an access violation occurs.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

       Cumulative update 9 for SQL Server 2016 SP1

       Cumulative Update 1 for SQL Server 2016 SP2

       Cumulative Update 5 for SQL Server 2017

       Cumulative Update 12 for SQL Server 2014 SP2

Each new cumulative update for SQL Server contains all the hotfixes and security fixes that were in the previous build. Check out the latest cumulative update for SQL Server:

Latest cumulative update for SQL Server 2016

Latest cumulative update for SQL Server 2017

Latest cumulative update for SQL Server 2014

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 terminologythat 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!

×