FIX: Error when you process a calculated column in a table with multiple partitions

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you have a Tabular model with a calculated column in SQL Server 2016. When you refresh the calculated column, the data might have to be re-encoded in order to change the column dictionary from value-encoded to hash-encoded. If there are multiple partitions, the re-encoding operation might encounter this defect and produce invalid encoded values in the segment. This may then trigger an exception and cause processing to fail.

The hotfix that's described in the "Resolution" section also fixes a related error that may occur during the re-encoding of the calculated column. The error message resembles the following:

Column 'A' count of segments is different from partition segments count. Possible cause for this issue is table metadata file corruption, 'P1'.


Cumulative update information

The fix for this issue is included in the following cumulative update for SQL Server:


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


Learn about the terminology that Microsoft uses to describe software updates.