Symptom:
When using DBCC CHECKDB with REPAIR_ALLOW_DATA_LOSS parameter to repair a corrupt .MDF database, like this:
DBCC CHECKDB(xxxx, ‘REPAIR_ALLOW_DATA_LOSS’)
you see the following error message:
Msg 2510, Level 16, State 17, Line 8
DBCC checkdb error: This system table index cannot be recreated.
Repair: The Nonclustered index successfully rebuilt for the object “sysidxstats” in database “Error1”.
DBCC results for ‘Error1’.
DBCC results for ‘sys.sysrscols’.
There are 1092 rows in 14 pages for object “sys.sysrscols”.
DBCC results for ‘sys.sysrowsets’.
There are 148 rows in 3 pages for object “sys.sysrowsets”.
DBCC results for ‘sys.sysclones’.
There are 0 rows in 0 pages for object “sys.sysclones”.
DBCC results for ‘sys.sysallocunits’.
There are 172 rows in 2 pages for object “sys.sysallocunits”.
DBCC results for ‘sys.sysfiles1’.
There are 2 rows in 1 pages for object “sys.sysfiles1”.
DBCC results for ‘sys.sysseobjvalues’.
There are 0 rows in 0 pages for object “sys.sysseobjvalues”.
DBCC results for ‘sys.syspriorities’.
There are 0 rows in 0 pages for object “sys.syspriorities”.
DBCC results for ‘sys.sysdbfrag’.
There are 0 rows in 0 pages for object “sys.sysdbfrag”.
DBCC results for ‘sys.sysfgfrag’.
There are 0 rows in 0 pages for object “sys.sysfgfrag”.
DBCC results for ‘sys.sysdbfiles’.
There are 2 rows in 1 pages for object “sys.sysdbfiles”.
DBCC results for ‘sys.syspru’.
There are 0 rows in 0 pages for object “sys.syspru”.
DBCC results for ‘sys.sysbrickfiles’.
There are 0 rows in 0 pages for object “sys.sysbrickfiles”.
DBCC results for ‘sys.sysphfg’.
There are 1 rows in 1 pages for object “sys.sysphfg”.
DBCC results for ‘sys.sysprufiles’.
There are 2 rows in 1 pages for object “sys.sysprufiles”.
DBCC results for ‘sys.sysftinds’.
There are 0 rows in 0 pages for object “sys.sysftinds”.
DBCC results for ‘sys.sysowners’.
There are 14 rows in 1 pages for object “sys.sysowners”.
DBCC results for ‘sys.sysdbreg’.
There are 0 rows in 0 pages for object “sys.sysdbreg”.
DBCC results for ‘sys.sysprivs’.
There are 140 rows in 1 pages for object “sys.sysprivs”.
DBCC results for ‘sys.sysschobjs’.
There are 2262 rows in 29 pages for object “sys.sysschobjs”.
DBCC results for ‘sys.syscsrowgroups’.
There are 0 rows in 0 pages for object “sys.syscsrowgroups”.
DBCC results for ‘sys.sysexttables’.
There are 0 rows in 0 pages for object “sys.sysexttables”.
DBCC results for ‘sys.syscolpars’.
There are 888 rows in 16 pages for object “sys.syscolpars”.
DBCC results for ‘sys.sysxlgns’.
There are 0 rows in 0 pages for object “sys.sysxlgns”.
DBCC results for ‘sys.sysxsrvs’.
There are 0 rows in 0 pages for object “sys.sysxsrvs”.
DBCC results for ‘sys.sysnsobjs’.
There are 1 rows in 1 pages for object “sys.sysnsobjs”.
DBCC results for ‘sys.sysusermsgs’.
There are 0 rows in 0 pages for object “sys.sysusermsgs”.
DBCC results for ‘sys.syscerts’.
There are 0 rows in 0 pages for object “sys.syscerts”.
DBCC results for ‘sys.sysrmtlgns’.
There are 0 rows in 0 pages for object “sys.sysrmtlgns”.
DBCC results for ‘sys.syslnklgns’.
There are 0 rows in 0 pages for object “sys.syslnklgns”.
DBCC results for ‘sys.sysxprops’.
There are 0 rows in 0 pages for object “sys.sysxprops”.
DBCC results for ‘sys.sysscalartypes’.
There are 34 rows in 1 pages for object “sys.sysscalartypes”.
DBCC results for ‘sys.systypedsubobjs’.
There are 0 rows in 0 pages for object “sys.systypedsubobjs”.
DBCC results for ‘sys.sysidxstats’.
Repair: The Clustered index successfully rebuilt for the object “sys.sysidxstats” in database “Error1”.
Repair: The page (1:40) has been deallocated from object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data).
Repair: The Nonclustered index successfully rebuilt for the object “sys.sysidxstats, nc” in database “Error1”.
Msg 8945, Level 16, State 1, Line 8
Table error: Object ID 54, index ID 1 will be rebuilt.
The error has been repaired.
Msg 8928, Level 16, State 1, Line 8
Object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data): Page (1:40) could not be processed. See other errors for details.
The error has been repaired.
Msg 8939, Level 16, State 98, Line 8
Table error: Object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data), page (1:40). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 2057 and -4.
The error has been repaired.
Msg 8976, Level 16, State 1, Line 8
Table error: Object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data). Page (1:40) was not seen in the scan although its parent (1:163) and previous (1:34) refer to it. Check any previous errors.
The error has been repaired.
Msg 8978, Level 16, State 1, Line 8
Table error: Object ID 54, index ID 1, partition ID 281474980249600, alloc unit ID 281474980249600 (type In-row data). Page (1:164) is missing a reference from previous page (1:40). Possible chain linkage problem.
The error has been repaired.
Msg 8945, Level 16, State 1, Line 8
Table error: Object ID 54, index ID 2 will be rebuilt.
The error has been repaired.
There are 130 rows in 4 pages for object “sys.sysidxstats”.
CHECKDB found 0 allocation errors and 4 consistency errors in table ‘sys.sysidxstats’ (object ID 54).
CHECKDB fixed 0 allocation errors and 4 consistency errors in table ‘sys.sysidxstats’ (object ID 54).
DBCC results for ‘sys.sysiscols’.
There are 399 rows in 2 pages for object “sys.sysiscols”.
DBCC results for ‘sys.sysendpts’.
There are 0 rows in 0 pages for object “sys.sysendpts”.
DBCC results for ‘sys.syswebmethods’.
There are 0 rows in 0 pages for object “sys.syswebmethods”.
DBCC results for ‘sys.sysbinobjs’.
There are 23 rows in 1 pages for object “sys.sysbinobjs”.
DBCC results for ‘sys.sysaudacts’.
There are 0 rows in 0 pages for object “sys.sysaudacts”.
DBCC results for ‘sys.queue_messages_2009058193’.
There are 0 rows in 0 pages for object “sys.queue_messages_2009058193”.
DBCC results for ‘sys.queue_messages_2041058307’.
There are 0 rows in 0 pages for object “sys.queue_messages_2041058307”.
DBCC results for ‘sys.filestream_tombstone_2073058421’.
There are 0 rows in 0 pages for object “sys.filestream_tombstone_2073058421”.
DBCC results for ‘sys.syscommittab’.
There are 0 rows in 0 pages for object “sys.syscommittab”.
DBCC results for ‘sys.filetable_updates_2105058535’.
There are 0 rows in 0 pages for object “sys.filetable_updates_2105058535”.
DBCC results for ‘sys.plan_persist_query_text’.
There are 0 rows in 0 pages for object “sys.plan_persist_query_text”.
DBCC results for ‘sys.plan_persist_query’.
There are 0 rows in 0 pages for object “sys.plan_persist_query”.
CHECKDB found 0 allocation errors and 4 consistency errors in database ‘Error1’.
CHECKDB fixed 0 allocation errors and 4 consistency errors in database ‘Error1’.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Msg 824, Level 24, State 2, Line 8
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x4bbecdad; actual: 0x0bbfc5ad). It occurred during a read of page (1:40) in database ID 39 at offset 0x00000000050000 in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.SQL2014MSSQLDATAError1.mdf’. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
where ‘Error1’ is name of the corrupt MDF database being repaired.
Msg 2510 indicates the specific system table index cannot be recreated, which is also a consistency error.
Screenshot of error message:
Precise Explanation:
In a SQL Server MDF database, there are many system tables used to store the structure and meta data of the database.
When CHECKDB finds there are inconsistencies in the index of one of the system tables, it will report the error message Msg 2510 and try to fix the errors. If it cannot fix the error, then the recovery fails and will lead to more errors, such as Msg 824.
You can use our product DataNumen SQL Recovery to recover the data from the corrupt MDF file and solve this error.
Sample Files:
Sample corrupt MDF files that will cause the Msg 2510 error:
| SQL Server version | Corrupt MDF file | MDF file fixed by DataNumen SQL Recovery |
| SQL Server 2014 | Error6.mdf | Error6_fixed.mdf |