2008R2 Database Corruption Repair

A foreign trade chain used by the SQL 2008R2 database, the normal use of the sudden server power loss caused by the damage, the additional discovery database error can not be normal operation, the client side of the operation and maintenance of their own attempt to repair and rebuild the log but the fault is still, and later found that they can not solve the contact us to deal with.

Database size 800M, the underlying data looked at the normal, first with the tool to detect the page damage,

650) this.width=650; "title=" jc.jpg "src=" http://s3.51cto.com/wyfs02/M00/6D/E5/wKiom1VuhT_D96t2AAF4r37wJfQ956.jpg "Width=" 651 "height=" 232 "alt=" Wkiom1vuht_d96t2aaf4r37wjfq956.jpg "/>

You can see that there is really a page corruption, the new library is replaced by the rebuild log in the view of corruption, (2008r2 reconstruction method can be self-searching online)

The log rebuild succeeded after the substitution, but DBCC detection found an error system table pre-check: Object ID 3. The latch type SH cannot be used to read and latch the page (1:37,297). The CHECK statement was terminated due to an uncorrectable error.

650) this.width=650; "style=" width:654px;height:250px; "title=" 2008r2.jpg "src=" http://s3.51cto.com/wyfs02/M01/6D/ E1/wkiol1vuhzigs3l7aaqacw4jvck253.jpg "width=" 915 "height=" 434 "alt=" wkiol1vuhzigs3l7aaqacw4jvck253.jpg "/>

A lot of errors, in SQL2000 under the repair easier, but 2008r2 many repair statements are not universal. This failure is typically caused by System page corruption, and the corrupted table ID is 3. The system table in which the ID3 is located is queried by the statement. Repairing the damaged system tables may rebuild the log again, and DBCC detects that the database is normal and that the data in the table is normally accessible.

650) this.width=650; "style=" width:659px;height:323px; "title=" 2008shuju.jpg "src=" http://s3.51cto.com/wyfs02/M02/ 6d/e1/wkiol1vuh5hw23q0aap2jr4p3cs259.jpg "width=" 513 "height=" 370 "alt=" Wkiol1vuh5hw23q0aap2jr4p3cs259.jpg "/>

Now the high version of the database has the automatic page repair function, so the probability of damage decreased a lot, but there are still a lot of unexpected situation, this is 3 days to repair the 5th 2008 database, all complete repair can be normal use!

currently can be fully efficient repair MSSQL 6.5 7.0 2005 2008R2 , suspect, suspicious, resume hangs, suspicious, system table damage! Index break, page tear, communication interruption, consistency error, database restore restore times consistency error, error 823 and other cases of data recovery, various error prompt database file repair and some tables do not open bug fix!

qq:540773559

Jia Yu Data Recovery center:www.uuhf.net Research and Development products station: www.sysfix.cn

This article from "Sqlrecovery" blog, declined reprint!

2008R2 Database Corruption Repair