May 14, 2009 at 6:41 am
Hi -
I received a backup from one person.
When i tried to restore it, it went well, but i can not access the data inside some tables
.
I have made a dbcc checkdb allow data loss
and the result was this:
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 6750208 owned by data record identified by RID = (1:24:6) id = 3 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 111476736 owned by data record identified by RID = (1:92:3) id = 2055678371 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 41156608 owned by data record identified by RID = (1:93:0) id = 1819153526 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 34340864 owned by data record identified by RID = (1:93:4) id = 1886629764 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 34799616 owned by data record identified by RID = (1:93:7) id = 1886629764 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 42532864 owned by data record identified by RID = (1:140:1) id = 567673070 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 42663936 owned by data record identified by RID = (1:140:10) id = 631673298 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 216465408 owned by data record identified by RID = (1:140:15) id = 670625432 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 216727552 owned by data record identified by RID = (1:140:19) id = 670625432 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 20054016 owned by data record identified by RID = (1:247:0) id = 222623836 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 20381696 owned by data record identified by RID = (1:247:1) id = 222623836 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 3237543936 owned by data record identified by RID = (1:257:17) id = 1060198827 and indid = 10.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 40697856 owned by data record identified by RID = (1:257:18) id = 1067150847 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 46858240 owned by data record identified by RID = (1:258:5) id = 1243151474 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 163905536 owned by data record identified by RID = (1:258:16) id = 1243151474 and indid = 18.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 177012736 owned by data record identified by RID = (1:258:17) id = 1243151474 and indid = 19.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962755072 owned by data record identified by RID = (1:260:8) id = 397244470 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 78774272 owned by data record identified by RID = (1:260:12) id = 411148510 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 78839808 owned by data record identified by RID = (1:260:13) id = 411148510 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 78970880 owned by data record identified by RID = (1:260:15) id = 411148510 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 301596672 owned by data record identified by RID = (1:260:21) id = 420196547 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 190644224 owned by data record identified by RID = (1:261:5) id = 1243151474 and indid = 25.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 190971904 owned by data record identified by RID = (1:261:10) id = 1243151474 and indid = 30.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 191430656 owned by data record identified by RID = (1:261:17) id = 1243151474 and indid = 37.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 191496192 owned by data record identified by RID = (1:261:18) id = 1243151474 and indid = 38.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 210042880 owned by data record identified by RID = (1:262:14) id = 180195692 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 183566336 owned by data record identified by RID = (1:262:26) id = 219147826 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 118030336 owned by data record identified by RID = (1:263:8) id = 539148966 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962951680 owned by data record identified by RID = (1:457:7) id = 308196148 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7963017216 owned by data record identified by RID = (1:457:8) id = 308196148 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7963082752 owned by data record identified by RID = (1:457:9) id = 308196148 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 170459136 owned by data record identified by RID = (1:457:24) id = 354100302 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962820608 owned by data record identified by RID = (1:458:12) id = 445244641 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962886144 owned by data record identified by RID = (1:458:13) id = 445244641 and indid = 2.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:65), slot 0, text ID 40697856 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:66), slot 2, text ID 20381696 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:68), slot 4, text ID 78970880 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:68), slot 11, text ID 46858240 is not referenced.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:144) could not be processed. See other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 0, text ID 210042880 is referenced by page (1:66), slot 11, but was not seen in the scan.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:144), row 1. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 1798 and 1752.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 1, text ID 34799616 is referenced by page (1:79), slot 9, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 2, text ID 41156608 is referenced by page (1:64), slot 0, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 3, text ID 42532864 is referenced by page (1:145), slot 7, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 4, text ID 78839808 is referenced by page (1:260), slot 13, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 5, text ID 20054016 is referenced by page (1:111), slot 11, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 6, text ID 20381696 is referenced by page (1:247), slot 1, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 7, text ID 42663936 is referenced by page (1:95), slot 3, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 8, text ID 301596672 is referenced by page (1:260), slot 21, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 9, text ID 40697856 is referenced by page (1:257), slot 18, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 10, text ID 111476736 is referenced by page (1:92), slot 3, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 11, text ID 46858240 is referenced by page (1:258), slot 5, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 12, text ID 170459136 is referenced by page (1:457), slot 24, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 13, text ID 177012736 is referenced by page (1:258), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 14, text ID 183566336 is referenced by page (1:262), slot 26, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 15, text ID 190644224 is referenced by page (1:261), slot 5, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 16, text ID 190971904 is referenced by page (1:261), slot 10, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 17, text ID 191496192 is referenced by page (1:261), slot 18, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 18, text ID 34340864 is referenced by page (1:93), slot 4, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 19, text ID 7963082752 is referenced by page (1:4029), slot 2, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:441), slot 1, text ID 191496192 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:446), slot 23, text ID 78774272 is not referenced.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:464) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:464). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 0, text ID 6750208 is referenced by page (1:79), slot 2, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 1, text ID 3237543936 is referenced by page (1:257), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 2, text ID 78774272 is referenced by page (1:260), slot 12, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 3, text ID 78970880 is referenced by page (1:260), slot 15, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 4, text ID 7962755072 is referenced by page (1:260), slot 8, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 6, text ID 163905536 is referenced by page (1:258), slot 16, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 7, text ID 7962820608 is referenced by page (1:458), slot 12, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 8, text ID 191430656 is referenced by page (1:261), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 9, text ID 7962886144 is referenced by page (1:458), slot 13, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 11, text ID 7962951680 is referenced by page (1:457), slot 7, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 13, text ID 7963017216 is referenced by page (1:457), slot 8, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:466), slot 3, text ID 190644224 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:469), slot 4, text ID 190971904 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:497), slot 0, text ID 191430656 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:498), slot 0, text ID 177012736 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:499), slot 4, text ID 170459136 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:500), slot 0, text ID 216727552 does not match its reference from page (1:450), slot 11.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:904), slot 0, text ID 118030336 does not match its reference from page (1:95), slot 33.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:907), slot 2, text ID 34340864 is not referenced.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:910) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:910). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:910), slot 0, text ID 216465408 is referenced by page (1:449), slot 14, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:6630), slot 0, text ID 3237543936 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:15393), slot 0, text ID 78839808 is not referenced.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 2. Parent node for page (1:38280) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Parent node for page (1:3967) was not encountered.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:313) with values (TIPOOPERACAO = 1 and DATA = Apr 20 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1555) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:314) with values (TIPOOPERACAO = 1 and DATA = Apr 21 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1557) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:315) with values (TIPOOPERACAO = 1 and DATA = Apr 22 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1559) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:316) with values (TIPOOPERACAO = 1 and DATA = Apr 23 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1561) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:317) with values (TIPOOPERACAO = 1 and DATA = Apr 24 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1563) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:318) with values (TIPOOPERACAO = 1 and DATA = Apr 27 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1565) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:319) with values (TIPOOPERACAO = 1 and DATA = Apr 28 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1567) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:320) with values (TIPOOPERACAO = 1 and DATA = Apr 29 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1569) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:321) with values (TIPOOPERACAO = 1 and DATA = Apr 30 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1571) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:322) with values (TIPOOPERACAO = 1 and DATA = May 4 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1574) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:323) with values (TIPOOPERACAO = 1 and DATA = May 5 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1576) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:324) with values (TIPOOPERACAO = 1 and DATA = May 6 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1578) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:325) with values (TIPOOPERACAO = 1 and DATA = May 7 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1580) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:326) with values (TIPOOPERACAO = 1 and DATA = May 8 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1582) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:327) with values (TIPOOPERACAO = 1 and DATA = May 11 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1584) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:328) with values (TIPOOPERACAO = 1 and DATA = May 12 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1586) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:259) with values (TIPOOPERACAO = 0 and DATA = Apr 20 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1556) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:260) with values (TIPOOPERACAO = 0 and DATA = Apr 21 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1558) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:261) with values (TIPOOPERACAO = 0 and DATA = Apr 22 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1560) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:262) with values (TIPOOPERACAO = 0 and DATA = Apr 23 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1562) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:263) with values (TIPOOPERACAO = 0 and DATA = Apr 24 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1564) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:264) with values (TIPOOPERACAO = 0 and DATA = Apr 27 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1566) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:265) with values (TIPOOPERACAO = 0 and DATA = Apr 28 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1568) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:266) with values (TIPOOPERACAO = 0 and DATA = Apr 29 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1570) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:267) with values (TIPOOPERACAO = 0 and DATA = Apr 30 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1572) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:268) with values (TIPOOPERACAO = 0 and DATA = Apr 30 2009 12:00AM and TIPOFECHO = 2 and CODFECHOABERTURA = 1573) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:269) with values (TIPOOPERACAO = 0 and DATA = May 4 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1575) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:270) with values (TIPOOPERACAO = 0 and DATA = May 5 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1577) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:271) with values (TIPOOPERACAO = 0 and DATA = May 6 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1579) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:272) with values (TIPOOPERACAO = 0 and DATA = May 7 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1581) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:273) with values (TIPOOPERACAO = 0 and DATA = May 8 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1583) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:274) with values (TIPOOPERACAO = 0 and DATA = May 11 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1585) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:275) with values (TIPOOPERACAO = 0 and DATA = May 12 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1587) points to the data row identified by ().
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 992722589, index ID 0: Page (1:6144) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 992722589, index ID 0, page (1:6144). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 992722589, index ID 1. Page (1:6144) was not seen in the scan although its parent (1:22924) and previous (1:333) refer to it. Check any previous errors.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. The previous link (1:20979) on page (1:7176) does not match the previous page (1:37449) that the parent (1:23287), slot 46 expects for this page.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. B-tree chain linkage mismatch. (1:37449)->next = (1:7176), but (1:7176)->Prev = (1:20979).
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. The previous link (1:20982) on page (1:7178) does not match the previous page (1:37696) that the parent (1:23287), slot 56 expects for this page.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. B-tree chain linkage mismatch. (1:37696)->next = (1:7178), but (1:7178)->Prev = (1:20982).
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:745) is missing a reference from previous page (1:11124). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:1941) is missing a reference from previous page (1:10604). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:2197) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:2197). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:2197) was not seen in the scan although its parent (1:21405) and previous (1:10155) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:4146) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:4146). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:4146) was not seen in the scan although its parent (1:21405) and previous (1:22234) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:4547) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:4547). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:4547) was not seen in the scan although its parent (1:21405) and previous (1:11633) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:5101) is missing a reference from previous page (1:11092). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:7759) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:7759). Test (m_freeCnt == freeCnt) failed. Values are 2 and 53.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:7759). Test (emptySlotCnt == 0) failed. Values are 3 and 0.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:7759) was not seen in the scan although its parent (1:21405) and previous (1:36217) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:10604) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:10604). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:10604) was not seen in the scan although its parent (1:21405) and previous (1:4144) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:10798) is missing a reference from previous page (1:12468). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11092) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11092). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11092) was not seen in the scan although its parent (1:21404) and previous (1:3478) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11124) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11124). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11124) was not seen in the scan although its parent (1:21405) and previous (1:7942) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11291) is missing a reference from previous page (1:4547). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11338) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11338). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 376, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11338). Test (sorted.offset >= max) failed. Slot 0, offset 0x178 overlaps with the prior row.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11338) was not seen in the scan although its parent (1:21405) and previous (1:32002) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11546) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11546). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11546) was not seen in the scan although its parent (1:21404) and previous (1:10936) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11681) is missing a reference from previous page (1:12268). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11738) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11738). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11738) was not seen in the scan although its parent (1:21405) and previous (1:33202) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:12268) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:12268). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:12268) was not seen in the scan although its parent (1:21405) and previous (1:3927) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:12468) could not be processed. See other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:12468) was not seen in the scan although its parent (1:21405) and previous (1:351) refer to it. Check any previous errors.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:12468), row 207. Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:22464) is missing a reference from previous page (1:11338). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:23273) is missing a reference from previous page (1:11738). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:24741) is missing a reference from previous page (1:11546). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:32004) is missing a reference from previous page (1:4146). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:34457) is missing a reference from previous page (1:2197). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:37720) is missing a reference from previous page (1:7759). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:38153) is missing a reference from previous page (1:541). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 1611152785, index ID 1. Parent node for page (1:38216) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:4751) is missing a reference from previous page (1:9589). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:5885) is missing a reference from previous page (1:11298). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:9581) is missing a reference from previous page (1:10684). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:9585) is missing a reference from previous page (1:10892). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:9589) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:9589). Test (m_freeCnt == freeCnt) failed. Values are 1826 and 1877.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:9589). Test (emptySlotCnt == 0) failed. Values are 3 and 0.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:9589) was not seen in the scan although its parent (1:10894) and previous (1:13528) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:10684) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:10684). Test (emptySlotCnt == 0) failed. Values are 16 and 0.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:10684). Test (m_freeCnt == freeCnt) failed. Values are 2434 and 2706.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:10684) was not seen in the scan although its parent (1:10893) and previous (1:8393) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:10892) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:10892). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:10892) was not seen in the scan although its parent (1:10894) and previous (1:4512) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:11298) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:11298). Test (m_freeCnt == freeCnt) failed. Values are 3289 and 3561.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:11298). Test (emptySlotCnt == 0) failed. Values are 16 and 0.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:11298) was not seen in the scan although its parent (1:10893) and previous (1:1978) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:38144) is missing a reference from previous page (1:4104). Possible chain linkage problem.
DBCC results for 'SGTA'.
DBCC results for 'sysobjects'.
There are 437 rows in 9 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
The repair level on the DBCC statement caused this repair to be bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
There are 441 rows in 20 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 88 consistency errors in table 'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 1165 rows in 22 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 263 rows in 21 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 18 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 16 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 49 rows in 2 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 592 rows in 3 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 63 rows in 1 pages for object 'sysreferences'.
...........................................................................
...........................................................................
...........................................................................
I think that the problem is one the indexes of some tables.
If i drop all the indexes and then create it again will the database be fixed?
p.s He as no more backups other than this.........
May 14, 2009 at 7:08 am
Looks like you may have some irreparable corruption there. Can you please run the following so that I can see exactly what errors remain. Please post the full results.
DBCC CHECKDB(<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 14, 2009 at 7:32 am
what is the difference between allocation errors and concistency errors?
the result of the command:
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 6750208 owned by data record identified by RID = (1:24:6) id = 3 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 111476736 owned by data record identified by RID = (1:92:3) id = 2055678371 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 41156608 owned by data record identified by RID = (1:93:0) id = 1819153526 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 34340864 owned by data record identified by RID = (1:93:4) id = 1886629764 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 34799616 owned by data record identified by RID = (1:93:7) id = 1886629764 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 42532864 owned by data record identified by RID = (1:140:1) id = 567673070 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 42663936 owned by data record identified by RID = (1:140:10) id = 631673298 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 216465408 owned by data record identified by RID = (1:140:15) id = 670625432 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 216727552 owned by data record identified by RID = (1:140:19) id = 670625432 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 20054016 owned by data record identified by RID = (1:247:0) id = 222623836 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 20381696 owned by data record identified by RID = (1:247:1) id = 222623836 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 3237543936 owned by data record identified by RID = (1:257:17) id = 1060198827 and indid = 10.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 40697856 owned by data record identified by RID = (1:257:18) id = 1067150847 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 46858240 owned by data record identified by RID = (1:258:5) id = 1243151474 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 163905536 owned by data record identified by RID = (1:258:16) id = 1243151474 and indid = 18.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 177012736 owned by data record identified by RID = (1:258:17) id = 1243151474 and indid = 19.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962755072 owned by data record identified by RID = (1:260:8) id = 397244470 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 78774272 owned by data record identified by RID = (1:260:12) id = 411148510 and indid = 4.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 78839808 owned by data record identified by RID = (1:260:13) id = 411148510 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 78970880 owned by data record identified by RID = (1:260:15) id = 411148510 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 301596672 owned by data record identified by RID = (1:260:21) id = 420196547 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 190644224 owned by data record identified by RID = (1:261:5) id = 1243151474 and indid = 25.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 190971904 owned by data record identified by RID = (1:261:10) id = 1243151474 and indid = 30.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 191430656 owned by data record identified by RID = (1:261:17) id = 1243151474 and indid = 37.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 191496192 owned by data record identified by RID = (1:261:18) id = 1243151474 and indid = 38.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 210042880 owned by data record identified by RID = (1:262:14) id = 180195692 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 183566336 owned by data record identified by RID = (1:262:26) id = 219147826 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 118030336 owned by data record identified by RID = (1:263:8) id = 539148966 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962951680 owned by data record identified by RID = (1:457:7) id = 308196148 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7963017216 owned by data record identified by RID = (1:457:8) id = 308196148 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7963082752 owned by data record identified by RID = (1:457:9) id = 308196148 and indid = 3.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 170459136 owned by data record identified by RID = (1:457:24) id = 354100302 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962820608 owned by data record identified by RID = (1:458:12) id = 445244641 and indid = 1.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 7962886144 owned by data record identified by RID = (1:458:13) id = 445244641 and indid = 2.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:65), slot 0, text ID 40697856 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:66), slot 2, text ID 20381696 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:68), slot 4, text ID 78970880 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:68), slot 11, text ID 46858240 is not referenced.
Server: Msg 8928, Level 16, State 1, Lect ID 2, index ID 255: Page (1:144) could not be processed. ine 1
ObjSee other errors for details.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:144), slot 0, text ID 210042880 is referenced by page (1:66), slot 11, but was not seen in the scan.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:144), row 1. Test (ColumnOffsets bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 0, text ID 6750208 is referenced by page (1:79), slot 2, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 1, text ID 3237543936 is referenced by page (1:257), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 2, text ID 78774272 is referenced by page (1:260), slot 12, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 3, text ID 78970880 is referenced by page (1:260), slot 15, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 4, text ID 7962755072 is referenced by page (1:260), slot 8, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 6, text ID 163905536 is referenced by page (1:258), slot 16, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 7, text ID 7962820608 is referenced by page (1:458), slot 12, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 8, text ID 191430656 is referenced by page (1:261), slot 17, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 9, text ID 7962886144 is referenced by page (1:458), slot 13, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 11, text ID 7962951680 is referenced by page (1:457), slot 7, but was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:464), slot 13, text ID 7963017216 is referenced by page (1:457), slot 8, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:466), slot 3, text ID 190644224 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:469), slot 4, text ID 190971904 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:497), slot 0, text ID 191430656 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:498), slot 0, text ID 177012736 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:499), slot 4, text ID 170459136 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:500), slot 0, text ID 216727552 does not match its reference from page (1:450), slot 11.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:904), slot 0, text ID 118030336 does not match its reference from page (1:95), slot 33.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:907), slot 2, text ID 34340864 is not referenced.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:910) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:910). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:910), slot 0, text ID 216465408 is referenced by page (1:449), slot 14, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:6630), slot 0, text ID 3237543936 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:15393), slot 0, text ID 78839808 is not referenced.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 411148510, index ID 2. Parent node for page (1:38280) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 606625204, index ID 1. Parent node for page (1:3967) was not encountered.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:313) with values (TIPOOPERACAO = 1 and DATA = Apr 20 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1555) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:314) with values (TIPOOPERACAO = 1 and DATA = Apr 21 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1557) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:315) with values (TIPOOPERACAO = 1 and DATA = Apr 22 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1559) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:316) with values (TIPOOPERACAO = 1 and DATA = Apr 23 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1561) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:317) with values (TIPOOPERACAO = 1 and DATA = Apr 24 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1563) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:318) with values (TIPOOPERACAO = 1 and DATA = Apr 27 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1565) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:319) with values (TIPOOPERACAO = 1 and DATA = Apr 28 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1567) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:320) with values (TIPOOPERACAO = 1 and DATA = Apr 29 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1569) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:321) with values (TIPOOPERACAO = 1 and DATA = Apr 30 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1571) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:322) with values (TIPOOPERACAO = 1 and DATA = May 4 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1574) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:323) with values (TIPOOPERACAO = 1 and DATA = May 5 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1576) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:324) with values (TIPOOPERACAO = 1 and DATA = May 6 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1578) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:325) with values (TIPOOPERACAO = 1 and DATA = May 7 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1580) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:326) with values (TIPOOPERACAO = 1 and DATA = May 8 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1582) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:327) with values (TIPOOPERACAO = 1 and DATA = May 11 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1584) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:13287:328) with values (TIPOOPERACAO = 1 and DATA = May 12 2009 12:00AM and TIPOFECHO = 0 and CODFECHOABERTURA = 1586) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:259) with values (TIPOOPERACAO = 0 and DATA = Apr 20 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1556) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:260) with values (TIPOOPERACAO = 0 and DATA = Apr 21 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1558) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:261) with values (TIPOOPERACAO = 0 and DATA = Apr 22 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1560) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:262) with values (TIPOOPERACAO = 0 and DATA = Apr 23 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1562) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:263) with values (TIPOOPERACAO = 0 and DATA = Apr 24 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1564) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:264) with values (TIPOOPERACAO = 0 and DATA = Apr 27 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1566) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:265) with values (TIPOOPERACAO = 0 and DATA = Apr 28 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1568) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:266) with values (TIPOOPERACAO = 0 and DATA = Apr 29 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1570) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:267) with values (TIPOOPERACAO = 0 and DATA = Apr 30 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1572) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:268) with values (TIPOOPERACAO = 0 and DATA = Apr 30 2009 12:00AM and TIPOFECHO = 2 and CODFECHOABERTURA = 1573) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:269) with values (TIPOOPERACAO = 0 and DATA = May 4 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1575) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:270) with values (TIPOOPERACAO = 0 and DATA = May 5 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1577) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:271) with values (TIPOOPERACAO = 0 and DATA = May 6 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1579) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:272) with values (TIPOOPERACAO = 0 and DATA = May 7 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1581) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:273) with values (TIPOOPERACAO = 0 and DATA = May 8 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1583) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:274) with values (TIPOOPERACAO = 0 and DATA = May 11 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1585) points to the data row identified by ().
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'SGTA', index 'FECHOABERTURA.AK_FECHOABERTURA_TO_DT_TF' (ID 958626458) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:24419:275) with values (TIPOOPERACAO = 0 and DATA = May 12 2009 12:00AM and TIPOFECHO = 1 and CODFECHOABERTURA = 1587) points to the data row identified by ().
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 992722589, index ID 0: Page (1:6144) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 992722589, index ID 0, page (1:6144). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 992722589, index ID 1. Page (1:6144) was not seen in the scan although its parent (1:22924) and previous (1:333) refer to it. Check any previous errors.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. The previous link (1:20979) on page (1:7176) does not match the previous page (1:37449) that the parent (1:23287), slot 46 expects for this page.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. B-tree chain linkage mismatch. (1:37449)->next = (1:7176), but (1:7176)->Prev = (1:20979).
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. The previous link (1:20982) on page (1:7178) does not match the previous page (1:37696) that the parent (1:23287), slot 56 expects for this page.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 2. B-tree chain linkage mismatch. (1:37696)->next = (1:7178), but (1:7178)->Prev = (1:20982).
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:745) is missing a reference from previous page (1:11124). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:1941) is missing a reference from previous page (1:10604). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:2197) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:2197). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:2197) was not seen in the scan although its parent (1:21405) and previous (1:10155) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:4146) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:4146). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:4146) was not seen in the scan although its parent (1:21405) and previous (1:22234) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:4547) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:4547). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:4547) was not seen in the scan although its parent (1:21405) and previous (1:11633) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:5101) is missing a reference from previous page (1:11092). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:7759) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:7759). Test (m_freeCnt == freeCnt) failed. Values are 2 and 53.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:7759). Test (emptySlotCnt == 0) failed. Values are 3 and 0.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:7759) was not seen in the scan although its parent (1:21405) and previous (1:36217) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:10604) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:10604). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:10604) was not seen in the scan although its parent (1:21405) and previous (1:4144) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:10798) is missing a reference from previous page (1:12468). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11092) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11092). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11092) was not seen in the scan although its parent (1:21404) and previous (1:3478) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11124) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11124). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11124) was not seen in the scan although its parent (1:21405) and previous (1:7942) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11291) is missing a reference from previous page (1:4547). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11338) could not be processed. See other errors for details.
Server: Msg 8941, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11338). Test (sorted .offset >= PAGEHEADSIZE) failed. Slot 376, offset 0x1 is invalid.
Server: Msg 8942, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11338). Test (sorted.offset >= max) failed. Slot 0, offset 0x178 overlaps with the prior row.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11338) was not seen in the scan although its parent (1:21405) and previous (1:32002) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11546) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11546). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11546) was not seen in the scan although its parent (1:21404) and previous (1:10936) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11681) is missing a reference from previous page (1:12268). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:11738) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:11738). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:11738) was not seen in the scan although its parent (1:21405) and previous (1:33202) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:12268) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:12268). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:12268) was not seen in the scan although its parent (1:21405) and previous (1:3927) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1243151474, index ID 3: Page (1:12468) could not be processed. See other errors for details.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:12468) was not seen in the scan although its parent (1:21405) and previous (1:351) refer to it. Check any previous errors.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3, page (1:12468), row 207. Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:22464) is missing a reference from previous page (1:11338). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:23273) is missing a reference from previous page (1:11738). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:24741) is missing a reference from previous page (1:11546). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:32004) is missing a reference from previous page (1:4146). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:34457) is missing a reference from previous page (1:2197). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:37720) is missing a reference from previous page (1:7759). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1243151474, index ID 3. Page (1:38153) is missing a reference from previous page (1:541). Possible chain linkage problem.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 1611152785, index ID 1. Parent node for page (1:38216) was not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:4751) is missing a reference from previous page (1:9589). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:5885) is missing a reference from previous page (1:11298). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:9581) is missing a reference from previous page (1:10684). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:9585) is missing a reference from previous page (1:10892). Possible chain linkage problem.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:9589) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:9589). Test (m_freeCnt == freeCnt) failed. Values are 1826 and 1877.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:9589). Test (emptySlotCnt == 0) failed. Values are 3 and 0.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:9589) was not seen in the scan although its parent (1:10894) and previous (1:13528) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:10684) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:10684). Test (emptySlotCnt == 0) failed. Values are 16 and 0.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:10684). Test (m_freeCnt == freeCnt) failed. Values are 2434 and 2706.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:10684) was not seen in the scan although its parent (1:10893) and previous (1:8393) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:10892) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:10892). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:10892) was not seen in the scan although its parent (1:10894) and previous (1:4512) refer to it. Check any previous errors.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1886629764, index ID 2: Page (1:11298) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:11298). Test (m_freeCnt == freeCnt) failed. Values are 3289 and 3561.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2, page (1:11298). Test (emptySlotCnt == 0) failed. Values are 16 and 0.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:11298) was not seen in the scan although its parent (1:10893) and previous (1:1978) refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1886629764, index ID 2. Page (1:38144) is missing a reference from previous page (1:4104). Possible chain linkage problem.
CHECKDB found 0 allocation errors and 88 consistency errors in table 'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'ANULACAO' (object ID 411148510).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'REPORTLEVEL' (object ID 606625204).
CHECKDB found 0 allocation errors and 33 consistency errors in table 'FECHOABERTURA' (object ID 958626458).
CHECKDB found 0 allocation errors and 3 consistency errors in table 'EXPORTLOG' (object ID 992722589).
CHECKDB found 0 allocation errors and 55 consistency errors in table 'LIQUIDACAO' (object ID 1243151474).
CHECKDB found 0 allocation errors and 1 consistency errors in table 'LOG_OPERATION' (object ID 1611152785).
CHECKDB found 0 allocation errors and 20 consistency errors in table 'CCCONTRIBUINTE' (object ID 1886629764).
CHECKDB found 0 allocation errors and 202 consistency errors in database 'SGTA'.
thank you, for your help,
Pedro
May 14, 2009 at 10:59 am
Ok, two things.
1) This is not completely repairable.
2) You're going to lose data and you probably already lost a lot in the previous repair
I suspect (and will get a second opinion) that if you run checkDB with the repair_allow_data_loss option again, the errors in the non-system tables will get fixed. It will do so by discarding the pages that are affected, and you're got a fair few of those. Most in the nonclustered indexes, but I did notice a couple on index 0 or 1. The errors look like they could be the result of fixes that were done by the previous repair that you did.
No amount of repairs is going to fix the errors in sysindexes though. CheckDB will not repair the system tables. To get rid of those you're going to have to recreate the database.
Generate scripts of all the objects
BCP all the data out
Create a new database
Run the scripts in there to recreate the objects
Reload the data
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 14, 2009 at 12:38 pm
Gail asked me to chime in here.
The sysindexes errors are corruptions in the statistics blobs - you should be able to get around those by dropping and recreating all your statistics.
The other errors should be fixed by repair. I didn't look really closely at all the errors from each DBCC, but there may have been some errors that were hidden by the first set of corruptions that were fixed.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
May 14, 2009 at 2:28 pm
Paul Randal (5/14/2009)
The sysindexes errors are corruptions in the statistics blobs - you should be able to get around those by dropping and recreating all your statistics.
Drop and recreate all indexes as well, seeing as a couple reference indid 1 as the 'statistic' that's damaged?
There's one that looks like an index on a system table.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 6750208 owned by data record identified by RID = (1:24:6) id = 3 and indid = 2.
I don't have 2000 installed anymore. Was it possible to drop an index from a system table?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 14, 2009 at 5:19 pm
Dropping system table indexes - not in any documented way.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
January 6, 2010 at 5:33 am
We have just got a similar error (see below) only on the sysindexes table of a database which we cannot easily put into standalone mode.
I cannot tell what the recommendation of this thread was in the end - regarding rebuilding the sysindexes table.
I am very new to SQL (Oracle is my forte) so I'm rather lost as to how important this error is and what to do to resolve it.
#
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 315 consistency errors in table 'sysindexes' (object ID 2).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 315 consistency errors in database 'SurfControl_WebFilter'.
#
I hope it is ok to add to this thread rather than rasing a new one.
Thanks
January 6, 2010 at 7:14 am
Please rather post new questions in a new thread. Often people won't look at threads with lots of answers, assuming they are resolved.
In a new thread, please post the full and complete output of the following:
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
The sysindexes table cannot be rebuilt, and the solution depends completely on the details of the problem.
Do you have a clean backup? One that doesn't have the corruption in it?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply