cyclic redundancy check error

I have revived a database by replacing the log file, detaching and
reattaching.

Now I get the following error when running a query against the
suspected culprit table:

Server: Msg 823, Level 24, State 2, Procedure  LocationCountbyCount
ry,
Line 3
I/O error 23(Data error (cyclic redundancy check).) detected during
read at offset 0x00000181ab0000 in file 'C:\Program Files\Microsoft SQL
 Server\MSSQL\Data\my
DatabaseName.mdf'.

Connection Broken

Is there anything I can do to fix this?

Try doing a DBCC CHECKTABLE on that table and see what it reports.  Post the
results here.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada  tom@cips.ca
www.pinpub.com

"laurenq uantrell" < laurenquantrell@hotm
ail.com> wrote in message
news:1135611827.501973.78400@g14g2000cwa.googlegroups.com...
I have revived a database by replacing the log file, detaching and
reattaching.

Now I get the following error when running a query against the
suspected culprit table:

Server: Msg 823, Level 24, State 2, Procedure  LocationCountbyCount
ry,
Line 3
I/O error 23(Data error (cyclic redundancy check).) detected during
read at offset 0x00000181ab0000 in file 'C:\Program Files\Microsoft SQL
 Server\MSSQL\Data\my
DatabaseName.mdf'.

Connection Broken

Is there anything I can do to fix this?

Whew! 45 minutes running DBCC CHECKTABLE produced these results:

Server: Msg 8966, Level 16, State 2, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789856) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789857) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789858) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789859) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789860) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789861) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789862) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789863) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789856) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789857) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789858) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
CHECKTABLE found 0 allocation errors and 8 consistency errors not
associated with any single object.
DBCC results for 'myTableName'.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789859) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789860) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789861) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789862) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789863) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 8976, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789856) was not
seen in the scan although its parent (1:789623) and previous (1:789855)
refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 234 refers to child page (1:789857) and previous child
(1:789856), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 235 refers to child page (1:789858) and previous child
(1:789857), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 236 refers to child page (1:789859) and previous child
(1:789858), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 237 refers to child page (1:789860) and previous child
(1:789859), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 238 refers to child page (1:789861) and previous child
(1:789860), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 239 refers to child page (1:789862) and previous child
(1:789861), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 240 refers to child page (1:789863) and previous child
(1:789862), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789864) is
missing a reference from previous page (1:789863). Possible chain
linkage problem.
There are 5507914 rows in 186584 pages for object 'myTableName'.
CHECKTABLE found 0 allocation errors and 17 consistency errors in table
'myTableName' (object ID 1027899129).
 repair_allow_data_lo
ss is the minimum repair level for the errors found
by DBCC CHECKTABLE (MyDatabaseName.dbo.myTableName ).
Stored Procedure: MyDatabaseName.dbo.sprocTableCheck
Return Code = -6

The key bit is:

" repair_allow_data_lo
ss is the minimum repair level for the errors found"

If you run it with  repair_allow_data_lo
ss, it MAY fix your problem but it
will LIKELY cause you to lose data.


--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada  tom@cips.ca
www.pinpub.com

"laurenq uantrell" < laurenquantrell@hotm
ail.com> wrote in message
news:1135693208.073001.300030@z14g2000cwz.googlegroups.com...
Whew! 45 minutes running DBCC CHECKTABLE produced these results:

Server: Msg 8966, Level 16, State 2, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789856) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789857) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789858) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789859) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789860) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789861) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789862) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789863) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789856) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789857) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789858) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
CHECKTABLE found 0 allocation errors and 8 consistency errors not
associated with any single object.
DBCC results for 'myTableName'.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789859) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789860) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789861) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789862) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789863) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 8976, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789856) was not
seen in the scan although its parent (1:789623) and previous (1:789855)
refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 234 refers to child page (1:789857) and previous child
(1:789856), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 235 refers to child page (1:789858) and previous child
(1:789857), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 236 refers to child page (1:789859) and previous child
(1:789858), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 237 refers to child page (1:789860) and previous child
(1:789859), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 238 refers to child page (1:789861) and previous child
(1:789860), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 239 refers to child page (1:789862) and previous child
(1:789861), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 240 refers to child page (1:789863) and previous child
(1:789862), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789864) is
missing a reference from previous page (1:789863). Possible chain
linkage problem.
There are 5507914 rows in 186584 pages for object 'myTableName'.
CHECKTABLE found 0 allocation errors and 17 consistency errors in table
'myTableName' (object ID 1027899129).
 repair_allow_data_lo
ss is the minimum repair level for the errors found
by DBCC CHECKTABLE (MyDatabaseName.dbo.myTableName ).
Stored Procedure: MyDatabaseName.dbo.sprocTableCheck
Return Code = -6

After running DBCC CHECKTABLE I get these results:

Server: Msg 8966, Level 16, State 2, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789856) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789857) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789858) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789859) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789860) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789861) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789862) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789863) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789856) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789857) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789858) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
CHECKTABLE found 0 allocation errors and 8 consistency errors not
associated with any single object.
DBCC results for 'myTableName'.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789859) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789860) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789861) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789862) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789863) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 8976, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789856) was not
seen in the scan although its parent (1:789623) and previous (1:789855)
refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 234 refers to child page (1:789857) and previous child
(1:789856), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 235 refers to child page (1:789858) and previous child
(1:789857), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 236 refers to child page (1:789859) and previous child
(1:789858), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 237 refers to child page (1:789860) and previous child
(1:789859), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 238 refers to child page (1:789861) and previous child
(1:789860), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 239 refers to child page (1:789862) and previous child
(1:789861), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 240 refers to child page (1:789863) and previous child
(1:789862), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789864) is
missing a reference from previous page (1:789863). Possible chain
linkage problem.
There are 5507914 rows in 186584 pages for object 'myTableName'.
CHECKTABLE found 0 allocation errors and 17 consistency errors in table
'myTableName' (object ID 1027899129).
 repair_allow_data_lo
ss is the minimum repair level for the errors found
by DBCC CHECKTABLE (MyDatabaseName.dbo.myTableName ).
Stored Procedure: MyDatabaseName.dbo.sprocTableCheck
Return Code = -6

Is that with  repair_allow_data_lo
ss?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada  tom@cips.ca
www.pinpub.com

"laurenq uantrell" < laurenquantrell@hotm
ail.com> wrote in message
news:1135704934.219295.29650@g49g2000cwa.googlegroups.com...
After running DBCC CHECKTABLE I get these results:

Server: Msg 8966, Level 16, State 2, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789856) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789857) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789858) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789859) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789860) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789861) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789862) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 8966, Level 16, State 1, Procedure sprocTableCheck, Line 2
Could not read and latch page (1:789863) with latch type UP.
1(Incorrect function.) failed.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789856) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789857) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789858) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
CHECKTABLE found 0 allocation errors and 8 consistency errors not
associated with any single object.
DBCC results for 'myTableName'.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789859) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789860) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789861) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789862) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 2533, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Page (1:789863) allocated to object ID 1027899129, index
ID 0 was not seen.  Page may be invalid or have incorrect object ID
information in its header.
Server: Msg 8976, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789856) was not
seen in the scan although its parent (1:789623) and previous (1:789855)
refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 234 refers to child page (1:789857) and previous child
(1:789856), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 235 refers to child page (1:789858) and previous child
(1:789857), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 236 refers to child page (1:789859) and previous child
(1:789858), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 237 refers to child page (1:789860) and previous child
(1:789859), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 238 refers to child page (1:789861) and previous child
(1:789860), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 239 refers to child page (1:789862) and previous child
(1:789861), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Index node page
(1:789623), slot 240 refers to child page (1:789863) and previous child
(1:789862), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Procedure sprocTableCheck, Line 2
Table error: Object ID 1027899129, index ID 1. Page (1:789864) is
missing a reference from previous page (1:789863). Possible chain
linkage problem.
There are 5507914 rows in 186584 pages for object 'myTableName'.
CHECKTABLE found 0 allocation errors and 17 consistency errors in table
'myTableName' (object ID 1027899129).
 repair_allow_data_lo
ss is the minimum repair level for the errors found
by DBCC CHECKTABLE (MyDatabaseName.dbo.myTableName ).
Stored Procedure: MyDatabaseName.dbo.sprocTableCheck
Return Code = -6

Tom,
I have run DBCC CHECKTABLE with  repair_allow_data_lo
ss (it failed to
repair on the non-data-loss options) and it seems to have reconstructed
this very large table. Running row counts on various Group Bys it
appears that the number of rows are correct though I have no way of
knowing if column data has been currupted since this is a many millions
of rows table.

If you have an older copy of the DB, perhaps you can do a column-by-column
comparison.  At least that would verify the older stuff.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada
www.pinpub.com
.
"laurenq uantrell" < laurenquantrell@hotm
ail.com> wrote in message
news:1135881183.968306.281210@g44g2000cwa.googlegroups.com...
Tom,
I have run DBCC CHECKTABLE with  repair_allow_data_lo
ss (it failed to
repair on the non-data-loss options) and it seems to have reconstructed
this very large table. Running row counts on various Group Bys it
appears that the number of rows are correct though I have no way of
knowing if column data has been currupted since this is a many millions
of rows table.