SQL Server R2 Database Corruption Repair success stories
2016.4 months Qingdao A chain store uses SQL 2008R2 database, the customer in the normal use suddenly the server power outage causes the damage, the additional Discovery database error is unable to run normally, the customer over there the administrator has tried the repair and the reconstruction log but the fault still, later found himself unable to solve, Through Baidu Search, contact us for processing.
Our engineers have a detailed view of the database size of about 800M, the underlying data looked at the basic normal, first with the tool to detect the page damage, such as
We can see that there is really a page corruption, the new library is replaced by the Rebuild log in view of the corruption as
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:75,678).
The CHECK statement was terminated due to an uncorrectable error.
This error is very common, it is easier to repair under SQL2000, 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. Repair the damaged system tables may be rebuilt, re-rebuild the log, DBCC detection after the discovery of the database is normal, and the data in the table can be accessed normally!
Important reminder: can be fully and efficiently repaired at present MSSQL 6.5 7.0 2005 2008R2 2012 according to the library suspect, suspicious, resume hangs,
Suspicious, system table is corrupted! Index break, page tear, communication interrupt, 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 can't open bug fix!
SQL Server R2 Database corruption repair success Story