Access the SQL Virtual Database Release Notes
SQL Virtual Database helps you quickly and easily access data and objects from your backup files without performing costly restore operations or impacting your production servers.
You can get a quick glimpse into the newest features, fixed issues, and known issues in this release of SQL Virtual Database by accessing the Release Notes.
o Review issues fixed by this release o Review previous features and fixed issues o See known issues
o See list of recommended Idera Solutions
Get Started
Use the following checklist to get started with SQL Virtual Database. Get Started Checklist Steps
Locate the backup files for the database you want to attach.
Decide whether you want to attach a full backup file or attach multiple data files such as transaction log backups.
Create the virtual database according to your specific recovery needs. Use the Query tool to verify your virtual database was attached correctly.
Use SQL Server Management Studio or another database management tool to view, compare, recover, and report on objects and data from your virtual databases.
Decide whether you want to update your existing SQL Server backup jobs to create file maps auto-matically after the regularly scheduled backup operation is completed. This improves the virtual database performance, allowing you to more quickly access future backups.
Monitor the amount of disk space used by your virtual databases.Typically, virtual databases require a frac-tion of the disk space consumed by a fully restored backup. If you are virtualizing large databases, you may need to allocate additional disk space over time.
Welcome to SQL Virtual Database
SQL Virtual Database is a powerful one-of-a-kind solution that lets you quickly and easily attach SQL Server backup files and query them like real databases.
Need help using SQL Virtual Database? See the following sections:
l Configure your deployment l Create virtual databases
l Learn how to use virtual databases l See Tips and Tricks
What is SQL Virtual Database?
Idera SQL Virtual Database (SQL VDB) is a powerful one-of-a-kind solution that lets you attach SQL Server backup files and query them like real databases. With its revolutionary, patent-pending technology, you gain instant access to critical data in a backup file without spending the time and storage previously required for restore. In minutes, you can create a virtual database and then use any native SQL Server or third-party tools to query and extract the data you need.
SQL Virtual Database offers:
Virtual recovery
Provides instant, feature-rich access to all data from within SQLsafe backup and native SQL Server backup files.
Point-in-time selection
Provides point-in-time selection and recovery, allowing granular control over the state of the data displayed in the virtual database.
Native SQL Server and third-party application access
Use existing SQL Server tools such as SQL Server Management Studio and third-party applications to interact with the new virtual database as though it were an actual physical database.
Intuitive Console
Allows virtual databases to be quickly and easily created, edited, or removed.
No impact to production servers
Installs to a single non-critical server and attaches all virtual databases to a single SQL Server instance.
How SQL Virtual Database helps
Database administrators are often asked to recover a backup in order to recover objects and data, compare two systems, or run a report. Previously, the only way to do this is to restore the database, a consuming activity that requires time and storage.
SQL Virtual Database lets you create a ‘virtual database’ that appears to SQL Server and third-party applications as a physical database. This virtual database provides direct access to the data without a restore. This direct access greatly reduces the time required for data recovery,increases your productivity, and reduces resource requirements.
With SQL Virtual Database, you can: o Eliminate long restore times
o Access a backup file and retrieve the objects or data you need immediately o Save massive amounts of storage
o Execute any query
o Use backups for reporting, data extraction, data analysis, and more
o Take the load off your production servers and experience zero impact on production databases
o Access full, differential, and transaction log backup files made by Idera SQL Safe Backup and SQL Server
How SQL Virtual Database works
SQL Virtual Database is driven by a unique, patent-pending recovery technology that makes backup files behave like regular phys-ical databases. This technology allows you to create virtual databases by directly attaching backup files to SQL Server without requiring a restore operation.
Each virtual database is hosted by the SQL Server instance you specify. All objects and data in the virtual databases are access-ible to SQL Server jobs and stored procedures, T-SQL scripts, and other third-party applications.
The SQL VDB Engine, which consists of the Filter Driver and Filter Service, manages the virtual database and services the SQL Server I/O requests to the virtual data files. As the SQL VDB Engine attaches your selected backup files and creates the vir-tual database, it consolidates all the transactions and presents them to SQL Server for recovery. During this process, SQL Virvir-tual Database "maps" the data from the backup files. If the data is already "mapped", such as through SQL Safe or the Map Gen-eration CLI action, then SQL Virtual Database proceeds to the virtual database creation.You can create a virtual database by attaching specific data sets from multiple full, differential, and transaction log backups.
You can then use the SQL VDB Console, or any other third-party tool, to perform queries against specific virtual databases or simply check the status of your virtual databases. For more information, see our instructions on how to use your virtual database, as well as tips and tricks.
The product features, such as the virtual database creation, are also available through the SQL VDB CLI. For more information, see the product component descriptions.
How SQL VDB works with SQL Safe Backup
SQL virtual database seamlessly converts SQLsafe backup files into virtual databases. You can use SQL virtual database with any backup file generated by SQLsafe 5.0 or later. For more information, see the product requirements.
When you attach a backup file previously created by SQLsafe 5.0, the SQLvdb Engine performs the same steps as it does with the native SQL Server backup. To optimize performance for large databases, use the Map Generation CLI action to generate the required metadata before attaching the backup files.
With SQLsafe 6.0 or later, you can configure your backup operation to automatically generate the metadata. By default, this option is enabled when you perform a new manual backup or define a new backup policy. For more information, see the SQL Safe online Help.
Virtual data files created by SQL VDB
For each virtual database you create, several files are also created to support the new virtual database. These virtual data files are:
File Description Location Can you move it? When is it deleted?
*.xbm *.xcm *.xdm *.xtm
Files that the SQ VDB Driver creates to map the data in the selec-ted backup files.
In the same folder where you store your backup files.
No. Moving these files will cause errors when you attempt to access the virtual database.
Never ...
After you have retrieved the data you need from the virtual database, you can use the groom feature to delete unused data files, manually delete these files, or schedule a job to peri-odically groom old files.
*.lcf *.mcf *.ncf
Files that the SQL VDB Service creates when reading changed pages from the transaction log for the selected backup files.
In the VDB/S-parse folder under the Pro-gram Files dir-ectory on the client com-puter.
No, but you can specify a new loc-ation ...
Moving these files when the virtual database is attached will cause errors when you attempt to access its data. To choose a different location for these files, delete your virtual data-bases, and then specify a new dir-ectory path. When you create the next virtual database, the SQL VDB Engine will use the new path.
When the virtual database is removed (dropped) from the SQL Server instance.
*.lxf *.mxf *.nxf
Virtualized versions of the .lcf and .mcf files associated with the selected backup set. None ... These files are place-holders for SQL Server.
No, these files do not exist on your disk.
When the virtual database is removed (dropped) from the SQL Server instance.
File Description Location Can you move it? When is it deleted? *.vdb An XML file that
con-tains the configuration information for the vir-tual database.
In the Repos-itory folder under the Pro-gram Files dir-ectory on the client com-puter.
No. Moving these files will cause errors when you attempt to access the virtual database.
When the virtual database is removed (dropped) from the SQL Server instance.
Disk space allocation
The amount of disk space consumed by the virtual data files depends on the size and content of your backup files. For more information, see the recommended disk space allocations.
TIP The size for these files may display incorrectly in tools such as Management Studio. To see the cor-rect size, use Windows Explorer to navigate to the file and then view the file properties.
SQL VDB tips and tricks
Idera provides several tips and tricks so you can get the most value from SQL Virtual Database. You can watch a video demon-stration or read customer testimonials on the Idera Web site (http://www.idera.com/Products/SQL-toolbox/SQL-virtual-data-base/).
The following tasks are a small sample of the many ways you can use your virtual database: o Create DDL scripts for entire databases, tables, or rows
o Identify rows that were added, modified, or deleted since your last backup o Recover stored procedures
o Recover tables using bulk copy
o Report on data changes using T-SQL queries
o Run historical reports using Microsoft Reporting Services o View user, role, or schema changes
All of these tasks can now be done without restoring the database!
Find answers
This documentation set includes a comprehensive online Help system as well as additional resources that support you as you install and use the product. You can also search the Idera Solutions knowledge base, available at the Idera Customer Service Portal (idera.secure.force.com).
Contact Idera
Please contact us with your questions and comments. We look forward to hearing from you. For support around the world, please contact us or your local partner. For a complete list of our partners, please see our Web site.
Who? How? Sales 713.523.4433
1.877.GO.IDERA (464.3372) (only in the United States and Canada)
Sales Email
Support 713.523.4433
1.877.GO.IDERA (464.3372) (only in the United States and Canada)
http://www.idera.com/Support
Web site
www.idera.com
Document conventions
Idera documentation uses consistent conventions to help you identify items throughout the printed online library.
Convention Specifies
Bold Window items
Italics Book and CD titles
Variable names New terms
Fixed Font File and directory names Commands and code examples Text typed by you
Straight brackets, as in [value] Optional command parameters Curly braces, as in {value} Required command parameters Logical OR, as in value 1 |
value 2
Exclusively command parameters where only one of the options can be spe-cified
About Idera
Idera is a leading provider of application and server management solutions. We have a wide variety of performance management products for Microsoft SQL Server, and award-winning server backup solutions for both managed service providers and enterprise customers. Idera products install in minutes and start solving server problems immediately, giving administrators more time, reduced overhead and expenses, and increased server performance and reliability. We are a Microsoft Gold Certified partner, headquartered in Houston, Texas, with offices in Asia Pacific, Australia, New Zealand, Europe, Africa, and Latin America. So we're everywhere your IT needs are.
Idera products
Our tools are engineered to scale - from managing a single server to enterprise deployments with thousands of servers. Idera products combine ease of use with a design that installs in minutes, configure in hours, and deploy worldwide in days. To learn more about Idera products, visit http://www.idera.com/productssolutions/sqlserver.
Legal notice
Idera, Inc. (“Idera”) makes information and products available on this web site, subject to the following terms and conditions. By accessing this web site, you agree to these terms and conditions. Idera reserves the right to change these terms and conditions, and the products, services, prices, and programs mentioned in this web site at any time, at its sole discretion, without notice. Idera reserves the right to seek all remedies available by law and in equity for any violation of these terms and conditions. THIS WEB SITE COULD INCLUDE TECHNICAL OR OTHER INACCURACIES. CHANGES ARE PERIODICALLY MADE TO THE INFORMATION HEREIN. HOWEVER, IDERA MAKES NO COMMITMENT TO UPDATE MATERIALS ON THIS WEB SITE.
Trademark
IntelliCompress, PowerShellPlus, SharePoint enterprise manager, SharePoint security manager, SharePoint diagnostic man-ager, SharePoint backup, SharePoint performance monitor, SQL Elements, SQL check, SQL change manman-ager, SQL comparison toolset, SQL compliance manager, SQLcompliance, SQLcm, SQL defrag manager, SQL diagnostic manager, SQLdm, SQL mobile manager, SQLpermissions, SQLsafe, SQLsafe Freeware Edition, SQLsafe Lite, SQL schema manager, SQLsecure, SQLsmarts, SQLstats, SQLtool, SQL toolbox, SQL virtual database, SQLvdb, virtual database, Idera, BBS Technologies and the Idera logo are trademarks or registered trademarks of Idera, Inc., or its subsidiaries in the United States and other jurisdictions. All other company and product names may be trademarks or registered trademarks of their respective companies. Elements of this web site are protected by trade dress or other laws and may not be imitated or reproduced in whole or in part.
Copyright
The information on this web site is protected by copyright. Except as specifically permitted, no portion of this web site may be dis-tributed or reproduced by any means, or in any form, without Idera’s prior written consent.
Use of the Software
The software and accompanying documentation available to download from this web site are the copyrighted work of Idera. Use of the software is governed by the terms of the License Agreement, which accompanies such software. If no license accom-panies the download, the terms of the license, which accompanied the original product being updated, will govern. You will not be able to use, download, or install any software unless you agree to the terms of such License Agreement.
Use of web site information
Except as otherwise indicated on this web site, you may view, print, copy, and distribute documents on this web site subject to the following terms and conditions:
1. The document may be used solely for informational, personal, non-commercial purposes;
2. Any copy of the document or portion thereof must include all copyright and proprietary notices in the same form and manner as on the original;
3. The document may not be modified in any way; and
4. Idera reserves the right to revoke such authorization at any time, and any such use shall be discontinued immediately upon notice from Idera.
Documents specified above do not include logos, graphics, sounds or images on this web site or layout or design of this web site, which may be reproduced or distributed only when expressly permitted by Idera.
Warranties and Disclaimers; Liability Limitations
EXCEPT AS EXPRESSLY PROVIDED OTHERWISE IN AN AGREEMENT BETWEEN YOU AND IDERA, ALL INFORMATION AND SOFTWARE ON THIS WEB SITE ARE PROVIDED "AS IS" WITHOUT WARRANTY OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
IDERA ASSUMES NO RESPONSIBILITY FOR ERRORS OR OMISSIONS IN THE INFORMATION OR SOFTWARE OR OTHER DOCUMENTS WHICH ARE REFERENCED BY OR LINKED TO THIS WEB SITE.
IN NO EVENT SHALL IDERA BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION, THOSE RESULTING FROM: (1) RELIANCE ON THE MATERIALS PRESENTED, (2) COSTS OF REPLACEMENT GOODS, (3) LOSS OF USE, DATA OR PROFITS, (4) DELAYS OR BUSINESS INTERRUPTIONS, (5) AND ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF INFORMATION) WHETHER OR NOT IDERA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU.
Submissions
With the exception of credit card numbers for the purchase of products and services, Idera does not want to receive confidential or proprietary information through its web site.
Any information sent to Idera, with the exception of credit card numbers, will be deemed NOT CONFIDENTIAL. You grant Idera an unrestricted, irrevocable license to display, use, modify, perform, reproduce, transmit, and distribute any information you send Idera, for any and all commercial and non-commercial purposes.
You also agree that Idera is free to use any ideas, concepts, or techniques that you send Idera for any purpose, including, but not limited to, developing, manufacturing, and marketing products that incorporate such ideas, concepts, or techniques.
Idera may, but is not obligated to, review or monitor areas on its web site where users may transmit or post communications, including bulletin boards, chat rooms, and user forums. Idera is not responsible for the accuracy of any information, data, opin-ions, advice, or statements transmitted or posted on bulletin boards, chat rooms, and user forums.
You are prohibited from posting or transmitting to or from this web site any libelous, obscene, defamatory, pornographic, or other materials that would violate any laws. However, if such communications do occur, Idera will have no liability related to the content of any such communications.
Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, indi-viduals, or data.
Governing Law and Jurisdiction
You agree that all matters relating to your access to, or use of, this web site shall be governed by the laws of the state of Texas. You agree and hereby submit to the exclusive personal jurisdiction and venue of the state courts of Texas located in Harris County, Texas, and the United States District Court for the Southern District of Texas, with respect to such matters.
Idera makes no representation that information on this web site are appropriate or available for use in all countries, and prohibits accessing materials from territories where contents are illegal. Those who access this site do so on their own initiative and are responsible for compliance with all applicable laws.
Export Control Laws
Certain Idera products, including software, documentation, services, and related technical data, available on the Idera and other web sites are subject to export controls administered by the United States (including, but not limited to, the U.S. Department of Commerce Export Administration Regulations (“EAR”)) and other countries including, controls for re-export under European Union, the Singapore Strategic Goods Control Act, and the import regulations of other countries. Diversion contrary to U.S. or other applicable law of any Idera product or service is prohibited. Export, re-export or import of products and services may require action on your behalf prior to purchase and it is your responsibility to comply with all applicable international, national, state, regional and local laws, and regulations, including any import and use restrictions. Idera products and services are currently pro-hibited for export or re-export to Cuba, Iran, North Korea, Sudan, Syria, or to any country then subject to U.S. trade sanctions. Idera products and services are prohibited for export or re-export to any person or entity named on the U.S. Department of Com-merce Denied Persons, Entities and Unverified Lists, the U.S. Department of State's Debarred List, or the U.S. Department of Treasury's lists of Specially Designated Nationals, Specially Designated Narcotics Traffickers, or Specially Designated Ter-rorists. Idera products and services are prohibited from use with chemical or biological weapons, sensitive nuclear end-users, or missiles, drones or space launch vehicles capable of delivering such weapons. By downloading or using any product from this web site, or purchasing any service, you are acknowledging that you have read and understood this notice and agree to comply with all applicable export control laws. You are also representing that you are not under the control of, located in, or a resident or national of any prohibited country, and are not a prohibited person or entity. This notice is not intended to be a comprehensive sum-mary of the export laws that govern the products and services. It is your responsibility to consult with a legal advisor to ensure compliance with applicable laws.
United States Government Rights
All Idera products and publications are commercial in nature. The software, publications, and software documentation available on this web site are "Commercial Items", as that term is defined in 48 C.F.R.§2.101, consisting of "Commercial Computer Soft-ware" and "Commercial Computer Software Documentation", as such terms are defined in 48 C.F.R. §252.227-7014(a)(5) and 48 C.F.R. §252.227-7014(a)(1), and used in 48 C.F.R.?12.212 and 48 C.F.R. 227.7202, as applicable. Pursuant to 48 C.F.R. §12.212, 48 C.F.R.§252.227-7015, 48 C.F.R. §227.7202 through 227.7202-4, 48 C.F.R. §52.227-19, and other relevant sections of the Code of Federal Regulations, as applicable, Idera's publications, commercial computer software, and commercial com-puter software documentation are distributed and licensed to United States Government end users with only those rights as gran-ted to all other end users, according to the terms and conditions contained in the license agreements that accompany the products and software documentation, and the terms and conditions herein.
Installation and deployment
Deploy an installation of SQL Virtual Database to each SQL Server computer that hosts the databases you want to virtualize. Install all of the product components on the same computer. You can deploy SQL Virtual Database to a clustered SQL Server environment using Windows Server 2003, Windows Server 2008, or Windows Server 2012.
To install SQL Virtual Database:
1. Review the product requirements.
2. Log onto the target computer using an account with administrator privileges. 3. Download and install the SQL toolbox.
4. From the Tools available for install list, select SQL Virtual Database. 5. Click Install.
6. Start the SQL VDB Console. When you start the Console, the licensing console displays.
7. Choose the appropriate licensing option. You will need a production license for each computer on which you install SQL Virtual Database. For more information, see product licensing.
Upgrade to this release
You can easily and quickly upgrade to the latest version of SQL Virtual Database. For more information about this release, see what’s new.
TIP If you have modified your virtual databases, such as inserting table data or deleting schema objects, and want to keep your changes, back up your virtual databases before upgrading.
To upgrade:
1. Use an administrator account to log onto the target computer.
2. Use the SQL VDB Console to remove any virtual databases you have previously attached. Removing a virtual database will delete it.
3. Start SQL Toolbox. 4. Click the Updates tab.
5. Select SQL Virtual Database, and then click Install. SQL Toolbox silently installs the latest version.
6. Update any previously defined SQL Server Agent jobs to use the new CLI actions and options. You may have created SQL Server Agent jobs to:
o Use the Map Generation utility o Groom old virtual database files
o Automate virtual database creation for new SQL Server backups 7. Start the SQL VDB Console, and begin attaching virtual databases.
Product components and architecture
Before installing SQL Virtual Database, check the following product component definitions and architecture, and review how the product works.
SQL VDB components
CLI
Is the command line interface. The SQL VDB CLI calls the Management Service to manage the creation, modification, and removal of your virtual databases. You can call the CLI from new or existing T-SQL scripts, such as your SQL Server backup jobs. To access the SQL VDB CLI, start the Windows Command Prompt, and then enter sqlvdbcmd to see which options you can use.
Console
Is the user interface that allows you to manage your virtual databases and query any data or object from the virtual data-bases. You can also use the SQL VDB Console to change your product configuration and access online Help.
Filter Driver
Is a component of the SQL VDB Engine that is attached to a specific drive on the target SQL Server computer. The driver handles the SQL Server I/O requests required to create the virtual database. To optimize performance, the driver finds and attaches to the first available drive each time it receives a request to create a virtual database.
Engine
Consists of the SQL VDB Filter Driver and the Filter Service. The engine components communicate with SQL Server, and create and maintain your virtual database.
Filter Service
Is a component of the SQL VDB Engine that is installed on the target SQL Server computer. The SQL VDB Filter Service uses the configured Windows account or SQL Server login credentials to communicate with SQL Server. This service also coordinates with the driver to retrieve data from the specified backup files and then create data files for your virtual data-base. You can specify a different folder in which to store the virtual data files.
Virtual Data Files
Is a set of files that includes information about your product configuration, virtual database settings, and other data. For more information about these files, review how SQL VDB works.
SQL VDB architecture
The following graphic illustrates the relationship between the product components. All SQL VDB components are installed on the same physical SQL Server computer.
Product requirements
You can easily and quickly install SQL Virtual Database on any computer that meets or exceeds the following hardware, soft-ware, and permission requirements. Also review the product components and architecture as well as how the product works.
TIP The SQL VDB Filter Service no longer requires ports for communication between components. The Filter Ser-vice now uses Inter-process communication (IPC) to communicate with the Filter Driver and Console.
Console requirements
Ensure the computer on which you want to install the SQL VDB Console meets or exceeds the following requirements. Hardware/Software Requirement
CPU 2.0 GHz or higher
Memory 1 GB
32-bit Operating Sys-tem
Either:
o Windows Server 2003 R2 o Windows Server 2003 SP2 o Windows XP SP2 or later
o Windows Vista Business and Enter-prise
o Windows 7
o Windows Server 2008 o Windows Server 2008 R2
Hardware/Software Requirement Plus:
o .NET Framework 2.0 or later o MDAC 2.8 or later
64-bit Operating Sys-tem
Either:
o Windows Server 2003 R2 (x64) o Windows Server 2003 SP1 (x64) o Windows XP Professional (x64) o Windows 7
o Windows Server 2008 o Windows Server 2008 R2 Plus:
o .NET Framework 2.0 or later o MDAC 2.8 for later
SQL Server versions o SQL Server 2005 SP1 or later o SQL Server 2008
o SQL Server 2008 R2 o SQL Server 2012 RTM
Browser Internet Explorer 7.0 or later (for the online Help)
Backup file requirements
Backup File Attributes Requirements SQLsafe versions SQLsafe 5.0 or later
SQL Server versions o SQL Server 2005 SP1 or later o SQL Server 2008
o SQL Server 2008 R2 o SQL Server 2012 RTM
Backup Types o Full
o Differential o Transaction log
File Types o Single file
o Multiple files o Striped files
Permission requirements
The SQL VDB Filter Service account requires the following permissions. By default, setup program will assign the Local System account to the Filter Service. During install, you can input credentials for a Windows user account or SQL Server login.
Permissions Actions Taken Member of the Builtin Administrators Windows group on the SQL Server computer where the
SQL VDB Engine is installed
Create or edit virtual database
Read and write access rights on the folder where backup files are stored Read backup files and write temporary files
Disk space requirements
Use the following table to help you set aside the appropriate amount of disk space for your virtual databases. Virtual databases typically require a fraction of the disk space consumed by a fully restored backup. Before creating virtual databases, ensure you allocate the recommended additional disk space for each virtual database you plan to create.
Size of Backup Additional Disk Space
1 TB 105 MB
500 GB 51 MB
100 GB 10 MB
1 GB 105 kB
500 MB 51 kB
For more information about virtual data files, see how SQL Virtual Database works.
Deploy to a Windows cluster
Use the following instructions to deploy SQL Virtual Database in a clustered SQL Server environment. When deployment is com-plete, you can attach virtual databases to a virtual SQL Server instance located on an active Windows Server 2003, Windows Server 2008, or Windows Server 2012 cluster node. To ensure virtual databases can be used after a failover occurs, deploy SQL Virtual Database on each node in the Windows cluster.
TIP Ensure the backup files you want to virtualize are stored on either a network share or the drive assigned to the SQL Server resource group.
Enable fault tolerance for virtual database access
Use this process to enable fault tolerance for your virtual databases. Fault tolerance ensures you can continue accessing any vir-tual database on your Windows cluster when a node fails.
1. Use an administrator account to remotely log on to the active node of your cluster. 2. Open a new Command Prompt window.
3. For each SQL Server instance hosted on that cluster node, run the following command. This command creates a Generic Script Resource that controls failover for all virtual databases for that specific SQL Server instance, running this command per each clustered instance (not per node).
SQLvdbcmd Cluster FilterService SQLServerName
Configure your deployment
After initially installing and setting up SQL VDB, there are several tasks you might want to do in order to further customize and streamline your deployment.
o Update your existing SQL Server Agent jobs to use new CLI actions
o Change where the SQL VDB Engine stores cached files during the virtual database creation o Collect SQL VDB logs for troubleshooting
o Groom unused virtual data files
o Increase performance by preparing backup files for future data retrieval o Manage your product license
Collect logs for troubleshooting
Use the System Diagnostics window to collect verbose logs that can be used for troubleshooting by Idera Support. By default, high-level logging is always enabled for SQL Virtual Database activities and events.
To access system diagnostics:
1. On the SQL Virtual Database Welcome window, click Help & More. 2. Click System Diagnostics.
To collect the logs:
1. Ensure the Enable Debug Mode option is selected.
2. Click the collection button. SQL VDB creates a zipped folder of the specified log files and places this folder on the Windows desktop. By default, the zip folder is named IderaSQLvdbCollectionLogInstanceNameTimeStamp.zip.
3. Email the zipped log folder to Idera Support.
To collect the logs for issues encountered when installing SQL Virtual Database:
1. Start the Windows Command Prompt.
2. Navigate to the installer directory (by default, C:\Documents and Settings\User Name\My Documents). 3. Type one of the following commands:
Server Type Installation Command
x86 (32-bit) msiexec /i SQLvdb.msi /l*v C:\MyFolder\SQLvdb_install.log x64 (64-bit) msiexec /i SQLvdb-X64.msi /l*v C:\MyFolder
\SQLvdb_install.-log
4. Step through the setup program until you recreate the issue. SQL Virtual Database generates the resultant log file in the loc-ation you specified.
5. Email the log file to Idera Support.
Groom unused virtual data files
Use the Settings window to groom (delete) any unused virtual data files.
To groom your data files, click Clean Up. SQL Virtual Database automatically detects and deletes any virtual data files that are not being used or are not needed to support your existing virtual databases. By default, these virtual data files are located in the FilterMetaData folder under the Program Files directory (C:\Program Files\Idera\SQL virtual database).
TIP This feature is also available through the Cleanup action in the command line interface (CLI). To get more inform-ation, enter sqlvdbcmd in the Windows Command Prompt.
For more information about other configuration tasks, see Configure your deployment.
Manage your license keys
Use the Manage SQL VDB License option to view details about your trial or production license and perform actions such as activating a license.
From the licensing console, you can: o Verify current status of your license o Extend your trial period
o Register and activate your license o Deactivate your license
For more information about other configuration tasks, see Configure your deployment.
Access the licensing console
You can access the licensing console from SQL VDB by clicking Help & More, and then clicking Manage SQL VDB License.
About the SQL VDB trial license
By default, SQL Virtual Database installs with a limited-time trial license key that is valid for the computer on which you have installed the tool.
When you decide to move from a trial implementation of SQL virtual database to your production environment, contact and obtain a license key from Idera.
How SQL VDB licensing works
SQL Virtual Database checks for a valid license each time you start the tool. A valid license is a trial or production key that has been registered for the computer on which you have installed the SQL Virtual Database tool.
If your license expires, such as when the trial period ends, the Console functionality will be limited to removing previously created virtual databases and managing your product license. You can continue to access existing virtual databases using tools such as SQL Server Management Studio.
If your license is deactivated, you will no longer be able to use the tool. You can re-install the tool and reuse a previously deac-tivated production key.
Register your software
Use the Register Idera SQL virtual database window to start the license activation process and begin using this product.
Once your software is registered, you have 14 days to complete the license activation. You can continue using all the product fea-tures during that 2-week period. After your product registration has expired, you will no longer be able to use the product.
How do I access this window?
When you start the tool's user interface, such as the SQL VDB Console or SQL Admin Toolset Launchpad, the Licensing Console will automatically open when you start the tool.
To proceed to this window, click Register.
Fields
Name
Type your full name in this required field.
Organization
Type the name of your company, business unit, or department in this optional field.
Serial Number
Copy the product serial number to this required field.
Actions and Tasks
Activate Automatically when I am online
Select this option to allow the licensing engine to automatically activate your registered license key the next time you are online. This option requires an active Internet connection.
Register
Registers this product with Idera. This action starts the license activation process by sending your license key and com-pany information to Idera.
Try
Runs the product in trial mode, allowing you to continue evaluating this product.
Choose how to activate your license
Use the Activate Idera SQL virtual database window to choose how and when you want to complete the activation process. Activate your license as soon as possible after registering your software. Once your software is registered, you have 14 days to complete the license activation. You can continue using all the product features during that 2-week period.
After your product registration has expired, you will no longer be able to use the product.
TIP You can activate one license per computer at a time. That is, each installation of the tool requires a unique license key.
How do I access this window?
When you start the tool's user interface, such as the SQL VDB Console or SQL Admin Toolset Launchpad, the Licensing Console will automatically open. To proceed to this window, click Register, enter the required information on the Register Your Software window, and then click Register.
Actions and tasks
Activate over the internet
Connects to the Idera Web site and confirms that you have entered a valid license key. No additional action is needed. This action requires an Internet connection.
Activate by entering a code
Allows you to activate your license over the phone or through email. Use this option when you do not have Internet access from computer on which you installed the software.
Activate later
Allows you to activate your license at a later time. The product license remains registered with Idera.
Cancel
Stops the license process at this step. The next time you start the product, the Licensing Console will prompt you to activ-ate your license.
Try a different serial number
Allows you to use a different license key. After selecting this option, click Register and the Register Idera SQL virtual data-base window displays again.
Activate your license manually
Use the Activate Offline window to manually activate your license key when the target computer (on which the product is installed) does not have Internet access or is otherwise offline. Use the provided buttons to copy the necessary information and then email or call Idera Licensing to activate this license.
How do I access this feature?
When you start the tool's user interface, such as the SQL VDB Console or SQL Admin Toolset Launchpad, the Licensing Console will automatically open.
To proceed to this window, click Register, enter the required information on the Register Your Software window and click
Register, and then choose the Activate by Entering a Code option.
To manually activate your license:
1. Use the provided buttons to copy the license key and machine code.
Licensing provides you with an activation code.
3. Enter the activation code in the corresponding field on this window.
Actions and tasks
Copy license key and machine code to email Idera
Click Copy to Email to open a new email message, pre-populated with the license key and machine code, that you can immediately send to Idera Licensing to start the manual activation process.
Copy license key and machine code for your records
Click Copy to Clipboard to copy your license information and then paste it into an application such as Microsoft Word.
Return to the previous activation window
Click Go Back to return to the Activate Your License window and choose a different activation route.
Complete the license activation
Click Activate to complete the license activation process and begin using this product in production.
Fields
Activation Code
Allows you to enter the activation code provided by Idera Licensing.
Machine Code
Displays the serial number of the computer on which you have installed the registered product..
Machine ID
Displays the corresponding ID number for this computer..
Serial Number
Displays the serial number you entered when you registered the product.
Deactivate your license
Use the Deactivate License window to disable the currently active license key. You should deactivate the product license when you want to:
l Un-install the tool. You can re-install this tool on the same computer later.
l Migrate your installation from one computer to another. After migrating this tool to another computer, you will be prompted to complete the license activation process for the installation on the new computer.
To immediately deactivate the product license for this tool, click Deactivate.
TIP Deactivation requires Internet access. If the computer does not have Internet access or is otherwise unavailable, con-tact Idera Licensing to deactivate the license manually.
How do I access this window?
When you start the tool's user interface, such as the SQL VDB Console or SQL Admin Toolset Launchpad, navigate to the Help & More menu, select Manage SQL VDB, and then click Deactivate.
For tools that use a command line interface (CLI), such as SQL Safe Lite, deactivation can be performed through the Start menu (for example, Start > All Programs > Idera > SQL Safe > Deactivate SQL Safe Lite License).
Actions and Tasks
Cancel
Stops deactivation. You can continue to use this license key for the product installation on this computer.
Deactivate
Deletes the license key and activation information for the product installation on this computer. If you do not use this license key for another installation on a different computer, you can later re-install the product on this computer and re-activate the license key.
Extend your trial period
Use the Extend License Use Period window to add more time to your trial period for this specific tool. You can extend your trial before or after the original time period expires, and you can only extend your trial license once.
If your trial key has not yet expired, or if you previously extended your key, the Licensing Console returns an error.
How do I access this window?
When you start the tool's user interface, such as the SQL VDB Console or SQL Admin Toolset Launchpad, the Licensing Console will automatically open when you start the tool.
To proceed to this window, click Extend.
Actions and Tasks
Copy license key and limit code to clipboard
Click Copy to Clipboard to copy your trial license information and then paste it into an application such as Microsoft Word.
Return to the previous trial license window
Click Go Back to return to the main licensing window and choose a different action.
Extend your trial license online
Click Extend Online to connect to the Idera Web site, where the system validates that your current trial license has expired, and then adds 7 more days to the total trial time period. This action requires an Internet connection.
Extend your trial license manually
Email your trial license information to Idera Licensing, asking for a trial extension code. Type the code into the Extend Time field and click Extend.
Fields
Extend Time
Allows you to enter the new trial license key provided by Idera.
Limit Code
Displays the trial identification code.
Serial Number
Displays the trial license key.
Prepare backup files for future data retrieval
Use the Map Generation CLI action prepares your backups for future data retrieval.
You can use this CLI action to automatically generate virtual data files for specific backups on a routine basis. For example, you can schedule a SQL Server job that searches for new backup files and then generates the corresponding virtual data.
By building the virtual data before attempting to attach the backup file, you can decrease the time required to create the virtual database and get faster access to your data and objects. The larger the database is, the more time you can save by preparing your backups. For more information about virtual data files, review how SQL Virtual database works.
Consider running this action on backups for mission-critical and sensitive databases, as well as databases that often require object recovery and data retrieval.
You can specify any of the following options: o Individual backup files from a single location o Striped back up files from multiple locations o Specific data sets contained in the backup files o Connection credentials
o Password used to decrypt an encrypted SQL Safe backup file
o Whether the SQL VDB CLI should retry this action when a network file error occurs To see a detailed description of each option, enter sqlvdbcmd Map at the command prompt.
When to use map generation
You should use the Map Generation CLI action whenever you need to decrease the time required to create a virtual database. Con-sider using this action for the following types of backups:
o Large SQL Server backups o SQL Safe 5.0 backups
Note that you can run this CLI action manually by opening the Windows Command Prompt, and then typing the appropriate com-mand when the prompt displays.
To run the Map Generation CLI action in a job:
1. Install the SQL VDB on the SQL Server computer that hosts the databases you routinely back up. 2. Use Microsoft Management Studio to connect to the associated SQL Server instance.
3. Create a new job for this instance.
4. At the beginning of the job, insert a new step.
5. Input the following minimum code for this step. Additional options are available.
sqlvdbcmd Map MyFolder\MyBackupFiles\Name.bak -WindowsUsername targetdomain\account -WindowsPassword password
6. Schedule the job to run on a routine basis, such as once a week during off-hours. 7. Save the job.
8. Test your update by manually running the job.
Specify where the virtual data files are stored
Use the Settings window to specify which folder SQL VDB uses to stores data files when creating a virtual database. For more information about virtual data files, review how SQL VDB works. For more information about other configuration tasks, see Con-figure your deployment.
You can type the directory path for the folder you want to use or click the browse button to navigate to the folder. Once you have specified the appropriate folder, click OK.
TIP Ensure the SQL VDB Filter Service account has read and write access rights on the specified folder. For more information, see the product requirements.
Update SQL VDB jobs to use new CLI
SQL VDB 2.0 and later includes a new command line interface (CLI) that offers new functions and replaces the previous Map Gen-eration utility.
If you are upgrading from SQL VDB 1.x to SQL VDB 2.0 or later, you must update any SQL jobs that use the previous SQLvdbCLI commands. Starting with SQL VDB version 2.0, all SQLvdbCLI commands have been obsoleted.
Use the following table to identify which SQLvdbCLI commands you will need to replace with new CLI actions. For detailed descriptions and available options, see the CLI Help (sqlvdbcmd Help action).
CLI commands for 1.x Corresponding actions for 2.0 and later
SQLvdbCLI sqlvdbcmd
-Create Create
-Update Create
-Remove Remove
CLI commands for 1.x Corresponding actions for 2.0 and later -EncryptWindowsPassword EncryptWindowsPassword
None available EncryptSqlPassword
None available EncryptRestorePassword
-List None available
SQLvdbMapGen Map
TIP SQL VDB CLI actions and options are not case-sensitive.
Update jobs that call the Map Generation utility
The Map Generation utility was used with SQL VDB versions 1.x. This utility has been replaced by the Map Generation CLI action
that is included with the SQL VDB CLI.
For each job that calls the Map Generation utility, update your code to use the Map Generation CLI action instead: 1. Use Microsoft Management Studio to edit the job.
2. Find and delete this code:
sqlvdbmapgen -BackupFile MyFolder\MyBackupFiles\Name.bak -WindowsUsername tar-getdomain\account -WindowsPassword password
3. Enter this new code:
sqlvdbcmd Map MyFolder\MyBackupFiles\Name.bak -WindowsUsername tar-getdomain\account -WindowsPassword password
4. Save the job, and then run it manually to validate that it completes as expected.
Update grooming jobs
You can use SQL Server Agent jobs to groom (delete) unused data files associated with your virtual databases.
For each job that grooms virtual data files, update your code to use the new CLI action:
1. Use Microsoft Management Studio to edit the job. 2. Find and delete this code:
sqlvdbcli -Cleanup 3. Enter this new code:
sqlvdbcmd Cleanup
4. Save the job, and then run it manually to validate that it completes as expected.
Update jobs that restore backups as virtual databases
For each job that creates virtual databases, update your code to use the new CLI action:
1. Use Microsoft Management Studio to edit the job. 2. Find and delete this code:
sqlvdbcli -Create -Database MyNewVirtualDB -Full MyFolder\MyBackupFiles\Name.bak -InstanceName TargetServer -WindowsUsername targetdomain\account
-Win-dowsPassword password 3. Enter this new code:
sqlvdbcmd Create VirtualDatabaseName MyFolder\MyBackupFiles\Name.bak -Win-dowsUsername targetdomain\account -WindowsPassword password
Create Virtual Databases
Create virtual databases to access, compare, recover, and report on data from previous backups of databases in your envir-onment.
For example, you can create multiple virtual databases, at different points in time, from backups of the same live database. This strategy allows you to compare column values and schema objects from one version of the database to another version several days later without restoring the database.
You can create a virtual database by either: o Attaching a single full backup file
o Attaching multiple backup files, including transaction log backups Virtual databases can be created through the SQL VDB Console or CLI.
To access the SQL VDB CLI:
To access the SQL VDB CLI, start the Windows Command Prompt, and then enter sqlvdbcmd to see which commands and options you can use. For more information about the SQL virtual database components, see the product components.
About virtual databases
A virtual database (vdb) is a patent-pending software implementation of a database that allows for data storage and retrieval like a physical database.
Because a virtual database acts like a physical database, you can access any data or object in the virtual database using T-SQL scripts, third-party applications, reporting tools, and database management tools such as Microsoft SQL Server Management Stu-dio. Database management tools interface with and display the virtual database as a physical database.
Each SQL Server instance can host multiple virtual databases.
What you can do with a virtual database
Any operation that you can perform on a physical database can be performed on a virtual database. Likewise, applications that rely on getting information from this database can continue using the virtual version.
You can use the built-in query tool to execute commands on objects in this virtual database. You can also access this virtual data-base using Microsoft SQL Server tools, such as Management Studio, and other third-party applications. For more information, see our tip and tricks.
TIP You can modify the data and objects in the virtual database. However, because the virtual database is based on archived data, your changes will not persist when you recreate the same virtual database later. To preserve your changes, back up the modified virtual database and then create a new virtual database using those backup files.
Attach a single backup file
Use the Attach Full Backup window to easily create a virtual database from a single full backup file. For more information about how you can use the virtual database, see our tips and tricks.
TIP When you select a backup file, SQL Virtual Database opens the file in shared read mode. When Microsoft SQL Server or Idera SQL Safe attempts to append (write data to) or delete this file, the backup operation will fail because the file is locked for read. If your backup policies or jobs are configured to append new data sets to this file, change your backup settings so that a new and unique file is created for each backup.
You can select any full backup files created by Microsoft SQL Server or Idera SQL Safe. For more information, check the sup-ported backup file formats.
The Attach Full Backup window includes the following fields:
Backup File
Type or browse to the directory path and filename of the backup file you want to use. You can specify a single file for any full backup performed on the target database.
Backup files can be located on the local computer or a network share. To specify a network path, use UNC snytax (\\MyServer\MyFolder\MyBackup.bak).
Host Instance
Type the name of the SQL Server instance that should host the virtual database. You can browse for instances running on the local computer.
Virtual Database Name
Type a unique name you want to use for your new virtual database. This name will be displayed in the Console and in other database management tools, such as Microsoft SQL Server Management Studio.
By default, SQL VDB stores the database files for this new virtual database in the location you defined using the Settings window.
Attach multiple backup files
The Attach Multiple Backups wizard lets you build a live virtual database based on data from specific backup files. With this wiz-ard, you will:
o Select the backup files you want to include
o Select the date and time up to which you want data
o Specify how you want the virtual database to display in the Console and other tools For more information about how you can use the virtual database, see our tips and tricks.
Select backup files
Use the Backup Files tab to select which backup files you want to use to create your virtual database.
TIP When you select a backup file, SQL Virtual Database opens the file in shared read mode. When Microsoft SQL Server or Idera SQL Safe attempts to append (write data to) or delete this file, the backup operation will fail because the file is locked for read. If your backup policies or jobs are configured to append new data sets to this file, change your backup settings so that a new and unique file is created for each backup.
You can select any full, differential, and transaction log backup files created by Microsoft SQL Server or Idera SQL Safe. For more information, check the supported backup file formats.
After you add your backup files, SQL virtual database checks the LSN (log sequence number) range of each file to ensure it is in sequence. When the LSN range is out of sequence, the affected files do not contain all of the logged transactions required to cre-ate an accurcre-ate virtual database.
If an LSN range is out of sequence, such as a gap between one file and the next, the affected files are displayed in orange text. To resolve this issue, add more backup files to fill the LSN gap. Also consider verifying the backup files to ensure a complete backup had been performed. For more information, see Microsoft SQL Server Books Online.
Actions and tasks
Add a backup file to the list
Click Add to select a backup file to use when creating this virtual database. To add a file, first type the path and filename in the provided field, or browse for the files. You can also use wildcards to find folders or files that match a naming convention. If the selected backup file contains data for more than one database, you will be prompted to choose which data set you want.
If the selected backup file contains encrypted data, you will be prompted to provide the password required to decrypt the file.
If the backup was written (or striped) to multiple files, you will need to add each file in the stripe.
Browse for backup files
Click the browse button to find the files you want to use.
Configure encryption settings
Select the listed backup files that are encrypted and then click Encryption Settings to specify the password required to decrypt the data.
Remove a backup file from the list
Click Remove to delete a previously selected backup file from the list of files to use when creating this virtual database.
Columns and fields
Created
Provides the date and time when the backup files were created (that is, when the corresponding backup operations were per-formed).
Database
Provides the name of the database whose data was archived in this backup file.
Filename
Provides the name of the backup files you selected.
First LSN
Provides the LSN at which each backup file starts. For more information about LSN ranges, see Microsoft SQL Server Books Online.
Instance
Last LSN
Provides the LSN at which each backup file ends. For more information about LSN ranges, see Microsoft SQL Server Books Online.
Type
Indicates which type of backup was performed when the selected files were created.
Choose the target point in time
Use the Point in Time tab to choose the exact date and time at which you want to create the database.
You can pick any date and time included in the data sets of the selected backup files. If you do not see the point in time you want, you may need to choose different backup files. For example, to pick an hourly interval, select transaction log backup files.
Actions and tasks
Pick a date and time
You can use either the slider or the calendar to pick the exact date and time you want to recover. After you select a date and time, SQL virtual database lists which data sets will be used to create the virtual database up to the selected point in time.
Pick an LSN
SQL Server 2005 and later allows you to use a LSN (log sequence number) to identify the point at which you want to recover data. To recover up to a specific LSN range, select LSN from the drop-down menu, and then choose the appropriate backup file.
Verify data sets
Use the grid to verify which data sets will be used to create the virtual database up to the selected point in time. Depending on the point in time you selected, SQL virtual database may not need to use all the data sets available in the backup files.
About a point in time
A point in time provides a historical perspective of a physical database at the specified date and time. You can create multiple vir-tual databases, representing different points in time, from the same set of backup files. For example, you can create three virvir-tual databases that represent the physical database on Monday, Tuesday, and Wednesday. You can then access data and objects from the database as it existed on Monday, Tuesday, or Wednesday.
A point in time can help you:
o Analyze different versions of the same database o Copy different versions of the same object
o Compare changes in data and schema objects from one time period to another o Report on data that existed at a given date and time
Use the slider to pick a point in time during any hour of the most recent day in the selected backup files. As you hover over the slider, the available time intervals display. To pick a time, click the corresponding interval.
Use the calendar interface to choose a date and time in any available month by selecting the appropriate area on the displayed day. As you hover over a day, the available hour intervals display. To pick a time, click the corresponding interval.
The calendar interface indicates whether data is available for a given date and time, based on the backup files you selected. The calendar shows when different types of backups were performed to help you choose the correct files so that you have the data you need.
Specify how the Console creates this database
Use the Create As tab to specify how SQL VDB should create your new virtual database.
TIP The specified name and description will display in the Console and in other database management tools, such as Microsoft SQL Server Management Studio.
Actions and tasks
Specify the host instance
Type the name of the SQL Server instance that should host the virtual database.
Specify the virtual database name
Type a unique name for your new virtual database.
Choose where to store your database files
Click Database Files to customize the location where SQL VDB stores the files for your new virtual database. By default, SQL VDB uses the location defined in the Settings window.
On the Database File Locations window, specify the appropriate directory locations, and then click OK. The Database File Locations window allows you to manage the paths where SQL VDB restores new data files and log files. SQL VDB creates the file name automatically using the file type and destination database name for easy identification.
Specify a description
Type a description for this virtual database. Use a description that includes details about this data set to help you troubleshoot issues, administer your databases, or recover specific objects.
Review a summary of your new virtual database configuration
Review the provided summary, and then click Finish. When you finish this wizard, SQL Virtual Recovery will create a virtual data-base according to your specifications.
After you complete this wizard, the Console will list your new virtual database in the Welcome window. You can use the built-in query tool to execute commands on objects in this virtual database. You can also access this virtual database using Microsoft SQL Server tools, such as Management Studio, and other third-party applications.
If you want to change a setting now, click Back to return to the appropriate window. You can also change these settings later using the Edit button on the SQL VDB Console Welcome window.
Edit connection credentials
Use the Edit Credentials window to specify different connection credentials.SQL virtual database will use these credentials to connect to the target SQL Server instance, read the specified backup files, and create the virtual database.
By default, the SQL VDB Service credentials are used. However, the service account credentials may not have the appropriate privileges on the target SQL Server instance or the directory where the backup files are stored. This issue is more likely to occur when backups have been striped across multiple files located in different network shares.
Ensure you specify a Windows account that has the appropriate permissions, and then click OK. For more information, check the
permissions requirements.
Resolve missing backup files
Use the Missing Striped Backups window to resolve issues caused by missing data files. This window displays when a backup file you selected is one of several files created by a striped backup and you did not select all of the files required to create the vir-tual database.
To specify more backup files, type the path and filename of each file (or use the browse button to navigate to the target file), and then click Add.
For more information about how striped backups work, see Microsoft SQL Server Books Online.
How to use your virtual database
You can access your virtual database using any third-party tool, such as: o SQL Admin Toolset Multi Query tool
o SQL Comparison Toolset o SQL Server Management Studio For more usage ideas, see our tips and tricks.
To use the Multi Query tool in the Idera SQL Admin Toolset:
1. Click Multi Query from the SQL Admin Toolset Launchpad.
2. Add a new query or open an existing query. For more information, see the SQL Admin Toolset online Help.
3. Execute your query against the selected targets. In this case, the selected targets should include the virtual databases you want to query.
To use SQL Server Management Studio:
1. Connect to the SQL Server instance that is hosting your virtual database. 2. In the Object Explorer, expand the Databases node.
3. Select your virtual database from the list. Each virtual database will display as a physical database. 4. Perform an action or run a query. For usage ideas, see Tips and Tricks.
Test your virtual database
You can test your new virtual database using Microsoft SQL Server Management Studio (Management Studio) or the built-in Query Database tool. With either application, you can test your virtual database by performing simple T-SQL queries, such as test-ing whether you can select data from a specific table.
When you click Run Queries on the Welcome window of the SQL VDB Console, SQL Virtual Database starts the Management Studio tool. If Management Studio is not installed on the local computer, SQL Virtual Database starts the built-in Query Database tool instead.
You can immediately begin using the Query Database tool by typing or copying a script in to the editor pane, picking the virtual database on which you want to run your script, and then executing the query you entered. The following actions and tasks are available from this tool.
Choose the target database
Use the Target Database(s) field to select which virtual databases should be tested with this query.
Run the query
Click the execute button to run your script.
Control how your query is run
Use the Query tab on the Options window to set run properties, such as the maximum number of returned rows and the exe-cution timeout value.
Change how the editor pane displays your code
Use the Editor tab on the Options window to set the editor pane properties, such as whether to show line numbers or high-light syntax errors.
