SQL Server R2 database corruption repair succeeded

SQL Server R2 Database Corruption repair success stories

2016.4 months Qingdao A chain store uses the 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 that they can not solve, through the Baidu search, contact us to deal with.

Our engineers have a detailed view of the database size ofabout 6 00M , the underlying data looked at the basic normal, first use the tool to detect the page damage, such as:

650) this.width=650; "Src=" http://www.zhentiezi.com/data/attachment/portal/201604/12/153415jl233uvkljius1vi.jpg " Style= "Border:none;" alt= "153415jl233uvkljius1vi.jpg"/>

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:75678).

TheCHECK statement was terminated due to an uncorrectable error.

650) this.width=650; "Src=" Http://www.zhentiezi.com/data/attachment/portal/201604/12/153513vo1x09tehzjoocji.png " Style= "Border:none;" alt= "153513vo1x09tehzjoocji.png"/>

SQL2000 , but 2008R2 Many repair statements are not generic. This failure is generally caused by System page corruption, corrupted table id  3. , and the statement queries the system table where ID3 is located. Repairing a corrupted system table may rebuild, rebuild the log again, and DBCC detects that the database is healthy and that the data in the table can be accessed normally !

mssql 6.5 7.0 2000 2005 2008R2 2012 , , the system table is corrupted !

823 , !

SQL Server R2 database corruption repair succeeded