UF Kingdee SQL database error format recovery SQL database repair SQL Database recovery Tool method

"Customer Name": Guizhou Tongren driving Person Training Center

"Software name": UF T3 Universal Edition

"Database Version": MS SQL Server 2000 "database size": 1GB X 6 (3 accounts for a total of 6 years).

"Problem description": Due to server poisoning or Kaka, the customer sent the server computer to the installed shop to redo the operating system. Not detailed to inform the use of the computer, resulting in the entire hard drive by the repair shop technician full format repartitioning, and re-completed the new operating system, resulting in all the annual data sets UF T3 all lost, all backup lost, need emergency recovery.

"Problem analysis": After receiving the phone, the customer sent an accident hard disk, immediately organize the hard disk analysis work, check the error operation after the disk usage! C-Drive has an operating system installed. Occupy 10GB space, other disks are not used, the preliminary judgement of the value of recovery is very high! Through the self-developed MDF file fragment synthesis tool to extract, successfully scanned to disk deleted files UF database MDF.

After getting the source file, initial use of SQL DBCC checkdb detection, found that there is a small portion of the file coverage.

Check server: Msg 8966, Level 16, State 1, line 1

Failed to read and latch page (1:49) (with latch type SH). Sysindexes failed.

Detailed follow-up to the specific table, showing sysobjects sysindexes system table each has 10 rows of consecutive records can not be read.

After detailed comparison analysis, successfully backfill sysobjects sysindexes 10 line bad point, rebuild the system table.

Again DBCC checkdb detection, successful repair completed!

"Recovery results": send back to customer acceptance, feedback data integrity, 100% full recovery to the point of damage, customer satisfaction! Get the customer's great praise.

"Warm hint": Server redo operating system, need to carefully backup, inform technician in advance details. Important data, try to save as many backup points as possible!

"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.

UF Kingdee SQL database error format recovery SQL database repair SQL Database recovery Tool method