4

This database has a persisted computed column, which is computed by calling a .NET function. When changing compatibility from MSSQL 2005 to 2012, I was presented with error 10334, which looks more like a warning: it's telling me that it had to mark one of the tables as has_unchecked_assembly_data.

What it doesn't tell me is what to do about this. Should I leave it as is? Should I force the column to be recomputed somehow? How?

enter image description here

The documentation for alter assembly unchecked data lists several causes for this, and I think #1 is the only one that applies to this database. It also doesn't explain how to unmark such columns.

Solomon Rutzky
  • 70,048
  • 8
  • 160
  • 306
Roman Starkov
  • 267
  • 1
  • 7

2 Answers2

6

Execute DBCC CHECKTABLE or DBCC CHECKDB to set the has_unchecked_assembly_data to zero. This is documented in the SQL Server Books Online sys.tables reference.

Dan Guzman
  • 28,989
  • 2
  • 46
  • 71
2

While Upgrading to SQL Server 2017, i needed to run DBCC CHECKDB or DBCC CHECKTABLE with the EXTENDED_LOGICAL_CHECKS option to set has_unchecked_assembly_data to zero.

References:
Assemblies - Implementing
Performing Logical Consistency Checks on Indexes

MHeld
  • 432
  • 1
  • 5
  • 14