ApexSQL Restore release notes

Enhancements:

• Support for SQL Server 2017 CTP 2
• Support for Windows 10 Creators update

Fixes:

• The “There is insufficient free space on disk…” error is encountered when a specific compressed backup file larger than 2 gigabytes is restored

Enhancements:

• SQL Server 2016 support
• Users can now choose between 3 themes: white, colorful or dark

Fixes:

• The 'There is insufficient free space on disk volume' error is encountered when restoring large database if its original size is greater than available space on the disk
• The 'SQL Server indicated a logical consistency-based I/O error: incorrect pageid' error is encountered when querying specific restored database
• Application cannot attach the database on SQL Server where Windows authentication is disabled
• Network servers can be browsed and selected even though restore to remote server is not supported

Enhancements:

• The application now supports restoring to a point in time
• The application now displays restore progress

Fixes:

• The "The path has invalid attributes" error is encountered when trying to restore a SQL Server 2005 database with Full Text Search
• The "There is insufficient free space on disk volume" error is encountered when restoring a database which original size is greater than the available disk space
• The "Unknown file type (1): 6" error is encountered when restoring a specific database
• The "Remove server from the list" option does not work in the Server drop-down list in the "Restore a backup" dialog
• All backups in the "Restore a backup" dialog are deselected when a backup is removed from the list
• The "Unexpected error - Filter driver is not working correctly" and "Sequence contains no elements" errors are encountered and the application stops working when a transaction log backup and database backup for different databases are added

Known issues:

• The "History" list for detached databases is lost when the application is updated to the new version
• The automatic update does not work, the application must be updated manually

Enhancements:

• The application now fully supports SQL Server 2014
• The application now supports restore from network paths

Fixes:

• The "Unknown file type (1): 6" error is encountered when restoring a database backup of a database that contains index files
• The "ApexSql.Common.ActivationBroker had stopped working" error is encountered when starting the application with the Windows DEP feature turned on, or after the Hardware ID had changed
• The "Could not continue scan with NOLOCK due to data movement" error is encountered when attaching a new backup taken from a database with multiple data files
• The "Value Dispose() cannot be called while doing CreateHandle()." error is encountered when restoring a specific backup
• The "ApexSql.Restore.IncorrectRestoreParametersException" error is encountered in case an incorrect backup set parameter value is specified in CLI command
• Database restore fails in case the hard disk's root is selected as the restore path
• The "The operating system returned the error '1117(The request could not be performed because of an I/O device error.)'" error is encountered when trying to attach a specific database
• The Windows warning dialog "Unknown publisher" pops up when trying to activate the application using the online method
• Attached virtual database is not accessible in SQL Server Management Studio after the system is restarted in specific cases
• Added backup file is not automatically checked in the "Restore backup source" step of the application wizard
• The "Exception has been thrown by the target of an invocation." error is encountered when starting the application on a specific system
• The "Disk space saved" statistic and shown details are contradictory

Changes:

• New user interface that follows Metro UI style
• Windows XP is no longer supported

Known issues:

• The "History" list of detached databases is lost when the application is updated to the new version

Features:

• Virtually restores both native and natively compressed SQL backup sets as a fully functional SQL Server databases for the fraction of the time and space need for a native restore
• Supports attaching full, differential and transaction log backups
• Provides access to the data and objects stored in the backup via SSMS, Visual Studio or any third party application
• Allows reading and modifying the objects and data stored in backups access without altering the attached files themselves
• Allows mounting backup sets to a specific point in time
• Supports backups encrypted by TDE
• Supports FILESTREAM
• Supports virtual restores of backups made on SQL Server 2000 and later to SQL Server 2005, 2008 and 2012