Significance of has_unchecked_assembly_data due to a persisted computed column after changing compatibility level? 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?



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.
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.