• One of my team members hit this today will updating statistics. He got around it by creating a new table and loading the data in it (SELECT/INTO).

    A DBCC checktable of the original table suggests no issues.

    Still working on this one...