Toad® for SQL Server

Version 4.5.0  

Release Notes

August 27, 2009


Contents

Welcome to Toad for SQL Server

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

System Requirements

Global Operations

Installation

For More Information

 


Welcome to Toad for SQL Server

Toad for SQL Server is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, as well as instant access to SQL Server expertise.

Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.

Quest Software, Inc., a leading enterprise systems management vendor, delivers innovative products that help organizations get more performance and productivity from their applications, databases, Windows infrastructure and virtual environments.


New in This Release

Review the following sections for updates in this release and new features:

Prerequisites/Installation

General

Automation

Database Administration

General

Object Explorer

Master Detail Browser

Data Management

General

Export Wizard

Data Compare 

Query Development

Query Builder

Editor

Group Execute

Group Execute now generates a single result set that contains the data from the query run on each connection. Toad automatically adds a Connection column to the results to show which connection the data came from.

SQL Recall

Toad supports deleting multiple statements in the SQL Recall window.

Debugger

Project Management

Support for FTP connections, SQL Recall named SQL statements, and Database connections has been added to the Project Manager via the right-click menu. For Database connections, only databases that are currently connected can be added to the Project Manager.

Version Control


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of Toad for SQL Server.

Feature Resolved Issue Defect
Installation/ Upgrade

You can now install Toad on Windows Vista without performing a silent install.

ST#48360
CID#617034

Connections If you migrate settings from a previous version, the Run script on new connection option in Tools | Options | Database | SQL Server no longer points to the path from the previous version. ST#42899
Toad now connects to SQL Server instances on clusters.

ST#59002
CID#694516

Data Attempting to enter data for an XML data type in the Data tab no longer results in an error. ST#42580
Data Compare

Tables that do not include a primary key are now included when comparing data.

ST#41597
ST#41873
CID#465163

Debugger

You can now debug stored procedures with the following input parameters:

  • Binary

  • Varbinary

  • Bit

  • Timestamp

  • Image

ST#41538
CR#133602

ST#41539
CR#133634

ST#41540
CR#133636

Editor Settings specified in the Insert/Replace page under Tools | Options | Editor | Formatter are now applied to INSERT statements. ST#50363
Loading a saved script file that contains code regions no longer hangs Toad.

ST#59101
CID#694196
CID#690239

During a debugging session, opening a new Editor window no longer results in an error.

ST#64703
CID#731773

You can now share formatter settings between team members by clicking Advanced in the Preview tab under Tools | Options | Editor | Formatter, and specifying a network share folder where settings are stored. Each team member must update their folder to point to the shared folder location and selected format.

ST#46425
CID#603026

Code Completion:

  • Aliases and temp tables are now supported.
  • System objects now display by default in Code Completion lists.
  • The delay for displaying the Code Completion list has been reduced from 500 ms to 250 ms.
  • Using code completion with extended stored procedures no longer inserts the extended stored procedure name twice.
  • If you select the "Merge secondary items" checkbox in Tools | Options | Editor | Code Completion, and attempt to filter your column choice when the preceding code uses ( ), the highlighted object now correctly selects the columns.

ST#59056

ST#46871

ST#63366

ST#61989
CID#714933

ST#53700
CID#654327

ER Diagram Setting the maximum objects to a value greater than the default value now correctly applies the setting.

ST#58479
CID#691496

Execution Plan Generating an estimated execution plan in some instances where a statement includes stored procedures no longer results in an error.

ST#42562
CID#556015

ST#41981
CID#496556

Export Wizard/ One Click Export When exporting large results sets (approximately 500K), Toad no longer runs out of memory before the operation completes.

ST#41935
CID#483802

Job Manager

The following note has been added to the "Schedule Windows Tasks" topic in the Job Scheduler help file (topic is available if the Job Manager is open):

"Note: To manage windows tasks on a remote server you must have administrator privileges on the remote computer."

ST#42618
CID#558115

Object Explorer/ Database Explorer A script is now generated when you right-click an object and select Send To | Editor as Script for users, roles, schemas, and logins. ST#50651
Objects for a database that is in standby/read-only mode now display in the Object Explorer.

ST#57926
CID#686214

ST#63234
CID#677598

A Securables tab now displays in the Object Details pane for Users, Server Roles, and Logins.

ST#53706
CID#653163

Tables:

  • (Windows Vista only) Adding or removing a number of columns on a table no longer causes Toad to hang.
  • (Windows Vista only) Attempting to alter a table when a large number of connections are open no longer hangs Toad on Windows Vista.
  • When filtering by owner or schema in the Object Explorer, attempting to create a table now defaults to the owner or schema you selected for filtering.
  • You can now right-click an index in the Index tab of the Object Details pane and select Open Script in Editor to edit the script.

ST#52682
CID#633682

ST#58387
CID#677040

ST#50463
CID#629542

ST#43559
CID#575478

Databases:

  • When restoring a database, if you add a differential backup file and then add a Full backup file, the restore now succeeds.
  • Generating a data script on a large database no longer results in an out of memory error.
  • The action for shrinking a log file has been added back in this release. You can perform this action by right-clicking a database and selecting Tasks | Shrink Database.
  • Backup checks are now disabled by default.

ST#51164

ST#60398
CID#699141

ST#57078
CID#679569

Jobs:

Jobs now use a different icon to indicate whether the job is enabled, disabled, or failed on last execution.

ST#57772
CID#681549

Stored Procedures:

  • When altering a stored procedure, changes made to the ANSI nulls field or Quoted identifier field are not saved.
  • When creating or altering a stored procedure, pressing the ESC key to cancel a Code Completion recommendation no longer closes the window.
  • When viewing the Script tab in the Object Details pane (right-clicking the procedure and selecting View | Details), comments that are imbedded in a multi-line comment between the procedure name and the first parameter are now retained. Parameter lists that have a line feed after each parameter are also retained.
  • When viewing the Script tab in the Object Details pane, parameters are now correctly formatted when the "Automatically format generated SQL" checkbox is selected in Tools | Options | Explorer | General.

ST#44201

ST#56440
CID#676777

ST#53985
CID#656658
CID#678364

ST#54033
CID#654869

Maintenance Plans:

  • (LiteSpeed 4.8 plans converted to SSIS plans) When adding a Back Up Database task to a LiteSpeed 4.8 Maintenance Plan, selecting the Remove files older than checkbox now removes the 4.8 Maintenance Plan.
  • You can now view history for a maintenance plan by right-clicking the plan and selecting View | Details.

ST#52721

ST#57721
CID#684120

Project Manager You can now add the "Add to Project Manager" button to a toolbar.

ST#57280
CID#680346

Query Builder

Update and Delete statements now include the Where clause in the Generated Query tabs.

ST#44655
ST#58344
CID#689012

In the previous release, the online help incorrectly stated that you could not execute INSERT, UPDATE, or DELETE statements from the Query Builder. ST#58345
Reports Currently, the schema report contains information for tables, views, and procedural objects. ST#48513
Attempting to generate the Database User Details report for SQL Server 2005 no longer results in an error.

ST#56146
CID#673910

Version Control

(TFS) The following issues have been resolved: 

  • Toad now supports TFS 2008
  • If you have not selected a sub-project, attempting to add an object no longer results in an error.

ST#55362
CID#661375
CID#67201
CID#690923

ST#51033

If you disable a version control configuration in Tools | Options | Version Control | General, and then enable the configuration, when you click OK a null reference error no longer displays. ST#51933
Selecting the "Do not check in after execute script in Editor" checkbox in Tools | Options | Version Control | General now correctly applies the setting.

ST#61262
CID#709009

(Subversion) Toad has been tested with the CollabNet Subversion Command-Line Client 1.5.6

Notes: 

  • Toad only supports Subversion 1.5.6 or later.
  • Any Subversion client must have svn.exe in its installation directory to use version control in Toad.
  • Tortoise SVN is no longer supported in Toad because it no longer includes svn.exe in its installation directory.

See "Configure Subversion Version Control" in the Toad help for more information.

ST#56045
CID#694019

ST#55937

CID#667983

When renaming an object in version control, Toad drops the original object from version control and prompts you to add the renamed object to version control Note that this newly renamed object does not have any history associated with it.

ST#41786
CID#448598


Known Issues

The following is a list of issues known to exist at the time of the Toad for SQL Server release.

Feature Known Issue Defect
Installation/ Upgrade

Customized options selected in the Configuration wizard are not applied if you are running Toad as a Restricted user.

Workaround:
Customize these settings in the Options pages in Toad (Tools | Options from the menu)

ST#42154
CR#216699

If you migrate settings from the 4.1 release, attempting to search SQLServerPedia.com using SHIFT+F1 in the Editor or using the default Quick Search field (top-right) results in missing functionality such as filtering of results because Google Search is used instead.

Workaround:

  1. In Toad, select Tools | Options | Environment | Quick Search.
  2. Replace the current URL value for SQLServerPedia with the following: 
    http://sqlserverpedia.com/search/toad/
    v1/?query={0} 
ST#65352
The Toad for SQL ServerInstallation Guide and online help incorrectly state that Toad supports read-only installation of the product. N/A
Licensing

(Windows Vista only) The location where the license.key file is stored depends on whether User Account Control (UAC) is enabled in your Windows Vista environment when you install and initially launch Toad.

With User Account Control (UAC) enabled 

If you install Toad as an administrator and:

  • Launch Toad directly from the Installer’s last page and enter the license key, the license.key file is saved in C:\Program Files\Quest Software\Toad for SQL Server 4.5

    Note: You can write to C:\Program Files because you still have administrator privileges.

  • Exit the installer without launching Toad, then launch Toad from the Desktop shortcut or Windows Start menu and enter the license key, the license.key file is saved in the administrator's virtual store folder in:
    C:\Users\Admin\AppData\Local\VirtualStore\Program Files\Quest Software\Toad for SQL Server

    Note: You write to this folder because you run as standard user even if you logged in as an administrator.

  • Exit the installer without launching Toad, switch to a standard user, launch Toad, and enter the license key, the license.key file is saved in the user’s virtual store folder:
    C:\Users\username\AppData\Local\ VirtualStore\Program Files\Quest Software\Toad for SQL Server 4.5

With User Account Control (UAC) disabled 

If you install Toad as an administrator and:

  • Launch Toad from the last page of the installer, Desktop shortcut, or Windows Start menu, and enter the license key, the license.key file is saved in:
    C:\Program Files\Quest Software\Toad for SQL Server 4.5
  • Exit the installer without launching Toad, switch to a standard user, then launch Toad from the Desktop shortcut or Windows Start menu and enter the license key, the license.key file is saved in:
    C:\Users\username\AppData\Roaming\Quest Software\Toad for SQL Server 4.5

N/A
Data

Attempting to right-click a row and selecting Row Count results in a message stating that the row count could not be determined.

ST#56586
Debugger Currently, you cannot debug scripts on SQL Server Express databases. ST#65086
Editor When using the View Object at Cursor (SHIFT+F4) feature, triggers are not found. ST#41627

CR#164917
For Code Completion to work with INSERT statements, you must specify the INTO keyword. ST#64519
Export Wizard/ One Click Export Blob and Binary data types, including FileStreams, cannot be exported in this release.

ST#41665
CR#170430

Limitations when exporting fractional seconds: 

  • When exporting to an Access Database File, exports do not support fractional seconds, so the additional data is not exported.
  • When exporting to an Excel instance, exports support only 3-digits for fractional seconds. However, if you export to an Excel file, it supports all fractional seconds.
N/A
General

(Windows Vista and Windows Server 2008 only) In some cases, attempting to open a SQL file from the Open dialog results in an "Object reference not set to an instance of an object" error message. Toad uses the Microsoft Distributed Transaction Coordinator (DTC) to get Full-Text Search status for a file, but DTC is disabled by default on Windows Vista and Windows Server 2008.

Workaround: 
Enable Network DTC Access on the Toad client. See http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx for more information.

CR#65049
Import Wizard

Currently, you cannot import Excel 2007 files because they are saved using an xlsx format.

Workaround:
Save the Excel 2007 file as a 2003 compatible file before importing it.

ST#42416
CR#221667

Attempting to import data that was exported to an Excel instance where the fractional seconds were truncated results in an error. N/A
Log Reader Currently, the Log Reader does not support new SQL Server 2008 data types ST#59571
Object Explorer/ Database Explorer

If you execute a script in the editor with autocommit disabled, and then hover over a node in the Object Explorer, Toad appears to hang because it is waiting for you to either commit or rollback the current transaction.

Workaround:
Commit or rollback the editor transaction.

ST#55294

Tables:

Currently, you cannot perform an extended alter on a table with a FileStream column. This includes the following actions: 

  • Changing the column order of the table
  • Adding a new column in the middle of the table
  • Changing a column attribute like an IDENTITY
ST#56029

Table and Index Partitioning Wizard:

Currently, you cannot create or manage a partition on a table or index that includes a FileStream column.

ST#59194
Query Builder

When reverse engineering a query from the Query tab or the Editor, the Diagram tab does not support a SELECT statement where the columns are qualified with the database name

Workaround:
When you visualize the query to display in the Diagram tab, Toad automatically creates calculated columns for the columns qualified with a database name. This allows you to execute the query and return the correct result set.

ST#49731
Service Broker Currently, Service Broker does not support SQL Server 2008. ST#60874
SQL Optimizer For a list of known issues, see the SQL Optimizer release notes. N/A
Version Control

If you migrate settings when upgrading Toad, you may have to reconfigure the repository setting in version control if a "Failed to open the settings for module VersionControl reverting to defaults" error displays.

Workaround:

To reconfigure the repository, select Tools | Options | Version Control | Defaults and select the previous repository in the Version control folder field. Your previous project settings are applied.

ST#63004
In previous releases, the method Toad used to generate the script was different than the current method. After upgrading Toad, a message may display stating that objects or files in version control are different than the local version. If your local version is current, you should check the objects and files into version control. N/A
On Subversion, adding a large number of objects can result in decreased performance. ST#50279
The Update Database function for version control often requires that objects be dropped and recreated. If tables are referenced by Foreign Key constraints, the following error occurs when executing the script "Could not drop object N because it is referenced by a FOREIGN KEY constraint."

ST#42093
CR#214601

Version control does not support CLR objects. ST#52089

Third Party Known Issues

The following is a list of third party issues known to exist at the time of Toad for SQL Server release.

Feature Known Issue Defect
Export Wizard/ One Click Export

To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations:  

2003 PIAs

http://www.microsoft.com/downloads/details.aspx?
FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&
DisplayLang=en

2007 PIAs

http://www.microsoft.com/downloads/details.aspx?
familyid=59DAEBAA-BED4-4282-A28C-B864D8BFA513&displaylang=en

CR#138239

 


System Requirements

Client Requirements

Before installing Toad for SQL Server, ensure your client system meets the following minimum hardware and software requirements:

Platform

600 MHz minimum, 1 GHz recommended

Hard Disk Space

104 MB of disk space is required to run Toad.

Memory

512 MB of RAM minimum, 1 GB recommended

Note: The memory required may vary based on the following:

  • Applications that are running on your system when using Toad
  • Size and complexity of the database
  • Amount of database activity
  • Number of concurrent users accessing the database

Operating System

Windows Server 2003 (32-bit or 64-bit)

Windows XP Professional (32-bit or 64-bit)

Windows Vista (32-bit or 64-bit)

Windows Server 2008 (32-bit or 64-bit)

Windows 7 (32-bit)

Important: Toad uses the Microsoft Distributed Transaction Coordinator (DTC) when opening a SQL file to get Full-Text Search status, but DTC is disabled by default on Windows Vista and Windows Server 2008. If you are using either operating system, ensure that Network DTC access is enabled on the Toad client. See http://technet.microsoft.com/en-us/library/cc753510(WS.10).aspx for more information about enabling DTC access.

Additional Requirements

.NET Framework

Microsoft .NET Framework 3.5 (Service Pack 1)

Notes: 

  • The .NET Framework Client Profile is not supported.
  • To run Toad, the .NET security policy must be set to unrestricted. See User Requirements for more information. 

Web Browser

Microsoft Internet Explorer 6.0 or later

PDF Viewer
Adobe Acrobat  Reader 7.0 or later (for viewing the Toad for SQL Server Installation Guide)

(Optional) Spotlight on SQL Server

Spotlight on SQL Server 4.5 or later

Maintenance Plans

To take advantage of Integration Services (SSIS) in maintenance plans, you must install Client Tools 2005 or later on the client where Toad is installed.

Spatial Data Types

To work with spatial data types used in SQL Server 2008, you must install SQL Server 2008 Client Tools or SQL Server Management Studio 2008. 

Copy/Move Database Wizard

The SQL Server Backward Compatibility package is required to use the Copy/Move Database wizard.

Server Requirements

Before installing Toad for SQL Server, ensure your server meets the following minimum hardware and software requirements:

Operating System

  • Windows Server 2000 (Service Pack 4 or later)
  • Windows 2000 Professional Edition (Service Pack 4 or later)
  • Windows XP 32-bit (Service Pack 2 or later) and 64-bit
  • Windows Server 2003 32-bit or 64-bit (Service Pack 1 or later)
  • Windows Vista 32-bit and 64-bit
  • Windows Server 2008 32-bit or 64-bit

Database
Support

SQL Server 2000 (Service Pack 3 or later), 2005 (Service Pack 2 or later), 2008

Note: SQL Server Compact Edition is not supported.

Additional Requirements

.NET Framework
Microsoft .NET Framework 3.5 (Service Pack 1)

Maintenance Plans

To take advantage of Integration Services (SSIS) in maintenance plans, you must install Integration Services on any instance where you want to create maintenance plans.

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the MetaFrame Presentation Server 5.0 and Citrix Presentation Server Clients 10.2. See "Install Toad on Citrix Systems" in the Installation Guide for more information.

User Privilege Requirements

The following user privileges are required for installing and running Toad for SQL Server:

  1. From the Windows Start menu, select Settings | Control Panel.
  2. Double-click Administrative Tools.
  3. Double-click Microsoft .NET Framework 2.0Configuration.
  4. Click + to expand My Computer,and then select the Runtime Security Policy node. A list of tasks for the node display in the right panel.
  5. Click Evaluate Assembly from the list of tasks in the right panel. An Evaluate an Assembly window displays.
  6. Browse to the location of Toad.exe in the File field.
  7. Click Next to view permissions for Toad.exe.
  8. Set the permission to Unrestricted.

Silent Install Requirements

Before you perform a silent installation, the following software must be installed on every system on which you are installing Toad:

For information about installing Toad silently, see "Install Toad Silently" in the Installation Guide.

Debugging Requirements

Verify the following general requirements to ensure that the Debugger operates properly for all SQL Server installations:

Note: Currently, you cannot debug SQL/CLR code.

Configure Debugging for SQL Server 2008 

To debug locally, perform the following on the Toad client

  1. Install the SQL Server 2008 Client Tools on the Toad client.
  2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following

  1. Install the SQL Server 2008 Client Tools on the Toad client.
  2. Make sure the following permissions are set:
  3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2005

To debug locally, perform the following on the Toad client:

  1. Install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.
  2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following:

  1. On the Toad client, do one of the following:

  2. Make sure the following permissions are set:

  3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Configure Debugging for SQL Server 2000

To debug locally, perform the following on the Toad client:

  1. Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed.

  2. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

To debug remotely, perform the following:

  1. On the Toad client, do one of the following:

    Note: The Remote Procedure Call (RPC) service should be started on both the Toad client and server.

  2. Make sure the following permissions are set:

    Note: By default, Windows administrators on a computer running SQL Server are SQL Server sysadmins on that computer.

  3. If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.

Platforms Tested for Debugging Support

The following platforms have been tested for debugging support.

Note: The Service Pack on the client must match the Service Pack on the server unless specified otherwise.

SQL Server 2008 Platforms Tested for Debugging
Client Server
2003 EE (SP1) 2000 (SP4) 2000 Pro (SP4) XP Pro (SP3) Vista Server 2008
2003 EE (SP1) No No No No No No
XP Pro (SP3)

Yes

No No

Yes

No No
Vista No No No No No No
Server 2008 No No No No No No

 

SQL Server 2005 Platforms Tested for Debugging
Client Server
2003 EE (SP1) 2000 (SP4) 2000 Pro (SP4) XP Pro (SP3) Vista Server 2008
2003 EE (SP1) Yes Yes Yes Yes No No
XP Pro (SP3) Yes Yes Yes

Yes

No No
Vista No No No No Yes No
Server 2008 No No No No No No

 

SQL Server 2000 (SP4) Platforms Tested for Debugging
Client Server
2003 EE (SP1) 2000 (SP4) 2000 Pro (SP4) XP Pro (SP3) Vista Server 2008
2003 EE (SP1) No No No No No No
XP Pro (SP2) Yes Yes No

Yes (Local server)

No No
Vista No No No No No No
Server 2008 No No No No No No

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.

This release has the following known capabilities or limitations:

Quest SQL Optimizer for SQL Server—This release supports any single-byte character set. Double-byte or multi-byte character sets are not supported. In this release, all product components should be configured to use the same or compatible character encoding and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America.


Installation

The Toad for SQL Server release package contains the following products:

Installation Instructions

For general installation information, see the Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server | Documentation.


For More Information

Contact Quest Software

Email

info@quest.com

Mail

Quest Software, Inc.

World Headquarters

5 Polaris Way

Aliso Viejo, CA 92656 

USA

Web site

www.quest.com

See our web site for regional and international office information.

Contact Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.

From SupportLink, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.

Note: This document is only available in English. 


© 2009 Quest Software, Inc.

ALL RIGHTS RESERVED.

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

Web site: www.quest.com

Email: legal@quest.com

Refer to our web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Benchmark Factory, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.