Jul 26, 2007
In my ERRORLOG file I have this error come up able every 10 minutes:
2007-07-26 08:16:31.93 spid65 Getpage: bstat=0x9, sstat=0x10000, cache
2007-07-26 08:16:31.93 spid65 pageno is/should be:objid is/should be:
2007-07-26 08:16:31.93 spid65 (1:3435)/(1:3435)1573580644/18099105
2007-07-26 08:16:31.93 spid65 ... IAM indicates that page is NOT allocated to this object
2007-07-26 08:16:31.93 spid65 Error: 605, Severity: 21, State: 1
2007-07-26 08:16:31.93 spid65 Attempt to fetch logical page (1:3435) in database 'PDP' belongs to object 'EMP_SHIFT_DETAIL', not to object 'TRACKED_ITEMS'..
Here is the output of DBCC CHECKDB
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 852426752 owned by data record identified by RID = (1:110:19) id = 1925581898 and indid = 2.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:438), slot 3, text ID 852426752 is referenced by page (1:71), slot 4, but was not seen in the scan.
DBCC results for 'PDP'.
DBCC results for 'sysobjects'.
There are 652 rows in 11 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 480 rows in 18 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 3692 rows in 62 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 381 rows in 120 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 12 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 1650 rows in 8 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'TRACKED_ITEM_TOTAL_READING' (ID 2099048). Missing or invalid key in index 'TRACKED_ITEM_TTL_READNG_INDEX' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3280:54) identified by (RID = (1:3280:54) ) has index values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:0) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3285:83)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:1) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3285:84)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:2) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3286:8)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:3) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3286:9)).
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'TRACKED_ITEM_TOTAL_READING'.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:4) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3286:27)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:6) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3285:85)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:7) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3285:86)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:8) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3286:10)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:9) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3286:11)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:10) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3286:28)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:12) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3285:87)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:13) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3285:88)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:14) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:12)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:15) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:13)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:16) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:29)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:17) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:30)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:19) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3285:89)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:20) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3285:90)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:21) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3286:14)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:22) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3286:15)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:24) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 201500) points to the data row identified by (RID = (1:3285:91)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:25) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 201500) points to the data row identified by (RID = (1:3286:16)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:27) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3285:92)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:28) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3286:17)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:29) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3286:31)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:30) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3286:47)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:32) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:32)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:33) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:33)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:34) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:48)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:35) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:49)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:37) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 210000) points to the data row identified by (RID = (1:3286:34)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:38) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 210000) points to the data row identified by (RID = (1:3286:50)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:39) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 210000) points to the data row identified by (RID = (1:3286:51)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:41) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 211500) points to the data row identified by (RID = (1:3286:52)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:42) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 211500) points to the data row identified by (RID = (1:3286:53)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:44) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:35)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:45) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:36)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:46) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:54)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:47) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:55)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:49) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 214500) points to the data row identified by (RID = (1:3286:37)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:50) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 214500) points to the data row identified by (RID = (1:3286:38)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:52) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 220000) points to the data row identified by (RID = (1:3286:39)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:53) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 220000) points to the data row identified by (RID = (1:3286:40)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:55) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 221500) points to the data row identified by (RID = (1:3285:93)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:56) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 221500) points to the data row identified by (RID = (1:3285:94)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:57) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 221500) points to the data row identified by (RID = (1:3286:41)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:58) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3285:95)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:59) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3285:96)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:60) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3286:56)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:61) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3286:59)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:63) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 224500) points to the data row identified by (RID = (1:3286:42)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:64) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 224500) points to the data row identified by (RID = (1:3286:57)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:65) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 224500) points to the data row identified by (RID = (1:3286:61)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:67) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 230000) points to the data row identified by (RID = (1:3286:43)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:69) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 231500) points to the data row identified by (RID = (1:3286:44)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:70) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 231500) points to the data row identified by (RID = (1:3286:45)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:71) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 231500) points to the data row identified by (RID = (1:3286:60)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:73) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 233000) points to the data row identified by (RID = (1:3286:46)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:75) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 234500) points to the data row identified by (RID = (1:3286:58)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:40) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 130000) points to the data row identified by (RID = (1:3282:0)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:41) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 130000) points to the data row identified by (RID = (1:3282:1)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:47) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 131500) points to the data row identified by (RID = (1:3282:2)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:48) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 131500) points to the data row identified by (RID = (1:3282:3)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:52) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000) points to the data row identified by (RID = (1:3282:4)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:53) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000) points to the data row identified by (RID = (1:3282:5)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:55) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000) points to the data row identified by (RID = (1:3285:0)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:56) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3280:54)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:57) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3280:55)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:60) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3282:6)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:61) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3282:7)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:63) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 140000) points to the data row identified by (RID = (1:3280:56)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:64) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 140000) points to the data row identified by (RID = (1:3280:79)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:67) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 141500) points to the data row identified by (RID = (1:3280:80)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:68) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 141500) points to the data row identified by (RID = (1:3280:89)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:71) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 141500) points to the data row identified by (RID = (1:3282:8)).
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2669) is missing a reference from previous page (1:3126). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2687) is missing a reference from previous page (1:3438). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2842) is missing a reference from previous page (1:3439). Possible chain linkage problem.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. The next pointer of (1:3124) refers to page (1:2844). Neither (1:2844) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2845) is missing references from parent (unknown) and previous (page (1:2843)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2912) is missing a reference from previous page (1:3437). Possible chain linkage problem.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3054) is missing references from parent (unknown) and previous (page (1:2912)) nodes. Possible bad root entry in sysindexes.
There are 8402 rows in 87 pages for object 'TRACKED_ITEM_TOTAL_READING'.
CHECKDB found 0 allocation errors and 76 consistency errors in table 'TRACKED_ITEM_TOTAL_READING' (object ID 2099048).
DBCC results for 'CREDIT_LINE_ITEM'.
There are 0 rows in 0 pages for object 'CREDIT_LINE_ITEM'.
DBCC results for 'Stepped_Table_Header'.
There are 0 rows in 0 pages for object 'Stepped_Table_Header'.
DBCC results for 'TRACKED_ITEMS'.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3121) is missing references from parent (unknown) and previous (page (1:2687)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3123) is missing references from parent (unknown) and previous (page (1:3271)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. B-tree chain linkage mismatch. (1:3054)->next = (1:3124), but (1:3124)->Prev = (1:2912).
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Parent node for page (1:3124) was not encountered.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. B-tree chain linkage mismatch. (1:3127)->next = (1:3125), but (1:3125)->Prev = (1:3148).
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Parent node for page (1:3125) was not encountered.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3126) was not seen in the scan although its parent (1:3567) and previous (1:3125) refer to it. Check any previous errors.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3127) is missing references from parent (unknown) and previous (page (1:3433)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3144) is missing a reference from previous page (1:3432). Possible chain linkage problem.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Index node page (1:3567), slot 94 refers to child page (1:3148) and previous child (1:3433), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Index node page (1:3567), slot 103 refers to child page (1:3150) and previous child (1:3434), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3151) is missing a reference from previous page (1:3664). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3267) is missing a reference from previous page (1:3150). Possible chain linkage problem.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. B-tree chain linkage mismatch. (1:3123)->next = (1:3485), but (1:3485)->Prev = (1:3271).
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Parent node for page (1:3485) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3486) is missing references from parent (unknown) and previous (page (1:3052)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 79, in object ID 18099105, index ID 1, refers to page (1:3435), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 80, in object ID 18099105, index ID 1, refers to page (1:3439), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 83, in object ID 18099105, index ID 1, refers to page (1:3438), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 86, in object ID 18099105, index ID 1, refers to page (1:3436), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 91, in object ID 18099105, index ID 1, refers to page (1:3437), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 93, in object ID 18099105, index ID 1, refers to page (1:3433), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 99, in object ID 18099105, index ID 1, refers to page (1:3432), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 102, in object ID 18099105, index ID 1, refers to page (1:3434), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Index node page (1:3567), slot 87 refers to child page (1:3664) and previous child (1:3436), but they were not encountered.
There are 23644 rows in 359 pages for object 'TRACKED_ITEMS'.
CHECKDB found 0 allocation errors and 32 consistency errors in table 'TRACKED_ITEMS' (object ID 18099105).
DBCC results for 'SAFE_CONFIG_DETAIL'.
There are 0 rows in 0 pages for object 'SAFE_CONFIG_DETAIL'.
DBCC results for 'Currency'.
There are 11 rows in 1 pages for object 'Currency'.
DBCC results for 'RECIPE_INGREDIENT_XML'.
There are 0 rows in 0 pages for object 'RECIPE_INGREDIENT_XML'.
DBCC results for 'LINE_ITEMS'.
There are 0 rows in 0 pages for object 'LINE_ITEMS'.
DBCC results for 'TMP_OVERSHORT'.
There are 0 rows in 0 pages for object 'TMP_OVERSHORT'.
DBCC results for 'SAFE_DETAILS'.
There are 0 rows in 0 pages for object 'SAFE_DETAILS'.
DBCC results for 'SchemaVersions'.
There are 1 rows in 1 pages for object 'SchemaVersions'.
DBCC results for 'TRANSFER'.
There are 0 rows in 0 pages for object 'TRANSFER'.
DBCC results for 'Stepped_Table_Step'.
There are 0 rows in 0 pages for object 'Stepped_Table_Step'.
DBCC results for 'SAFE_MANAGEMENT'.
There are 0 rows in 0 pages for object 'SAFE_MANAGEMENT'.
DBCC results for 'RECIPE_XML'.
There are 0 rows in 0 pages for object 'RECIPE_XML'.
DBCC results for 'RETURN_ITEM_DETAIL'.
There are 0 rows in 0 pages for object 'RETURN_ITEM_DETAIL'.
DBCC results for 'INI_CONFIGURATION'.
There are 0 rows in 0 pages for object 'INI_CONFIGURATION'.
DBCC results for 'RETURN_ITEM'.
There are 0 rows in 0 pages for object 'RETURN_ITEM'.
DBCC results for 'DEPOSIT_CONFIG'.
There are 0 rows in 0 pages for object 'DEPOSIT_CONFIG'.
DBCC results for 'INV_BATCH'.
There are 0 rows in 0 pages for object 'INV_BATCH'.
DBCC results for 'Scheduler_Settings'.
There are 0 rows in 0 pages for object 'Scheduler_Settings'.
DBCC results for 'DEPOSIT_CONFIG_DETAIL'.
There are 0 rows in 0 pages for object 'DEPOSIT_CONFIG_DETAIL'.
DBCC results for 'RM_RECON_CAL_MTD_XML'.
There are 0 rows in 0 pages for object 'RM_RECON_CAL_MTD_XML'.
DBCC results for 'WASTE_TEMPLATE'.
There are 0 rows in 0 pages for object 'WASTE_TEMPLATE'.
DBCC results for 'DEPOSIT_DETAILS'.
There are 0 rows in 0 pages for object 'DEPOSIT_DETAILS'.
DBCC results for 'WASTE_TEMPLATE_ITEM'.
There are 0 rows in 0 pages for object 'WASTE_TEMPLATE_ITEM'.
DBCC results for 'RM_UNIT_XML'.
There are 0 rows in 0 pages for object 'RM_UNIT_XML'.
DBCC results for 'PO_TEMPLATE'.
There are 0 rows in 0 pages for object 'PO_TEMPLATE'.
DBCC results for 'ACTION'.
There are 0 rows in 0 pages for object 'ACTION'.
DBCC results for 'AEIC_CODES'.
There are 5 rows in 1 pages for object 'AEIC_CODES'.
DBCC results for 'PO_TEMPLATE_DETAIL'.
There are 0 rows in 0 pages for object 'PO_TEMPLATE_DETAIL'.
DBCC results for 'DAILY_OVERTIME'.
There are 3 rows in 1 pages for object 'DAILY_OVERTIME'.
DBCC results for 'EMP_PUNCH'.
There are 0 rows in 0 pages for object 'EMP_PUNCH'.
DBCC results for 'SUBLOCATION_XML'.
There are 0 rows in 0 pages for object 'SUBLOCATION_XML'.
DBCC results for 'RM_TRAN_SUMMARY'.
There are 0 rows in 0 pages for object 'RM_TRAN_SUMMARY'.
DBCC results for 'Scheduler_Shifts'.
There are 0 rows in 0 pages for object 'Scheduler_Shifts'.
DBCC results for 'EMP_PUNCH_HISTORY'.
There are 0 rows in 0 pages for object 'EMP_PUNCH_HISTORY'.
DBCC results for 'EMPLOYEE_ACTION'.
There are 0 rows in 0 pages for object 'EMPLOYEE_ACTION'.
DBCC results for 'MIDEPT_TRAN_SUMMARY'.
There are 0 rows in 0 pages for object 'MIDEPT_TRAN_SUMMARY'.
DBCC results for 'EMPLOYEE_GROUP'.
There are 0 rows in 0 pages for object 'EMPLOYEE_GROUP'.
DBCC results for 'EMPLOYEE_HOUR'.
There are 0 rows in 0 pages for object 'EMPLOYEE_HOUR'.
DBCC results for 'VENDOR_RAWMAT_XML'.
There are 0 rows in 0 pages for object 'VENDOR_RAWMAT_XML'.
DBCC results for 'FIFO_BUCKET'.
There are 0 rows in 0 pages for object 'FIFO_BUCKET'.
DBCC results for 'EMPLOYEE_JOB_LABOR'.
There are 0 rows in 0 pages for object 'EMPLOYEE_JOB_LABOR'.
DBCC results for 'EMPLOYEE_LABOR'.
There are 0 rows in 0 pages for object 'EMPLOYEE_LABOR'.
DBCC results for 'INV_TRANSACTION'.
There are 158 rows in 2 pages for object 'INV_TRANSACTION'.
DBCC results for 'EMPLOYEE_TAX_DETAIL'.
There are 0 rows in 0 pages for object 'EMPLOYEE_TAX_DETAIL'.
DBCC results for 'ETHNIC_GROUP'.
There are 6 rows in 1 pages for object 'ETHNIC_GROUP'.
DBCC results for 'VENDOR_RM_DETAIL_XML'.
There are 0 rows in 0 pages for object 'VENDOR_RM_DETAIL_XML'.
DBCC results for 'INV_RECONCILIATION'.
There are 0 rows in 0 pages for object 'INV_RECONCILIATION'.
DBCC results for 'DCS_SUPPORT'.
There are 0 rows in 0 pages for object 'DCS_SUPPORT'.
DBCC results for 'JOB'.
There are 0 rows in 0 pages for object 'JOB'.
DBCC results for 'DCS_LABOR'.
There are 0 rows in 0 pages for object 'DCS_LABOR'.
DBCC results for 'LABOR'.
There are 0 rows in 0 pages for object 'LABOR'.
DBCC results for 'INV_THEO_USAGE'.
There are 0 rows in 0 pages for object 'INV_THEO_USAGE'.
DBCC results for 'LABOR_CONFIG'.
There are 11 rows in 1 pages for object 'LABOR_CONFIG'.
DBCC results for 'LABOR_DEPARTMENT'.
There are 0 rows in 0 pages for object 'LABOR_DEPARTMENT'.
DBCC results for 'VENDOR_XMl'.
There are 0 rows in 0 pages for object 'VENDOR_XMl'.
DBCC results for 'INV_WASTE_USAGE'.
There are 0 rows in 0 pages for object 'INV_WASTE_USAGE'.
DBCC results for 'LABOR_PERIOD'.
There are 0 rows in 0 pages for object 'LABOR_PERIOD'.
DBCC results for 'LABOR_REFERENCES'.
There are 5 rows in 1 pages for object 'LABOR_REFERENCES'.
DBCC results for 'INV_BUCKET_USAGE'.
There are 0 rows in 0 pages for object 'INV_BUCKET_USAGE'.
DBCC results for 'MARITAL_STATUS'.
There are 4 rows in 1 pages for object 'MARITAL_STATUS'.
DBCC results for 'OVERTIME_LAW'.
There are 17 rows in 1 pages for object 'OVERTIME_LAW'.
DBCC results for 'RANGE_ALERT'.
There are 0 rows in 0 pages for object 'RANGE_ALERT'.
DBCC results for 'PUNCH_EDIT_HISTORY'.
There are 0 rows in 0 pages for object 'PUNCH_EDIT_HISTORY'.
DBCC results for 'TMP_ONHAND'.
There are 0 rows in 0 pages for object 'TMP_ONHAND'.
DBCC results for 'PUNCH_EDIT_REASON'.
There are 0 rows in 0 pages for object 'PUNCH_EDIT_REASON'.
DBCC results for 'INV_DOCS'.
There are 0 rows in 0 pages for object 'INV_DOCS'.
DBCC results for 'SCHOOL'.
There are 0 rows in 0 pages for object 'SCHOOL'.
DBCC results for 'SCHOOL_TIMING'.
There are 0 rows in 0 pages for object 'SCHOOL_TIMING'.
DBCC results for 'COST_HISTORY'.
There are 0 rows in 0 pages for object 'COST_HISTORY'.
DBCC results for 'STATE'.
There are 1 rows in 1 pages for object 'STATE'.
DBCC results for 'W4_EXCEPTIONS'.
There are 4 rows in 1 pages for object 'W4_EXCEPTIONS'.
DBCC results for 'KEY_IDENTIFIER'.
There are 1 rows in 1 pages for object 'KEY_IDENTIFIER'.
DBCC results for 'TMP_WASTE'.
There are 0 rows in 0 pages for object 'TMP_WASTE'.
DBCC results for 'WAGE'.
There are 0 rows in 0 pages for object 'WAGE'.
DBCC results for 'WAGE_TYPE'.
There are 3 rows in 1 pages for object 'WAGE_TYPE'.
DBCC results for 'TMP_THEOUSAGE'.
There are 0 rows in 0 pages for object 'TMP_THEOUSAGE'.
DBCC results for 'WAITING_CALL'.
There are 0 rows in 0 pages for object 'WAITING_CALL'.
DBCC results for 'WEEKLY_OVERTIME'.
There are 3 rows in 1 pages for object 'WEEKLY_OVERTIME'.
DBCC results for 'TMP_EMP_TIPS'.
There are 0 rows in 0 pages for object 'TMP_EMP_TIPS'.
DBCC results for 'TMPGoodsReceived'.
There are 0 rows in 0 pages for object 'TMPGoodsReceived'.
DBCC results for 'TMP_OrderReceiptException'.
There are 0 rows in 0 pages for object 'TMP_OrderReceiptException'.
DBCC results for 'TMP_TheoCalc'.
There are 0 rows in 0 pages for object 'TMP_TheoCalc'.
DBCC results for 'RM_LOC_XML'.
There are 0 rows in 0 pages for object 'RM_LOC_XML'.
DBCC results for 'TMP_PurchaseOrderPoll'.
There are 0 rows in 0 pages for object 'TMP_PurchaseOrderPoll'.
DBCC results for 'TMP_ReceiptPoll'.
There are 0 rows in 0 pages for object 'TMP_ReceiptPoll'.
DBCC results for 'TMP_RetPoll'.
There are 0 rows in 0 pages for object 'TMP_RetPoll'.
DBCC results for 'TMP_STOCKDEMAND'.
There are 0 rows in 0 pages for object 'TMP_STOCKDEMAND'.
DBCC results for 'TMP_RECON'.
There are 0 rows in 0 pages for object 'TMP_RECON'.
DBCC results for 'TMP_DAILYITMVAR'.
There are 0 rows in 0 pages for object 'TMP_DAILYITMVAR'.
DBCC results for 'ALERT_INFO'.
There are 0 rows in 0 pages for object 'ALERT_INFO'.
DBCC results for 'WASTE_ITEMS'.
There are 0 rows in 0 pages for object 'WASTE_ITEMS'.
DBCC results for 'Tmp_RmCountSheet'.
There are 0 rows in 0 pages for object 'Tmp_RmCountSheet'.
DBCC results for 'ALERT_SUBSCRIBER'.
There are 0 rows in 0 pages for object 'ALERT_SUBSCRIBER'.
DBCC results for 'PREATTACH_LIST'.
There are 0 rows in 0 pages for object 'PREATTACH_LIST'.
DBCC results for 'BREAK_POINTS'.
There are 0 rows in 0 pages for object 'BREAK_POINTS'.
DBCC results for 'ALERT_TYPE'.
There are 0 rows in 0 pages for object 'ALERT_TYPE'.
DBCC results for 'CATEGORY'.
There are 0 rows in 0 pages for object 'CATEGORY'.
DBCC results for 'BREAK_TABLE'.
There are 0 rows in 0 pages for object 'BREAK_TABLE'.
DBCC results for 'BREAK_TABLE_RULES'.
There are 0 rows in 0 pages for object 'BREAK_TABLE_RULES'.
DBCC results for 'AMWS_BUTTON'.
There are 160 rows in 2 pages for object 'AMWS_BUTTON'.
DBCC results for 'CATEGORY_ITEMS'.
There are 0 rows in 0 pages for object 'CATEGORY_ITEMS'.
DBCC results for 'CONDIMENTS'.
There are 0 rows in 0 pages for object 'CONDIMENTS'.
DBCC results for 'PREATTACHED_LIST_DETAILS'.
There are 0 rows in 0 pages for object 'PREATTACHED_LIST_DETAILS'.
DBCC results for 'AMWS_CONFIGURATION'.
There are 1 rows in 1 pages for object 'AMWS_CONFIGURATION'.
DBCC results for 'CATEGORY_XML'.
There are 0 rows in 0 pages for object 'CATEGORY_XML'.
DBCC results for 'AMWS_Session'.
There are 83 rows in 1 pages for object 'AMWS_Session'.
DBCC results for 'AMWS_USER'.
There are 2 rows in 1 pages for object 'AMWS_USER'.
DBCC results for 'CATEGORY_ITEMS_XML'.
There are 0 rows in 0 pages for object 'CATEGORY_ITEMS_XML'.
DBCC results for 'AMWS_TRANS'.
There are 368 rows in 5 pages for object 'AMWS_TRANS'.
DBCC results for 'INV_EXPLODE_SUPPORT'.
There are 6 rows in 1 pages for object 'INV_EXPLODE_SUPPORT'.
DBCC results for 'TMP_DAILYSHIFT'.
There are 0 rows in 0 pages for object 'TMP_DAILYSHIFT'.
DBCC results for 'AMWS_TAB'.
There are 15 rows in 1 pages for object 'AMWS_TAB'.
DBCC results for 'TMP_EMPONCLOCK'.
There are 0 rows in 0 pages for object 'TMP_EMPONCLOCK'.
DBCC results for 'CATEGORY_TRANSACTIONS'.
There are 0 rows in 0 pages for object 'CATEGORY_TRANSACTIONS'.
DBCC results for 'TMP_EMPSUMMARY'.
There are 0 rows in 0 pages for object 'TMP_EMPSUMMARY'.
DBCC results for 'CALENDAR_METHOD'.
There are 16 rows in 1 pages for object 'CALENDAR_METHOD'.
DBCC results for 'TIME_SLOT'.
There are 96 rows in 1 pages for object 'TIME_SLOT'.
DBCC results for 'TMP_JOBCLASSSUMMARY'.
There are 0 rows in 0 pages for object 'TMP_JOBCLASSSUMMARY'.
DBCC results for 'TMP_JOBCLASSSUMMARYSUB'.
There are 0 rows in 0 pages for object 'TMP_JOBCLASSSUMMARYSUB'.
DBCC results for 'CLOSED_DAY'.
There are 0 rows in 0 pages for object 'CLOSED_DAY'.
DBCC results for 'BREAK_POINTS_XML'.
There are 0 rows in 0 pages for object 'BREAK_POINTS_XML'.
DBCC results for 'TMP_LABORHRS'.
There are 0 rows in 0 pages for object 'TMP_LABORHRS'.
DBCC results for 'RECON_SUSPEND_HIST'.
There are 0 rows in 0 pages for object 'RECON_SUSPEND_HIST'.
DBCC results for 'TMP_WKTIMECARD'.
There are 0 rows in 0 pages for object 'TMP_WKTIMECARD'.
DBCC results for 'CTILock_Detail'.
There are 0 rows in 1 pages for object 'CTILock_Detail'.
DBCC results for 'EMPLOYEE_TIME_OFF'.
There are 0 rows in 0 pages for object 'EMPLOYEE_TIME_OFF'.
DBCC results for 'RM_THEO_INFO'.
There are 0 rows in 0 pages for object 'RM_THEO_INFO'.
DBCC results for 'EMPLOYEE_SCHEDULE'.
There are 0 rows in 0 pages for object 'EMPLOYEE_SCHEDULE'.
DBCC results for 'CTILocks'.
There are 0 rows in 1 pages for object 'CTILocks'.
DBCC results for 'RECEIVE_TEMPLATE'.
There are 0 rows in 0 pages for object 'RECEIVE_TEMPLATE'.
DBCC results for 'BREAK_TABLE_RULES_XML'.
There are 0 rows in 0 pages for object 'BREAK_TABLE_RULES_XML'.
DBCC results for 'Purchase_order_report'.
There are 0 rows in 0 pages for object 'Purchase_order_report'.
DBCC results for 'BUDGET_EDITOR'.
There are 0 rows in 0 pages for object 'BUDGET_EDITOR'.
DBCC results for 'Purchase_order_report_details'.
There are 0 rows in 0 pages for object 'Purchase_order_report_details'.
DBCC results for 'Employee_Schedule_Summary'.
There are 0 rows in 0 pages for object 'Employee_Schedule_Summary'.
DBCC results for 'CURRENT_DAY'.
There are 1 rows in 1 pages for object 'CURRENT_DAY'.
DBCC results for 'Receive_Template_Detail'.
There are 0 rows in 0 pages for object 'Receive_Template_Detail'.
DBCC results for 'CURRENT_SITE_INFO'.
There are 1 rows in 1 pages for object 'CURRENT_SITE_INFO'.
DBCC results for 'DAY_PLANNER'.
There are 2 rows in 1 pages for object 'DAY_PLANNER'.
DBCC results for 'BREAK_TABLE_XML'.
There are 0 rows in 0 pages for object 'BREAK_TABLE_XML'.
DBCC results for 'TMP_COG'.
There are 0 rows in 0 pages for object 'TMP_COG'.
DBCC results for 'Tmp_SvrSales'.
There are 0 rows in 0 pages for object 'Tmp_SvrSales'.
DBCC results for 'DELIVERY_SCHEDULE'.
There are 0 rows in 0 pages for object 'DELIVERY_SCHEDULE'.
DBCC results for 'Emp_Schedule_option'.
There are 2 rows in 1 pages for object 'Emp_Schedule_option'.
DBCC results for 'IDVALUES'.
There are 89 rows in 1 pages for object 'IDVALUES'.
DBCC results for 'JOB_CONFIG'.
There are 0 rows in 0 pages for object 'JOB_CONFIG'.
DBCC results for 'CONDIMENTS_XML'.
There are 0 rows in 0 pages for object 'CONDIMENTS_XML'.
DBCC results for 'INV_CLASS'.
There are 0 rows in 0 pages for object 'INV_CLASS'.
DBCC results for 'MACRO'.
There are 2 rows in 1 pages for object 'MACRO'.
DBCC results for 'SHIFT'.
There are 0 rows in 0 pages for object 'SHIFT'.
DBCC results for 'INV_DEPT'.
There are 0 rows in 0 pages for object 'INV_DEPT'.
DBCC results for 'MACRO_TASK'.
There are 2 rows in 1 pages for object 'MACRO_TASK'.
DBCC results for 'EMPLOYEE_PREFS'.
There are 0 rows in 0 pages for object 'EMPLOYEE_PREFS'.
DBCC results for 'CLASS'.
There are 1045 rows in 9 pages for object 'CLASS'.
DBCC results for 'DELIVERY_SCHEDULE_XML'.
There are 0 rows in 0 pages for object 'DELIVERY_SCHEDULE_XML'.
DBCC results for 'INV_UNIT'.
There are 0 rows in 0 pages for object 'INV_UNIT'.
DBCC results for 'NAV_TEMPLATES'.
There are 1 rows in 1 pages for object 'NAV_TEMPLATES'.
DBCC results for 'DAYPART'.
There are 80 rows in 1 pages for object 'DAYPART'.
DBCC results for 'EXCLUDEDEPARTMENTS'.
There are 5 rows in 1 pages for object 'EXCLUDEDEPARTMENTS'.
DBCC results for 'DEPARTMENT'.
There are 880 rows in 8 pages for object 'DEPARTMENT'.
DBCC results for 'LOCATION'.
There are 0 rows in 0 pages for object 'LOCATION'.
DBCC results for 'DEPARTMENT_SALES'.
There are 14859 rows in 171 pages for object 'DEPARTMENT_SALES'.
DBCC results for 'LABOR_MONITOR'.
There are 0 rows in 0 pages for object 'LABOR_MONITOR'.
DBCC results for 'ROLE'.
There are 17 rows in 1 pages for object 'ROLE'.
DBCC results for 'DEPOSIT'.
There are 0 rows in 0 pages for object 'DEPOSIT'.
DBCC results for 'GLCATEGORY_XML'.
There are 0 rows in 0 pages for object 'GLCATEGORY_XML'.
DBCC results for 'MENU_ITEM'.
There are 0 rows in 0 pages for object 'MENU_ITEM'.
DBCC results for 'ROLE_MACRO'.
There are 4 rows in 1 pages for object 'ROLE_MACRO'.
DBCC results for 'DRAWER_PULL'.
There are 445 rows in 4 pages for object 'DRAWER_PULL'.
DBCC results for 'MENU_ITEM_INGREDIENT'.
Server: Msg 8926, Level 16, State 3, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:2915), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3438) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:2913), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3436) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3122), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3437) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:2912), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3433) but are not in the same object.
There are 0 rows in 0 pages for object 'MENU_ITEM_INGREDIENT'.
DBCC results for 'DRIVE_THRU'.
There are 0 rows in 0 pages for object 'DRIVE_THRU'.
DBCC results for 'ROLE_TASK'.
There are 478 rows in 2 pages for object 'ROLE_TASK'.
DBCC results for 'EMP_SALES_DETAIL'.
There are 17488 rows in 219 pages for object 'EMP_SALES_DETAIL'.
DBCC results for 'GLSUBCATEGORY_XML'.
There are 0 rows in 0 pages for object 'GLSUBCATEGORY_XML'.
DBCC results for 'RAW_MATERIAL'.
There are 0 rows in 0 pages for object 'RAW_MATERIAL'.
DBCC results for 'EMP_SALES_MAIN'.
There are 515 rows in 3 pages for object 'EMP_SALES_MAIN'.
DBCC results for 'ROLE_USER'.
There are 2 rows in 1 pages for object 'ROLE_USER'.
DBCC results for 'EMP_SHIFT_DETAIL'.
Server: Msg 8926, Level 16, State 3, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3271), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3432) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3487), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3435) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3052), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3434) but are not in the same object.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree chain linkage mismatch. (1:3271)->next = (1:3432), but (1:3432)->Prev = (1:2784).
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree page (1:3432) has two parent nodes (0:1), slot 0 and (1:179), slot 1.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree chain linkage mismatch. (1:2912)->next = (1:3433), but (1:3433)->Prev = (1:3460).
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree page (1:3433) has two parent nodes (0:1), slot 0 and (1:3432), slot 1.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree chain linkage mismatch. (1:3052)->next = (1:3434), bu
View 13 Replies
View Related
