2

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.

Improve this question
4
  • 1
    DBCC CHECKTABLE or DBCC CHECKTABLE will set the has_unchecked_assembly_data to zero according to msdn.microsoft.com/en-us/library/ms187406.aspx.
    – Dan Guzman
    Nov 24, 2015 at 13:10
  • @DanGuzman It did, thank you! I did a fair bit of googling but couldn't find this. I'll accept if you post as an answer.
    – Roman Starkov
    Nov 24, 2015 at 13:47
  • @romkyns Just FYI, the documentation that you linked to for ALTER ASSEMBLY actually does explain this fix: UNCHECKED DATA: By default, ALTER ASSEMBLY fails if it must verify the consistency of individual table rows. This option allows postponing the checks until a later time by using DBCC CHECKTABLE. ;-)
    – Solomon Rutzky
    Nov 24, 2015 at 14:16
  • @srutzky hah! You're right. I did not recognize that as an SQL command, nor did it occur to me to google that.
    – Roman Starkov
    Nov 24, 2015 at 14:17

2 Answers 2

Reset to default
5

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.

Improve this answer
2
  • I think you have the DBCC listed twice ;-). Also, this fix is documented in the ALTER ASSEMBLY documentation under the UNCHECKED DATA option. Just mentioning that for completeness :-).
    – Solomon Rutzky
    Nov 24, 2015 at 14:18
  • @srutzky, thanks for pointing out the typo. Corrected.
    – Dan Guzman
    Nov 25, 2015 at 4:16
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

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.