Idera strives to ensure our products provide quality solutions for your SQL Server needs. The following known issues are described in this section. If you need further assistance with any issue, please contact Support (www.idera.com/support).
Because the SQL Virtual Database setup program runs silently when you choose to install or upgrade this tool, no error messages display to warn you after the install or upgrade fails. Some reasons why an install or upgrade will fail include:
C:\
You can now deploy SQL Virtual Database to virtual SQL Server instances located on the nodes of a Windows 2003 or Windows 2008 Server Cluster.
You cannot install SQL Virtual Database on computers running Windows Server 2000. For more information, see the product requirements.
SQL Virtual Database does not support attaching backup files written to a Trivoli Storage Manager (TSM) device. However, you can extract the data files to disk, and then attach the copied data files.
When you run the CLI REMOVE
action to drop a failed virtual database, the SQL VDB Console will continue to display that virtual database as though it is still attached. To work around this issue, remove the virtual database using the Console.
After a cluster node fails over, SQL Server may incorrectly report that the virtual databases attached to the virtual SQL Server instance hosted on that node are corrupted. This invalid error is most likely to occur during the failover process when the SQL Server Agent restarts before the SQL VDB Service restarts.
By default, the SQL Server 2012 security model creates a unique, restricted user for each service account. This configuration prevents the SQL Server Service from writing data files to the SQL VDB virtual database file location, causing the attachment of a virtual database to fail.
To work around this issue, assign the appropriate permissions to the default user SQL Server created for the SQL Server Service account.
SQL Virtual Database may require more time to create a virtual database when the selected backup files contain a large number of transactions. Because you can select full, differential, and multiple transaction log backups, a significant number of transactions may need to be recovered before the virtual database can be created. This issue is more likely to occur if the corresponding physical database incurred transactions during the backup operation.
For more information about virtual database creation, see how SQL Virtual Database works.
You may experience slower performance when attempting to attach a large SQL Safe backup file located on a network share.
You may experience slower performance when attaching backup files that contain multiple data sets. This issue is more common when attaching SQL Server backups.
Need more help? Search the Idera Customer Support Portal
Idera Website | Products | Purchase | Support | Community | About Us | Resources | Legal |
---|