Repair Toolbox for MySQL

MySql database repair tools

MySQL repair database tool

MySQL repair program for fixing MyISAM and InnoDB databases in Windows.

The main features of the MySQL database repair tool include:

  • repair corrupted databases from MyISAM, InnoDB database engines
  • support Unicode data repair
  • repair tables and data from recovered tables
  • repair view
  • recovering primary indexes and foreign keys
  • restoring simple index keys
  • preview of recovered data
  • preview of recovered structures (as SQL scripts for the creation of objects)
  • selective data saving for objects, structures and data
  • direct export recovered data into MySQL database
  • save recovered data as scripts on HDD
Note: Get acquainted with the professional software team development of Repair Toolbox for MySQL and feel the difference from other freeware or open source solutions, distributed under a GNU General Public License (GPL). The project requires donations from the users of Repair Toolbox for MySQL in order to remove all of the restrictions of the free version. However, it is not required for the evaluation of its data restoration engine, so you can continue testing its features.
Note: MySQL is the registered trademark of Oracle.

System requirements: Windows 98 and above


Step I

Selection of a damaged database file

Step II

Overview of the database structure

Step III

Saving the recovered data

Step IV

Viewing the exported information

Video Manual


MySQL Repair Tool helps to fix errors:

  • Error: Table 't' is marked as crashed and should be repaired.
  • Open the table failed: Can't open the file: '× × ×. MYI' (err no: 145).
  • ERROR 1016: Can't open the file: 'childX.InnoDB'.
  • InnoDB: Cannot find the table “table1/table2” from the internal data dictionary
  • InnoDB: of InnoDB though the .frm file for the table exists. Maybe you
  • InnoDB: have deleted and recreated InnoDB data files but have forgotten
  • InnoDB: to delete the corresponding .frm files of InnoDB tables?"
  • 127 = Record-file has crashed
  • 134 = Record was already deleted (or record file crashed)
  • 144 = Table has crashed and the last repair failed
  • 145 = Table was marked as crashed and should be repaired