How does the demo version work, and how is it different from the commercial version of Recovery for Sybase?
Both the free demo and the full version of Recovery for Sybase can detect missing or corrupted data in your Sybase database, but the demo is limited to a specific number of rows. It will recover some of the rows to demonstrate the potential for recovery, then replace all additional rows with null values (non-text fields) or “demo” placeholder text (text fields). You can then review the demo recovery to decide whether the full version is a worthwhile purchase.
Should I back up my Sybase database before I make a recovery attempt?
Yes. We advise a full backup before any recovery attempts so that you can make additional recovery attempts if necessary.
Where can I read a more detailed description of the different product license options?
Our Licensing page has this information. Please review license options before making your purchase.
My recovered database seems fine, but the file size is small when compared to my original file. Why does this occur?
There are several reasons for size discrepancies. In the full version of Recovery for Sybase, badly damaged data areas are omitted from the recovery results, which can reduce file sizes significantly. If corruption is severe, the database may lose information, and some features may not be successfully recreated in the output. For this reason, we advise you to try the demo version before using the full version. However, in most cases, slight differences in file size are not a serious issue.
If you are running the demo version of Recovery for Sybase, the file will be much smaller than your original database due to the large number of placeholders (the “demo” text in the recoverable rows).
I ran the program, and Recovery for Sybase created SQL scripts and a batch file in the output folder. How do I take these files and incorporate them into a new database?
Sybase databases can be recreated in two ways. The most time-consuming method is to run SQL scripts individually, starting with schema.sql, then dataNNNN.sql. This will recreate the database, but some users may have difficulty following this process, especially if they are unfamiliar with SQL scripts.
The easier method is to run the batch file that Recovery for Sybase creates during the recovery process. This is located in the same folder as the SQL scripts, and it automates the database restoration.
If I want to make a batch file or run Recovery for Sybase from the command line, what should I know?
First of all, make sure that you have created an output directory (the directory where the recovered files will be stored), as the program will not perform this action for you. Use common patterns to create your commands. An asterisk (‘*’ without quotes) will identify a group of symbols, while a question mark (‘?’ without quotes) will identify single symbols. You should not use angle brackets when creating the command.
The command line call is as follows:
Always back up your corrupted Sybase databases before running any recovery attempt. Command line functionality is available only for Service and Enterprise license owners.