Applies ToSQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use) SQL Server 2016 Service Pack 1

Symptoms

Consider the following scenario when you use SQL Server 2016:

  • You create a clustered columnstore index on a memory-optimized table that contains a column of data type string (for example, nchar or nvarchar).

  • The data length of the column isĀ 32 bytes (for example, nchar(16) or nvarchar(16)).

  • The data in the column is unique or almost unique, and the data size is 32 bytes.

In this scenario, when you insert data into this table, you may receive the following assert error in the SQL Server error log:

vldPageCount <= SegmentsTableRow::MaxSerializedPages

Resolution

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

Note After you install the update, you must set trace flag 9968 to enable the fix. To set trace flag 9968, see the Trace Flags (Transact-SQL) topic on the Microsoft Developer Network (MSDN) website.

Each new build for SQL Server 2016 contains all the hotfixes and security fixes that were included in the previous build. We recommend that you install the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

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 terminology Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.