sql database repair tool

How to repair a corrupted SQL database?

1. Stop the SQLServer service, backup the two files of the failed database in the \data subdirectory

under the SQLServer installation directory, a data file hbposv6_branch_data.mdf,

a hbposv6_branch_log.ldf (it may not be so named), and check whether the disk

space has enough space;

2. Start the SQLServer service (if it has been stopped), and create a new database named

the name of the original database.

3. Stop SQLServer

4. Replace the MDF file (hbposv6_branch_data.mdf) of the old database with the corresponding MDF file of the new database

and delete the LDF file (hbposv6_branch_log.ldg).

5. Restart the SQLServer service and run the following command:








— Verifyonerowisupdatedbeforecommitting



6. Stop SQL and then restart the SQLServer service, then run the following command

(replace log file path address):






‘c:\ProgramFiles\ MicrosoftSQLServer\MSSQL\Data\hbposv6_branch_log.ldf’)

— Here, enter the path to your database


7. Stop SQL and then restart the SQLServer service and run:






< p>reconfigurewithoverride


8. Run dbcccheckdb(db_name) to check the integrity of the database

9. Repair the counting library

–Please execute the following statement in the query analyzer. Disconnect all other

all databases before execution, preferably disconnecting the network cable

–If it is not the name of this database, please change the database


–to the database to be repaired



— Single user mode

EXECsp_dboption ‘hbposv6_branch’,’singleuser’,’TRUE’


— Database check



–If the return result has red text, there is an error in the database that needs to be repaired

–Database Repair



–again database check, if the red prompt text is no longer present in the returned result,

that means the repair was successful;



–otherwise it means that a higher level of repair is still needed; try replacing the above repair statement’s

‘repair_rebuild’) with ‘repair_rebuild’,’repair_rebuild’),


–otherwise it means that a higher level of repair is needed; try replacing the above repair statement’s

‘ repair_rebuild’ for ‘repair_allow_data_loss’ and try again,

after which check the database again.

–If there are still bugs that have not been fixed, please send us that information in text

–Be sure to execute the following statement to return to multi-user mode before exiting

EXECsp_dboption ‘hbposv6_branch’,’singleuser’,’FALSE’


Note: Both replace dbname with the real database name.

How to Repair Corrupt MySQL Data Table

Tools/Materials: ManagementStudio.

1. First of all, on the desktop, click on the “ManagementStudio” icon.

2, after the window, the left side of the data table to be repaired to select “rss”.

3, then in the window, click on the toolbar “New Query” icon.

4. Next, on the window, enter the sql statement “repairtablerss;” for repairing the corrupted MySQL data table.

4. Then on the window, click on the “Execute” icon in the toolbar.

5. Finally, on the window, it shows Repair Corrupted MySQL Table Successfully.

What are the database repair software

Database is generally referred to as a depository system for storing data, most of them are used to store and record the user’s data, if the database is corrupted it will not be able to record the good storage, then you need to repair the database tool, the tool can repair the files and other data of the database, the tool can be used effectively and technically to repair it, it can be repaired due to the loss, accidental deletion, destroyed, formatted after the factor, there are many database repair tools.

The following tools can be used:

SQL Database Repair Tool v6.62 Demo Green Edition

D-RecoveryStandard2.2.1 Green Special Edition

DbvisitStandbyOracle Database Recovery Management Tool 7.0.26 Official Version

sqlserver data how to repair tools

The recovery of mistakenly deleted data in SQLServer is not supposed to be a difficult task, and it can be recovered from the transaction log. However, there are two prerequisites for this recovery:

1. There is at least one full backup of the database before it was deleted by mistake.

2. The Recoverymode of the database is “Full”.

For these two prerequisites, there will be three cases:

Situation 1, if both prerequisites exist, through the SQL statement can be recovered in three steps (refer to the article), without the need to use third-party tools.

a) Backup the transaction log of the current database: BACKUPLOG[database name]TOdisk=N’backup filename’WITHNORECOVERY

b) Restore a full backup before it was deleted by mistake: RESTOREDATABASE[database name]FROMDISK=N’full backup filename’ WITHNORECOVERY,REPLACE

c) Restore the database to a point in time prior to the mistaken deletion: RESTORELOG[database]FROMDISK=N’First step log backup filename’ WITHSTOPAT=N’Point in time prior to mistaken deletion’,REPLACE

Scenario 2, If the 1st prerequisite does not exist and the 2nd prerequisite exists, a third-party tool is required.

Situation III. If the 2nd prerequisite does not exist, recovery is not possible. So, be sure to set the database recovery mode to “Full”.

I am facing the second scenario and need to find a third party tool.

First, I looked for LogExplorerforSQLServer, which doesn’t support SQL Server 2008.

Later, I looked for SQLLogRescue, which also doesn’t support SQL Server 2008.

Next, I found SysToolsSQLRecovery, which supports SQL Server 2008. It supports SQLServer2008, but needs to be purchased, and the Demo version doesn’t have data recovery.

Finally, I found RecoveryforSQLServer on officerecovery.com, although it is also a commercial software and needs to be purchased, the Demo version can recover data as long as the database file is not more than 24Gb. Luckily, my friend’s database file is not big, and I used it to complete the recovery of accidentally deleted data.

Here are the steps to share the recovery with RecoveryforSQLServer:

1. Run RecoveryforSQLServer

2. Click File>Recover in the menu, select the database data file (.mdf)

to recover.

3. Next>Next, enter the RecoveryConfiguration interface, select Custom (selected Custom can only choose to recover accidentally deleted data from the log).

4. Next, enter the Recoveryoptions window, check Searchfordeletedrecords, and select the database to be recovered log file path (logfilepath).

5. Next and select the destination folder (Destinationfolder), which is used to store the SQL statements and bat files generated during the recovery process.

6. Click Start to begin the recovery operation (generate the appropriate SQL files and bat files in the destination folder selected in the previous step), and then the SQLServerDatabaseCreationUtility window appears.

7. Next, select the target database where the recovered data will be stored.

8. Next, select Importavailiabledatafrombothdatabaseandlogfiles

9. Next, Next, and then the data recovery is complete!