Database: MySQL 5.6.24 Type InnoDB*There was backup of the physical folder Data of previous months that is used as a basis for importing the current damaged database tablesExcuse the inconvenience, in fact when the database is damaged, the engine will not start. The problem that the database has is irreparable so as the last alternative was to try to import table by table in another new database, or in this case as I had a backup of a couple of months ago, what I did was take that as a base and go erasing and importing table by table which if they could be read.Various tools were tested to see if the damaged but unsuccessful table could be repaired, the data were corrupt.The procedure is basically flying the files of the tables .idb in the folder corresponding to the database, so you need to have a backup or have the database physically, all in file format, preferably the full folder Data or in some cases it may appear as Lib.In order to carry out the dump first it is necessary to already have an armed database with the same structure tables-fields to which you want to dump the files .idb, this can be done in real time with the engine walking with the basic or backup database that has to work, that at least has the structure tables-fields working.It must be understood that part of the work is done with consultations SQL, and part manipulating files so you need to access the physical files of the server MySQLif installed individually, it would be located in the folder C:\Program Files (x86)\MySQL\MySQL Server 5.6 or something similar.In my case, inside the folder MySQL Server 5.6 There's a folder called Data where all data are saved, configured thus by my.ini which saves the configuration, may be different for other server installations.Once we take this data into account, we can start the process (the Server MySQL should be working even if it is with a basic database of the same structure Table-fields).Each database is saved in a separate folder within the folder Data, then, if we have a database called administration_2 as it is in my case, then there will be a folder administration_2 inside the folder Data.Once we have the server booted, you already need to access it through some tool or something that allows you to consult SQLIn my case I use the MySQL Administrator that comes in the package MySQL GUI Tools. And with this it is only left to remove the data from the tables and import the new ones with the following procedure, table by table:1) Go to the database folder, in my case C:\Program Files (x86)\MySQL\MySQL Server 5.6\Data\administracion_2\(2) In this database folder there are two files per table, one in format .frm which saves the structure of the table, and another in format .idb which saves data in format InnoDB, even if the table is empty, this file will still exist and have data inside.3) Open the consultations executioner MySQL by hand, it can be the MySQL Administrator, MySQL Workbenchetc.4) Eliminate data of the empty table, worth incoherence because even though it is empty MySQL it has loaded and in memory, it is deleted with the SQL instruction ALTER TABLE table_name DISCARD TABLESPACE in "table_name" goes the name of the table, which is also reflected in the file name .idb. In my case actividades. The one immediately when running that command SQL It'll be fine. the file .idb corresponding to the table, in my case the command ALTER TABLE àdministracion_2.actividades DISCARD TABLESPACE It'll be fine. the file actividades.idb.(5) Copy the file you want to dump, which corresponds to the table, in the database folder, in my case actividades.idb inside C:\Program Files (x86)\MySQL\MySQL Server 5.6\Data\administracion_2\6) This data is imported with the SQL command ALTER TABLE table_Name IMPORT TABLESPACE in my case "table_name" That's it. activities. The one immediately when running that command SQL It will matter. the newly copied file .idb corresponding to the table, in my case the command ALTER TABLE àdministracion_2.actividades IMPORT TABLESPACE It will matter. the file actividades.idb.NOTE: Not to be confused, the files of the tables must be copied with the same name of the Table.idbIn my case activities.idb to the same place where MySQL erased them when running the command ALTER TABLA table_name DISCARD TABLESPACEBut, MySQL you will not be able to import, you will not find the file of new data to import.The table-by-table procedure is repeated, the only table that could not be updated/recovered is the damaged, the rest of the database if possible, based on an earlier database, and importing table by current corrupted database table.Greetings!