Previous features and fixed issues

This build of SQL Virtual Database includes many fixed issues, including the following updates.

2.0.1 Fixed issues

SQL VDB now successfully creates a virtual database in situations when an incompatibility occurs between the SQL VDB Filter Driver and other third-party drivers, such as CA ArcServe, interacting with the target SQL Server instance.
SQL VDB now successfully generates the virtual data map when the data files associated with the archived database are located on multiple physical disks that have different data retrieval speeds.
SQL VDB now successfully creates virtual databases for large backup files stored on a Windows cluster node.
SQL VDB now correctly excludes deleted data and log files when creating a virtual database.
SQL VDB now handles NULL values that may be returned from the operating system when a virtual database is being created, allowing the operation to continue.

2.0 New features

New SQL Server 2012 support

SQL Virtual Database 2.0 fully supports the use of SQL Server 2012 RTM.

New support for FILESTREAM enabled databases

Virtual databases can now be created from databases that contain FILESTREAM data.

New support for TDE encrypted databases

Virtual databases can now be created from databases that are encrypted with Transparent Data Encryption (TDE).

Improved support for DBCC CHECKDB

The WITH TABLOCK keyword is no longer required when running DBCC CHECKDB against virtual databases, resulting in a more thorough integrity check and improved performance.

Improved CLI

The SQL Virtual Database CLI syntax has been updated and new commands have been added for greater flexibility.

2.0 Fixed issues

SQL VDB no longer causes SQL Server Management Studio to return the error “Cannot show requested dialog” when that client tool attempts to display the virtual database properties.
SQL VDB no longer locks the master database when it creates a virtual database on that target SQL Server instance.
Virtual database files now include the name of the source backup file, the name of the virtual database, and have the extension .VirtualDatabase. Learn more about virtual database file changes.
SQL VDB now supports TDE encrypted, native backup files.
You can now create virtual databases from SQL Server database snapshots.
SQL VDB now stores virtual database files in the Program Files directory. Learn more about virtual database file changes.
SQL VDB no longer causes a recovery lock while creating a virtual database. The recovery lock would render the target SQL Server instance inaccessible or make the system databases, such as model, appear corrupted.

1.6 New features

There are no new features in SQL Virtual Database 1.6.

1.6 Fixed issues

Users no longer receive an error when attempting to read or write to memory using a SQL Safe-generated backup file. This issue was a rare occurrence.
SQL VDB now allows you to have multiple mounts using the same encrypted backup file as the source.
SQL Server no longer generates an error message resulting from SQL Server 2000 partially-completed virtual log files returning with no data.
Users who have SQL Server 2000 databases containing multiple log files no longer receive an incorrect virtual log file number used by SQL VDB as an index to the log file arrays.

1.5 Fixed issues

The Attach Multiple Backups wizard now allows you to select multiple log files without forcing the use of the most closely-related full backup file. You can select an appropriate full backup file, and then freely select from the other available log files that are part of the same LSN chain.

1.4 Service Pack 1 Fixed issues

A backup of a virtual database can now be successfully restored or used to create another virtual database.
The Map Generation utility now correctly generates virtual data files for native backups of SQL Server 2008 instances.
The SQL VDB production license now allows you 14 days to activate the license key before it expires.
SQL VDB now correctly handles page validation when creating virtual databases.

1.4 Build 44 New features

The SQL Virtual Database Map Generation utility now supports compressed native backups of SQL Server 2008 databases.

1.4 Fixed issues

This release contains the following fixed issues:

The SQL VDB Engine how correctly detects and handles non-data pages, such as pages containing full-text data, when attaching and searching backup files.
You can now create a virtual database from a full backup and multiple transaction log backups that belong to an unbroken LSN chain, even when additional full backups were performed during the same time frame as the transaction log backups.

1.3 Fixed issue

SQL VDB now successfully attaches a backup file that had been created when the target database was growing. This issue was most likely to occur when the transactions that caused the database growth affected a GAM page. For more information about GAM pages and database growth, see SQL Server Books Online.

1.2 Fixed issue

When creating virtual databases, the SQL VDB Engine now correctly handles:

any LOP_BUF_WRITE transactions in the selected backup files

timeout errors when creating or accessing the virtual data files

1.1 Build 1118 Fixed issue

The SQL VDB configuration files are now encrypted.

1.1 Fixed issues