Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

The index may be corrupt. Run DBCC CHECKTABLE to verify consistency. Expand / Collapse
Author
Message
Posted Sunday, September 9, 2012 7:49 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, June 16, 2014 10:44 AM
Points: 153, Visits: 583
restored database from SQL2000 to SQL 200R2
After restore I got bunch message in the logs.

Any idea? what is fix? Or i can ignore the warning?

Message
Warning: A column nullability inconsistency was detected in the metadata of index "_WA_Sys_OPERATION_SEQ_NUM_10566F31" (index_id = 4) on object ID 274100017 in database "DB_name". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.
Post #1356477
Posted Sunday, September 9, 2012 8:08 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:37 AM
Points: 40,596, Visits: 37,053
And, did you run CheckTable as the error said? If so what's the output?

If not, please run this and post the full and unedited results.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1356479
Posted Sunday, September 9, 2012 9:04 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, June 16, 2014 10:44 AM
Points: 153, Visits: 583
Hi Gila


Command(s) completed successfully.
Post #1356484
Posted Sunday, September 9, 2012 9:34 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:37 AM
Points: 40,596, Visits: 37,053
Is the statistic _WA_Sys_OPERATION_SEQ_NUM_10566F31 still present?
If so, maybe drop it. SQL can always recreate it if it needs to.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1356485
Posted Sunday, September 9, 2012 10:21 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, June 16, 2014 10:44 AM
Points: 153, Visits: 583
Gila,

1)There wont be any issue, If I drop?

2)After dropping, Can i recreate?

there are approx 100 of them in sql logs for that database.
Post #1356488
Posted Sunday, September 9, 2012 10:25 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:37 AM
Points: 40,596, Visits: 37,053
No issues, as I said SQL can recreate it if necessary.

Yes, drop any stats that were mentioned in errors.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1356489
Posted Sunday, September 9, 2012 10:48 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Friday, December 12, 2014 12:03 PM
Points: 4,363, Visits: 9,547
One of the steps of upgrading from 2000 to anything later (2005, 2008, 2008R2, 2012) is to update all statistics. That is a post-upgrade requirement.

If you perform that step - it should take care of these types of errors.

The next item you want to perform is: DBCC CHECKDB(database) WITH DATA_PURITY;

This is a one time operation and should complete successfully. If it doesn't complete successfully, fix the errors either on the 2000 instance (because someone manually modified the system tables) or on the 2005 instance by recreating the affected objects.



Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #1356497
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse