Can this program recover all types of Interbase and Firebird databases?
SecureRecovery for Interbase supports both modern and legacy versions of Interbase and Firebird. Unlike other data recovery programs, it is specifically designed for these file types, and it is capable of recovering large databases (over 2 gigabytes) even when data has become severely corrupted.
SecureRecovery for Interbase looks great. How can I determine whether it will work for my databases?
The easiest way to determine whether this tool will work for your system is to download the free demo version of the software. The demo has the same features as the full version, but it will only recover a limited number of rows in each database table. Each additional text field will be populated with placeholder text, and non-text fields will be blank.
By running the demo and reviewing the output, you can easily determine whether your Interbase or Firebird database is recoverable and decide whether or not to purchase a license. Please note that if tables or records do not appear in the database created by the demo version, those objects will not be recoverable with the full version of the software.
You should also make several backups of corrupted Interbase or Firebird databases before running data recovery software of any kind (including SecureRecovery for Interbase).
I’m ready to purchase the software. Which license is right for me?
View our Licensing page to review available options and to read about the differences between versions. The Standard license is often an appropriate choice for recovering individual databases, but if you would like command line functionality, you will need either the Service or the Enterprise version.
SecureRecovery for Interbase ran successfully, and it created a folder with SQL scripts and a batch file. How do I move my data into a new database?
You will need to process all of the SQL scripts, starting with Schema.SQL, then moving on to dataNNNN.sql.
The program will recreate the database from scratch. The included batch file partially automates the procedure, making the import process much more convenient for end users.
I attempted to process the SQL scripts created by the program, but I am unable to rebuild the database, or the process generates error messages that prevent me from using data. How can I fix this?
In addition to the scripts created by SecureRecovery for Interbase, a batch file called runme.bat will be created to automate the rebuild. Run this batch file, passing a path to ISQL.exe as a command-line argument (for instance: runme.bat c:\Interbase\bin\).
It is also important to note that a database administrator password will be required in order to initiate the rebuild. During the data recovery process, this password is set by default to “masterkey” in all SQL scripts. You will need to take one of the actions listed below to bypass this issue.
The first way to begin the database rebuild process is to manually replace the default Database Administrator (SYSDBA) password. Note that the password should be replaced in every single script created during database recovery.
You can also temporarily change the Database Administrator’s password to “masterkey,” then change it back to the original value after the recreation is complete.
Finally, you can input your desired password into the “Password” field when initializing SecureRecovery for Interbase before selecting the database to be recovered. This is only an option if you have not yet attempted a recovery.
My recovered databases have smaller file sizes than my original databases. Is this normal?
Yes, this is normal and does not necessarily indicate a serious issue with the recovery.
When SecureRecovery for Interbase encounters severely damaged data, its output file will replaces that information with blank space. This can reduce the size of the file. Additionally, some features may become damaged or unavailable as a result of database corruption, and when this occurs, these features will not be included in the output. Most recovered databases are smaller than the original corrupt files.
If you are running the demo version of SecureRecovery for Interbase, the software will only recover a set number of rows in each table, so the file will be much smaller than your original database.
I have the Service or Enterprise version of SecureRecovery for Interbase. How can I use the command line to access the program?
Use the following call for batch files or command line access:
Use the pattern ‘*’ to replace any group of symbols, and ‘?’ to replace an individual symbol. Do not use angle brackets in the call.
Before using SecureRecovery for Interbase in command line mode, make sure that you have created a folder/directory for the recovered databases (you will specify this folder when operating the application). Otherwise, the program may not function as expected.