FIX: Returns incorrect results when computed column is queried after installing hotfix that's described in KB 3213683 and enabling TF 176 in SQL Server 2016 or 2017

Koskee seuraavia: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Consider the following scenario:

  • Assume that you are using Microsoft SQL Server 2016 or 2017. 
  • You install the Cumulative Update 2 for SQL Server 2016 SP1 or Cumulative Update 4 for SQL Server 2016 to address the issue that's described in the Knowledge Base (KB) article 3213683. 
  • You enable the Trace Flag (TF) 176 after you apply the hotfix.
  • In this situation, when you query a computed column, you may notice that incorrect results are returned. Additionally, you may receive a metadata error that resembles the following:
Metadata stored on disk for computed column ColumnName in table TableName did not match the column definition. In order to avoid possible index corruption, please drop and recreate this computed column.


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

      Cumulative Update 1 for SQL Server 2017

      Cumulative Update 8 for SQL Server 2016 RTM

      Cumulative Update 5 for SQL Server 2016 SP1


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.