Recovery for MySQL

Frequently Asked Questions

Questions And Answers

 
Q: Can Recovery for MySQL repair my MySQL database?
A:

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!

 
Q: What limitations does the demo version of Recovery for MySQL have?
A: 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.

 
Q: I have tried the demo. How do I decide whether to purchase the full version of Recovery for MySQL?
A:

Evaluating the results of demo recovery can help in making the decision.

 
Q: What are the differences between product licenses?
A:

Details of current licensing scheme are described at the Licensing page.

 
Q: Why do results of recovery contain less data than the original MySQL database?
A: 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.
 
Q: Running Recovery for MySQL from command line (through Windows Start -> Run menu).
A:

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

 
Q: 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?
A:

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


Product Guide

Recovery for MySQL

Product Home

Product

Product information
Free demo version is available:
Download

Order

Place an order
Upgrade
Sales assistance
1-888-827-9543
Resellers
Licensing

Support

Request support
Frequently asked questions

Company

Profile
Products
Customers

I need recovery for... Use the product reference to locate a recovery solution for your application file, database, server or media.

Office and Windows

Email

Access

Exchange Server

Excel

Exchange OST

Money

Lotus Notes

QuickBooks

OneNote

PowerPoint

Outlook

Project

Outlook Express

Publisher

Undelete for Outlook

Word

Works

Windows Backup

Windows Registry

Servers

Databases

Active Directory

Access

BizTalk

FileMaker Pro

Exchange Server

Interbase / Firebird

Lotus Notes

MySQL

Project Server

Oracle

SharePoint

Paradox

PostgreSQL

SQL Server

Sybase

SQL Anywhere Server

Visual FoxPro

Other

Media

Zip

Flash Drive

PDF

Hard Drive

JPEG, GIF, TIFF, BMP, PNG or RAW

CD and DVD

Photo File

Diskette

Photoshop

Removable Disk

WordPerfect

Virtual Drive

Writer

Calc


No portion of this website may be reproduced without express written permission by OfficeRecovery
Copyright © 1998-2017 OfficeRecovery