His hospital information System master server RAID5 crash hard disk corruption SQL database corruption repair SQL Server database repair backup file Unable to restore data recovery

"Customer Name": Binzhou Wudi County Hospital of Shandong Province

"Software name": Zhong Lian Jia Yu His hospital information management system

"Database Version": MS SQL Server 2008R2 "database size": 48GB.

"Problem description": On the eve of the Lunar New Year, the customer due to server hard disk damage, causing RAID5 serious damage. It also affects all hot backup disks, all of which are covered by damaged files damaged by the main disk. Lead to the central United Jia Yu His Hospital information management System 4 databases (Cailiao,oa,hos) varying degrees of impaired DBCC CHECKDB can not be executed, failed to pass, the system table seriously damaged. Hospital information data, very important, need to be repaired immediately! Customer call, contact us, explain the basic situation! To corrupt the database file.

"Problem analysis": Preliminary telephone communication with the hospital system administrator, preliminary understanding of the general situation! I immediately expand the corrupt file analysis tool to co-ordinate the solution.

Server: Msg 7995, Level 16, State 1, line 1
Database ' Hos ' has a consistency error in sysobjects, sysindexes, syscolumns, or systypes, which hinders further CHECKDB processing.
DBCC execution is complete. If DBCC outputs an error message, contact your system administrator.

DBCC detects a corrupted sysindexes,sysobjects,sysclocms system table that belongs to a serious damage! caused by a power outage, power failure, or forcibly shutting down the host, accidentally unplugging the plug, etc., resulting in a high-speed disk file system damage. When you restart your computer, WINDOWS boot up with the feature Chkdisk detect the Repair feature. The disk index and arrowheads information for the damaged sector are erased. Erase the damaged fan block data, backfill the empty value! Repaired the disk. The result.

The Fix method can only use template source file comparison to backfill damaged chunks.

"Recovery results": After 6 hours of continuous analysis backfill, successfully backfill damaged block code, database file successfully attached to the line, DBCC CHECKDB detection success through error-free! Send back to the customer test acceptance, feedback data 100% complete, accurate and correct, fast recovery speed, high efficiency, save a lot of hospital losses, customer satisfaction! Get the customer's great praise.

"Warm tip": This case tells us that the RAID server is not 100% reliable, but still a certain program to reduce the chance of damage. Do not power off the server host, press the restart key to forcibly restart. The circuit is unstable be sure to use the UPS power supply.

"Data Engineer" Yun Jun telephone//qq:18302650920 Welcome to come to inquire to discuss data recovery.

1, the system crashes only the SQL Server data files in the case of recovery. That is, no log files or log file corruption in the case of recovery

2, the SQL Server data file has a bad page in the case of recovery.

3, in SQL Server2000, SqlServer2005, SQL2008 run in simple log mode, full log mode or bulk logging mode data is mistakenly (drop, delete, truncate) Delete table recovery, Data recovery after updata, etc.

4. SQL serve files cannot be appended with data recovery.

5. SQL Server database is marked as suspect, unavailable, etc.

6, Sql Server2000, SqlServer2005, SQL2008 database sysobjects and other system table corruption can not be applied in the case of recovery.

7. The SQL Server database recovers only if the data files do not have any logs .

8. The recovery of SQL Server data files is deleted by mistake.

9, SQL Server2000, SQL Server2005, SQL2008 database master database is corrupted and cannot be resumed under normal operation condition.

10, SQL Server restore times consistency error, error 823 and other cases of data recovery, various error prompt database file repair

11. Recoverable database damage caused by bad drive

12. Can repair the database after the log shrinkage or sudden power outage

13. Can recover multiple relational databases

14. Recoverable SQL database bkf backup file and bak file

15. Database recovery in case of mis-formatting of SQL Server database on disk array

16, SQL Server database can be formatted, mistakenly deleted, all market recovery software can not restore the situation of recovery, that is, the fragment-level database extraction recovery.

17, recoverable shade ransomware virus file poisoning is encrypted, database file anti-blackmail service.

His hospital information System master server RAID5 crash hard disk corruption SQL database corruption repair SQL Server database repair backup file cannot restore data recovery