The effective way to find out if a MySQL database is recoverable is to try the demo version of Recovery for MySQL on it. Visit the Demo page for a free copy of the demo.
Product specifications with lists of items recovered and not recovered is available at the Product Information page.
Note: Always backup your original corrupted MySQL database before proceeding with any recovery activity!
What limitations does the demo version of Recovery for MySQL have?
The demo version recovers limited number of rows from the corrupted database. The remaining rows will be blank. Full version of Recovery for MySQL recovers demo-limited records as well.
No additional rows or tables or any other elements and features of the original database will be recovered by commercial version of Recovery for MySQL if absent from demo output.
I have tried the demo. How do I decide whether to purchase the full version of Recovery for MySQL?
Evaluating the results of demo recovery can help in making the decision.
What are the differences between product licenses?
Details of current licensing scheme are described at the Licensing page.
Why do results of recovery contain less data than the original MySQL database?
This is normal. The damaged parts of your MySQL database will convert to zero size on output. The other common reason of file size decrease is when some of features of the original database are not supported and therefore absent from the recovered database.
Demo-recovered database is smaller because it mostly consists of demo placeholders than actual data.
Running Recovery for MySQL from command line (through Windows Start -> Run menu).
If your license type is Enterprise or Service, you can run Recovery for MySQL from command line and use these calls in your batch files. Standard version does not support command line. The format for command line call is:
myr.exe <original filename with path> "<path to directory to store the recovered file(s)>"
(without angle brackets).
Please note that the directory for recovered file(s) should be created before starting the recovery.
Command line mode supports patterns '*' (replaces group of symbols) and '?' (replaces one symbol).
After running Recovery for MySQL on the corrupted database, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new database?
To recreate database, process resulting sql scripts starting with schema.sql and following by dataNNNN.sql. The database will be recreated from scratch.
To make the import procedure more convenient for the end-user an appropriate batch file is automatically created and put in the same folder as sql script(s).