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

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

Latest cumulative update 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.


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!