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 123»»»

DBCC CheckTable returns following results, best way to deal with this? Expand / Collapse
Author
Message
Posted Tuesday, March 12, 2013 8:06 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 6:20 AM
Points: 271, Visits: 415
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_Advertise_BrandCopy_Price_Stock' (ID 69). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:11226494:9) identified by (Id = 11078215) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 137.50 and NSFPQtyInStock = 0 and Id = 11078215'.
Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_ITEMS_ADVFLAG_PARETN_PRICE_STOCK' (ID 70). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:10834009:15) identified by (Id = 8885719) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 9.30 and NSFPQtyInStock = 0 and Id = 8885719'.

These indexes were created days ago and are rarely used. Is it safe to drop and recreate corrupted indexes?
Post #1429835
Posted Tuesday, March 12, 2013 8:07 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 6:20 AM
Points: 271, Visits: 415
Also, neither is the PK or a FK or clustered.
Post #1429837
Posted Tuesday, March 12, 2013 8:37 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 29, 2014 9:40 AM
Points: 201, Visits: 811
As always I would suggest backups before any work is carried out but it should be ok to drop the index and recreate, you will have to perform an offline rebuild. Have a read of the blog below before you do anything:

http://www.sqlskills.com/blogs/paul/teched-demo-nonclustered-index-corruption/

Also would have a look at your disk subsystem as well, corruption would suggest an issue.
Post #1429856
Posted Tuesday, March 12, 2013 8:38 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: Yesterday @ 8:36 AM
Points: 40,615, Visits: 37,080
Please run the following and post the full, complete and unedited output.

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 #1429859
Posted Tuesday, March 12, 2013 8:41 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 6:20 AM
Points: 271, Visits: 415
GilaMonster (3/12/2013)
Please run the following and post the full, complete and unedited output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS



Running this now.


EDIT: This may take some time. It's only 5% done with its initial @BlobEater step.
Post #1429862
Posted Tuesday, March 12, 2013 9:50 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 6:20 AM
Points: 271, Visits: 415
GilaMonster (3/12/2013)
Please run the following and post the full, complete and unedited output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS




Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_Advertise_BrandCopy_Price_Stock' (ID 69). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:10834009:15) identified by (Id = 8885719) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 9.30 and NSFPQtyInStock = 0 and Id = 8885719'.
Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_Advertise_BrandCopy_Price_Stock' (ID 69). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:10945035:10) identified by (Id = 9750456) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 34.40 and NSFPQtyInStock = 0 and Id = 9750456'.
Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_Advertise_BrandCopy_Price_Stock' (ID 69). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:11226494:9) identified by (Id = 11078215) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 137.50 and NSFPQtyInStock = 0 and Id = 11078215'.
Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_ITEMS_ADVFLAG_PARETN_PRICE_STOCK' (ID 70). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:10834009:15) identified by (Id = 8885719) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 9.30 and NSFPQtyInStock = 0 and Id = 8885719'.
Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_ITEMS_ADVFLAG_PARETN_PRICE_STOCK' (ID 70). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:10945035:10) identified by (Id = 9750456) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 34.40 and NSFPQtyInStock = 0 and Id = 9750456'.
Msg 8951, Level 16, State 1, Line 1
Table error: table 'Items' (ID 1954106002). Data row does not have a matching index row in the index 'IX_ITEMS_ADVFLAG_PARETN_PRICE_STOCK' (ID 70). Possible missing or invalid keys for the index row matching:
Msg 8955, Level 16, State 1, Line 1
Data row (1:11226494:9) identified by (Id = 11078215) with index values 'AdvertiseFlag = 1 and BrandCopyParentId = 0 and NSFPPrice = 137.50 and NSFPQtyInStock = 0 and Id = 11078215'.
CHECKDB found 0 allocation errors and 6 consistency errors in table 'Items' (object ID 1954106002).
CHECKDB found 0 allocation errors and 6 consistency errors in database 'NewCatalog'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (NewCatalog).
Post #1429913
Posted Tuesday, March 12, 2013 10:41 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: Yesterday @ 8:36 AM
Points: 40,615, Visits: 37,080
Drop the indexes 'IX_Advertise_BrandCopy_Price_Stock' and 'IX_ITEMS_ADVFLAG_PARETN_PRICE_STOCK' (on the table 'Items') and recreate them. Don't rebuild them, drop and recreate.


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 #1429959
Posted Tuesday, March 12, 2013 10:43 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 6:20 AM
Points: 271, Visits: 415
GilaMonster (3/12/2013)
Drop the indexes 'IX_Advertise_BrandCopy_Price_Stock' and 'IX_ITEMS_ADVFLAG_PARETN_PRICE_STOCK' (on the table 'Items') and recreate them. Don't rebuild them, drop and recreate.


Doing so now. Our sysops guys checked the server and said there doesn't appear to be any issue with the hardware. How else can corruption like this occur?
Post #1429961
Posted Tuesday, March 12, 2013 10:45 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: Yesterday @ 8:36 AM
Points: 40,615, Visits: 37,080
IO subsystem problems in almost all cases. Could be as simple as a write cache that's not battery backed, could be misbehaving filter drives in the IO stack, etc.


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 #1429965
Posted Tuesday, March 12, 2013 10:46 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 6:20 AM
Points: 271, Visits: 415
GilaMonster (3/12/2013)
IO subsystem problems in almost all cases. Could be as simple as a write cache that's not battery backed, could be misbehaving filter drives in the IO stack, etc.


DROP and CREATE worked where REBUILD failed. Thank you.


EDIT: I think I'll have to do some reading to understand your answer here though haha
Post #1429967
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse