Page History
...
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:
- The target computer does not meet the minimum requirements or prerequisites for this tool
- The default installation drive on the target computer is not
C:\ - The SQL VDB Console is running on the target computer
- The SQL VDB CLI is executing a command on the target computer
- Virtual databases are in the process of being created
- Virtual databases are still attached to the target SQL Server instance
...
You cannot install SQL Virtual Database on computers running Windows Server 2000. For more information, see the product requirements.
TSM support
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.
...
- Determine the number of threads
If the server has two or less CPUs, then:
number of threads = (number of backup files x 2) + number of CPUs
If the server has more than two CPUs, then:
number of threads = number of backup files x 5 - Calculate the max memory
max memory = 106KB x number of threads
Per native compressed backup
- Determine the number of threads
If the server has two or less CPUs, then:
number of threads = 2
If the server has more than two CPUs, then:
number of threads = number of backup files - Calculate the max memory
max memory = 1MB + (106KB x number of threads)
Known issues
Using the CLI to remove a failed virtual database does not sync with SQL VDB Console
...
To work around this issue, assign the appropriate permissions to the default user SQL Server created for the SQL Server Service account.
...
For more information about virtual database creation, see how SQL Virtual Database works.
Slow performance when attaching backup files from a network share
...