You'll receive

Bi-weekly updates

Exclusive discounts

Product update alerts

Tools for Security and Compliance ApexSQL Security and Compliance Toolkit for SQL Server
Tools for DBAs and Operations Engineers ApexSQL Operations Toolkit for SQL Server
Tools for SQL Server Professionals ApexSQL Fundamentals Toolkit for SQL Server
Tools for Developers and DevOps Engineers ApexSQL DevOps Toolkit for SQL Server
Tools for MySQL Professionals ApexSQL Fundamentals Toolkit for MySQL Server
Spotlight Cloud hosted SQL Server monitoring and diagnostics
LiteSpeed High-speed SQL Server backup, compression and restore

ApexSQL Recover

Important notice

Expand all

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


What are the limitations of the ApexSQL Recover which could prevent the successful recovery of all data?

What other issues may negatively affect the ability to recover all lost data?

How can I increase my chances of a successful recovery?

What is the most appropriate recovery solution for my specific case?

Is it possible to recover lost data when database is in the simple recovery model?

Is there another ApexSQL tool that can be used in conjunction with ApexSQL Recover when performing data recovery?

Is it possible to recover dropped databases?

Is it possible to recover corrupted data?

Does ApexSQL Recover require a full backup?

Can the ‘export from database backup’ feature be used to migrate the table to a lower SQL Server version?

Can the recovery from drop/delete/truncate processes be performed when s connection to the database is not available?

Why was my recovery only partially successful?

What are server-side components and why do I need them?

Should I use ApexSQL Recover instead of ApexSQL Log to recover deleted data?

What is a ‘full chain of transaction log files’?

Why doesn’t ApexSQL Recover generate indexes and primary keys during lost data recovery

Can I use ApexSQL Recover to see who made the changes in addition to recovering them?

Can I send my database and backups to ApexSQL in order to get it recovered?

Where can i find video guides for recovery with ApexSQL Recover?

Can 100% successful recovery be guaranteed by ApexSQL?

Licensing and evaluation

How is ApexSQL Recover licensed?

Do i need multiple licenses if i need to install ApexSQL Recover on one machine and connect to the remotely located server?

Are there any restrictions or limitations in the evaluation version of ApexSQL Recover?

I was unable to evaluate ApexSQL Recover properly and my trial has expired. Do you offer extension and how can I get it?

Is my ApexSQL Recover license transferable between SQL Server instances?

What is the licensing model of ApexSQL Recover in a clustered SQL Server environment?

© 2022 Quest Software Inc. ALL RIGHTS RESERVED.   |   GDPR   |   Terms of Use   |   Privacy