For the best web experience, please use IE11+, Chrome, Firefox, or Safari

ApexSQL Recover FAQ

Important Notice

For a variety of reasons, we cannot guarantee a 100% success rate for data recovery, since conditions can vary tremendously from case to case. Because of this, we encourage customers to fully test ApexSQL Recover during the 14-day trial, as well as to contact us to obtain necessary confirmations prior to purchasing. Although ApexSQL Recover is very successful in most cases, in certain cases it may not recover all or even most of your data

ApexSQL Recover fully supports recovery of BLOB values when recoveries are done from online or detached database files, or from database backups. However, ApexSQL Recover doesn’t support recovery of out-of-row BLOB values when doing recoveries from transaction log files. It also doesn’t support the recovery of encrypted data, CLR types, or FILESTREAM BLOBs, among other specific features of SQL Server. Recovery from SPARSE columns and page and row compressed tables is supported


ApexSQL Recover cannot update multiple records if a unique clustered key wasn't defined on the table and thus wasn't specified in the WHERE clause of the UPDATE operation

The following can influence data recovery:

  • The database was switched to the Full recovery model, but a full database backup wasn't created immediately after
  • Not enough information in the provided data sources. This can happen when differential backup is used and some of intermediate backups are missing
  • The more activities are performed on the database after data loss has occurred, the less likely that all data can be recovered

The most critical task to ensure highest recovery possibility is to perform post-accident steps which need to be performed immediately once the disaster has been detected. Full information on the steps can be found in this article

Depending on the nature of the disaster, or from the SQL Server environment specifics, different recovery approaches can be deemed as ‘the best’ for specific cases. To determine the most appropriate one, please follow the recovery flow chart

Yes, the recovery of a database in the simple recovery model is possible, although the recovery can be limited. Since ApexSQL Recover uses the information in the database .mdf file to extract the recovery information, recovery is still possible even in the simple recovery model if the SQL Server has not already overwritten the .mdf file. More details on the topic can be found here

Yes. ApexSQL Log is a transaction log reader which can recover data lost due to delete statement, or create roll-back scripts to undo insert, update, delete or other applications. Furthermore, ApexSQL Diff and ApexSQL Data Diff can be used to compare and synchronize database vs it’s copy, vs. backup, source control, etc.

No, ApexSQL Recover does not help with recovery of corrupted databases or database files

While having access to the full database backups can increase the chance of successful recovery, ApexSQL Recover does not require mandatory presence of full database backups, since it utilizes .ldf and .mdf files in the recovery process.
When performing the extraction from a database backup, a full backup is required, and differential or transaction log backups cannot be used instead

No, downgrade is generally not supported in the SQL Server, and ApexSQL Recover cannot be used to override this SQL Server limitation

Server-side components are ApexSQL Recover components which must be installed on remote servers in order to enable ApexSQL Recover to remotely access all SQL Servers on that machine (nothing is installed on the SQL Server itself and there are no “Agents”). Essentially, server-side components are a single windows service which unlocks online transaction log file for remote access. Full information on what server-side components are can be found in this link

Although the recovery output is the same for both ApexSQL Log and ApexSQL Recover, the mechanisms used for the recovery are different, so if one tool does not recover the deleted records, the other tool might do the job. In general, it all depends on the resources for the recovery. If the user has only transaction log files available, then ApexSQL Log would be the best solution. On the other hand, if .mdf file is available as the source, ApexSQL Recover should be used as primary recovery tool

The full chain of transaction log files/backups is a continuous sequence of transaction log backups which starts with the full database backup followed by subsequent transaction log backup up until the recovery/auditing point

This is by design since it ensures that all possible records are recovered and not prevented by the violation of the primary key (duplicate key) when multiple same records on the same table row are recovered. More on this topic can be found in this article

No, ApexSQL Recover is not an auditing tool, but highly specified recovery tool. In order to see who made changes, when and how, ApexSQL Log can be used to audit transaction log files

No, ApexSQL does not provide recovery services but provides the tools for the recovery (ApexSQL Recover and ApexSQL Log) which users can use directly on their SQL Server instances to perform the recovery

Video guides related to the data recovery can be found at ApexSQL TV

No, for a variety of reasons, ApexSQL cannot guarantee a 100% success rate for data or structure recovery, since conditions can greatly vary from one case to another. With this in mind, all potential customers are encouraged to trial the product, and work with our engineers during the pre-sales to confirm the recovery success potential for their particular case themselves, prior to purchasing

Licensing and evaluation

ApexSQL Recover is licensed per server instance. A single license allows ApexSQL Recover to be licensed on one computer with SQL Server instance installed

No, this is included in the simple license and GUI does not require a separate license

Besides the time limitation of the evaluation period to 14 days, the main restriction during the trial is in the output results. While ApexSQL Recover is in the trial-mode, only every 1/10 rows/objects will be available for the recovery

Yes. If evaluator feels that he was unable to properly evaluate the tool during the trial period, extension for additional 14 days is available. Simply contact ApexSQL Support team with the extension request and your trial will be extended shortly

No, migration from one server instance to another is not available. However, permanent migrations from one SQL Server instance to another are allowed if the current instance is being deprecated or upgraded to the newer version

When licensing ApexSQL Recover in a clustered SQL Server environment, each SQL Server instance on active nodes requires a separate license. Instances on the passive nodes don’t require licensing