February 7, 2012 at 7:36 am
I took a db backup from a SQL Server 2000 SP4 database and restored it into SQL2008 R2 SP1 and I got these warnings:
Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_FKSEQ_08EA5793" (index_id = 6) on object ID 149575571 in database "mxxxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_MODSEQ_08EA5793" (index_id = 5) on object ID 149575571 in database "mxxxxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
Warning: A column nullability inconsistency was detected in the metadata of index "PK_NAMSYSTABXXXX" (index_id = 2) on object ID 149575571 in database "mxxxxxx". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
I then ran the DBCC CHECKTABLE utility against the table and it did not report any issues.
I then ran the DBCC CHECKDB utility against the entire db and it did not report any issues either.
Has anyone seen this before? I realize that the two utilities don't find any issues but I wonder if there is a reason for this or something else I should check.
February 7, 2012 at 8:51 am
I have not seen it, but the first two look like system generated statistics. That's nothing to sweat since they're going to be completely rebuilt anyway since statistics generated in 2000 are not compatible with 2005, or those with 2008/2008R2, or those with 2012. The primary key would be the one concern I would have. But, if you've passed a consistency check, I think you're OK.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply