A column nullability inconsistency was detected in the metadata E

Hello, I am trying to restore a backup of a database that was taken in SQL
Server 2000 onto SQL Server 2005. It appears the action completes, but I get
a list of errors. I have ran a checktable on the tables in question on both
our origional 2000 database and 2005, as well as a checkdb on the database in
question on our SQL Server 2005 and get no errors. Any ideas?
Database 'MyDatabase' running the upgrade step from version 539 to version
551.
A column nullability inconsistency was detected in the metadata of
indexWarning: A column nullability inconsistency was detected in the metadata
of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
935062467 in database "MyDatabase". 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_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
in database "MyDatabase". 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_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062467
in database "Mydatabase". 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_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
database "MyDatabase". 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_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
verify consistency.Judging by the names of these, they appear to be auto-created statistics (and not indexes). I'd drop
those and then re-try the upgrade. See the DROP STATISTICS command.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Aaron" <Aaron@.discussions.microsoft.com> wrote in message
news:5DF5A523-75C0-45E1-BE54-6901814D0110@.microsoft.com...
> Hello, I am trying to restore a backup of a database that was taken in SQL
> Server 2000 onto SQL Server 2005. It appears the action completes, but I get
> a list of errors. I have ran a checktable on the tables in question on both
> our origional 2000 database and 2005, as well as a checkdb on the database in
> question on our SQL Server 2005 and get no errors. Any ideas?
> Database 'MyDatabase' running the upgrade step from version 539 to version
> 551.
> A column nullability inconsistency was detected in the metadata of
> indexWarning: A column nullability inconsistency was detected in the metadata
> of index "_WA_Sys_claim_scrubber_37BBEBC3" (index_id = 34) on object ID
> 935062467 in database "MyDatabase". 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_abn_notifier_37BBEBC3" (index_id = 35) on object ID 935062467
> in database "MyDatabase". 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_cptguidelines_37BBEBC3" (index_id = 36) on object ID 935062467
> in database "Mydatabase". 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_federal_37BBEBC3" (index_id = 37) on object ID 935062467 in
> database "MyDatabase". 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_medicarea_37BBEBC3" (index_id = 38) on object ID 935062467 in
> database "MyDatabase". The index may be corrupt. Run DBCC CHECKTABLE to
> verify consistency.
>sql