ApexSQL Restore
can attach native or natively compressed backups and backup sets created in SQL Server 2005 and above to any edition of SQL Server 2005 and above, including full and differential database backups as well as transaction log backups.
|
Quick tip: Please note that due to SQL Server limitations you cannot:
|
|
Quick tip: The minimum permissions required to use ApexSQL Restore are:
|
The name of the virtual database doesn’t have to correspond to the name of the actual database the attached backup set was taken from. However, it does have to conform to the SQL Server database naming standards and needs to differ from the names of any other attached physical or virtual database on the SQL instance.
Detached backup sets are listed under same section and can be re-attached in single click. Please note that reattaching a detached backup set by clicking the Attach virtual database command will result in the backup set being attached with the same settings.
For example, if you’ve attached and afterwards detached a full database backup, a differential database backup and the first subsequent transaction log backup from a backup set which contains three additional transaction log backups, clicking the Attach virtual database command will result in those same backups being attached and the same restore path being used; if you want to attach a different backup configuration form the same backup set you’ll need to use the Add virtual database command (i.e. create a new virtual database).
