Toad® for SQL Server

Beta Version 5.0.0.157

Beta Release Notes

Released: March 08, 2010


Contents

Welcome to Toad for SQL Server

New v5.0 Functionality

Resolved Issues and Enhancements

Known Beta Issues

Third Party Known Issues

System Requirements

Global Operations
 

Beta Group


Welcome to Toad for SQL Server

With Toad, developers and database administrators can use a familiar, proven tool to manage databases. Toad empowers developers and administrators, of varying skill levels, to rapidly create and execute queries, automate database object management and develop SQL more efficiently.


 

New v5.0 Functionality

SQL Azure Support

Collaboration

You can now view RSS and Twitter feeds, including Toad Community postings from within Toad using the new Collaboration window. You can access this window from View | Collaboration. Once open, you can click any entry to open the related content. An icon indicates an RSS feed and an icon indicates a Twitter entry.

When you open the Collaboration window, it polls all RSS and Twitter feeds that you have defined in the Collaboration options page (Tools | Options | Environment | Collaboration). The first time you open the Collaboration window, the options page automatically displays.

In the Collaboration options page, you can also define your Twitter account details and a Twitter search to follow in Toad. The search defaults to a specific search depending on which product you use. By default, any posts in Toad are posted to this specific search. You can also clear the Only Search checkbox to display all your twitter posts.

In the Collaboration window, you can click at the top of the window to compose a new entry. You can select the drop-down arrow beside the icon to select which feed you want to post to.

To post to Twitter, use the entry field at the bottom of the window. When using Twitter, if you click an item in the list, an appropriate reply entry is entered in the field. If the post contains a link, that link is opened in the Web Browser as well. To post an update, press ENTER or click the lower-right Twitter icon. If you click the camera icon to the right of the twitter icon, you can toggle whether you want to include a screen shot of Toad with your post (After posting, this option always reverts back to false).

Debugger

Debug Trace

The debugger trace functionality adds the ability of any Toad debugger to generate a trace on a piece of code executed through a debugger, which can then later be replayed to investigate what actually happened during the execution. One additional feature of replaying the trace is that you can step both backwards and forwards in the debugger to evaluate the execution.

You enable debug trace collection by selecting the Collect debug trace checkbox in the Debugger Start Parameters window that displays when starting a debug session. You can also open this window by clicking on the Debugger toolbar.

Note: This flag is cleared after every execution (You probably don’t want to collect execution traces on every execution).

You can also enable and disable trace collection while executing using a new toggle on the Debugger toolbar.

When a debug trace has been created, a window displays that lets you browse through, delete, and replay debug traces. You can also open this window by selecting Debug | Windows | Debug Traces from the menu.

Each item in the list represents saved debug traces and you will only see the traces that were created for the current connection. When you hover over an item in the list, the full name of the piece of code and the value of any specified parameters when you executed it display. To replay a trace, double-click it in the list or click .

You can also generate a coverage report from the trace by clicking .

The debug trace collects the following:

·         Local parameters and arguments. Global variables are not collected by default, but can be enabled in the options.

·         Step information and callstacks.

·         Scripts of all involved code. This means that when you replay a trace you will see the script in the editor as it looked when the trace was created regardless of whether the object has been changed in the database.

The debug trace does not collect the following:

·         Anything returned to the script result or output.

·         The final return value from a function.

When you are executing a trace, the following additional toolbar buttons display to let you step over backwards, step into backwards and step out of backwards.

In addition, debug trace options are available in Tools | Options | Debugger | General

The first option determines whether the trace should record every line executed while debugging or the lines where you break or step over. By default all lines are executed.

The second option determines whether global variables are recorded in the trace. By default, this is not recorded for performance reasons.

Database Administration

Object Explorer

Data Management

Export Wizard

Export Wizard

Import Wizard

You can now execute an import template against a different connection than the one saved with it. For example, this allows you to use the same import template against your test, development, and production databases. To execute the template against a different connection, make sure you are connected to, and the new database has focus in the Connection Manager when you execute the template.

 

Query Development

Code Completion

The following improvements have been made to code completion:

Group Execute

Group Execute includes the following enhancements:

Automation

Tools

Project Manager

You can now open a new project or save a project using buttons on the Project Manager toolbar.

FTP


Resolved Issues and Enhancements

Feature

Resolved Issue

Change Request

 

New in this Beta Drop

 

Code Completion

Code Completion Does Not Properly Recognize UNICODE Data types on INSERT/UPDATE/DELETE Expansion.

CR64574

Completion doesn't handle quoting & dual screen.

CR71480

Data Compare & Sync

SQL Azure: Data Compare Support.

CR71325

Debugger

Debug Trace should collect Script Results.

CR71375

Debug Trace should be able to create a coverage report.

CR71243

Export Wizard

SQL Azure: Export does not work producing "Invalid object name" error.

CR71564

Blobs fail to export from tables tab.

CR41529

Group Execute

We should be consistent in the way we show results regardless of the number of databases selected when on the parent node.

CR70961

Update Group Execute Success - Error Colors to Match Connection Colors.

CR68651

Import Wizard

SQL Azure: Truncate option does not work producing "Error: Reference to database and/or server name in 'DB_AUTO_TEST.dbo.import table3' is not supported in this version of SQL Server."

CR71634

SQL Azure: Import in new table does not work.

CR71566

SQL Azure: Import from several excel files does not work producing syntax not supported error.

CR71648

Object Editor

Resource Governor: Add support for "RESET STATISTICS".

CR71252

SQL Azure: Database Trigger DOE support.

CR71232

SQL Azure: Table DOE support.

CR71000

SQL Azure: Role DOE support.

CR71225

Schema Compare & Sync

"An item with the same key has already been added" error occurs when comparing some snapshots.

CR69735

Script Generation

SQL Azure: Database Trigger script generation.

CR71233

SQL Azure: Table script generation.

CR71224

SQL Azure: Role script generation.

CR71226

SQL Editor

Add the Execute Option to the Context Menu.

CR71323

UI

SQL Azure: SQL Azure Portal Access.

CR71238

Integration of Toad communities into Toad.

CR70991

 
 

In Previous Beta Drops

 

Code Completion

SQL Azure: Code completion does not work for SQL Azure.

CR70951

Improve performance.

CR70986

Improvements to code completion UI.

CR71089

Code completion should be able to give suggestions for column values.

CR71154

Code completion should pop up immediately after choosing a table directly after select.

CR71153

Show parameter hints for code completion when inserting code.

CR71202

When building WHERE condition global variables appear after the columns and before the suggested join operation. Join operation should be at the top.

CR71368

Connection Manager

SQL Azure: Implement connectivity to SQL Azure database.

CR69719

Better way to show which connection you're on in the Obj Explorer if the Conn Mgr is closed.

CR70477

Better handling of services.

CR71237

Stop Instance while Toad is Connected Causes Exception.

CR70639

Data Grid

Copying from grid in editor blows up.

CR71171

Add option to customize format for any datatype.

CR70210

Debugger

Debug Trace: Add debug trace functionality.

CR71209

Debugging should be disabled for encrypted stored procedure/functions.

CR67503

ER Diagrammer

SQL Azure: Implement ER Diagrammer support.

CR70407

ER Diagram: Cannot cancel the long running process.

CR67334

Export Wizard

SQL Azure: Import/Export support.

CR70470

[toad_ss_beta] In Beta 5.0.0.87, I try to export the results grid to Excel I get an exception.

CR70854 (Reported by Rich Jesse)

When multiple tables or views are selected, "Create As New Table" should be disabled.

CR62438

FTP

FTP Enhancement Request - Add an Explorer Style Folder Drop-down List.

CR64874

Import Wizard

Support: Import Wizard failed to recognize the last 3 columns of excel (xls).

CR69303

Group Execute

Move Group Execute from instance-level only functionality to database-level functionality.

CR65552

Not Saving Connection Information.

CR69348

Unavailable Connections Slow Down Group Execute.

CR68775

Object Details

Object Explorer: Improve Job RHS History tab.

CR60031

CLR Objects: There is no way to rename CLR objects.

CR61325

Object Editor

SQL Azure: Login DOE support.

CR70449

SQL Azure: User DOE support.

CR70451

SQL Azure: Uddt DOE support.

CR70453

SQL Azure: Database DOE support.

CR70455

SQL Azure: Synonym DOE support.

CR70443

SQL Azure: Schema DOE support.

CR70445

SQL Azure: Rename DOEs Support.

CR70467

SQL Azure: Stored Procedure DOE support.

CR70447

Filtered Indexes support (Index DOE).

CR68607

Logins: Option "User must change password at next login" is missing from SQL Server logins.

CR64957

Disable Alter actions for System Objects.

CR54674

SQL Server 2008 support - Support of 2008 for DOE: extended alter table.

CR56029

Resource Governor: Resource Pool DOE implementation.

CR68609

Resource Governor: Enable/Disable actions implementation.

CR68617

Resource Governor: Classification Function DOE implementation.

CR69742

Resource Governor: Workload Group DOE implementation.

CR68610

Resource Governor: Remove Classifier Function dialog. Suggestion to add option to drop user-defined function itself.

CR70310

Error altering table in SQL Server 2005.

CR68437 (Reported by cynthiarancho48)

Run DBCC check table instead of using dynamic SQL for Check Tables.

CR67209

Hide Database drop-down in Rename dialogs for all objects. Add option to control to hide specific dropdowns.

CR67208

Filtered Indexes support (Index DOE).

CR68607

Logins: Option "User must change password at next login" is missing from SQL Server logins.

CR64957

Create Database: Impossible to set 'read only' for newly added filestream filegroup.

CR64023

Functions: Incorrect syntax is generated for Rename DOE. Schema is missing.

CR70557

Databases: Exception occurs when trying to click on Create Like DOE.

CR70624

Functions: Exception occurs when open Create like DOE.

CR70566

Tables: Exception when clicking on Create Statistics.

CR70476

Object Explorer

SQL Azure: Implement Object Explorer functionality - LHS.

CR70468

SQL Azure: Stored proc/function execution support.

CR70460

SQL Azure: Implement Object Explorer functionality - RHS.

CR70469

Switching between open connections and the object explorer/editors.

CR65558

[toad_ss_beta] Custom Auto Filter dialog: Allow user option on case-sensitivity and default should be case-insensitive search.

CR42283 (Reported by Matt Sprygada)

Restore Defaults link in Options page incorrectly enables Always Preview Script in Obj Editor checkbox.

CR55874

Resource Governor: LHS infrastructure support.

CR68608

Permissions

Architecture and Appearance changes: Privilege Escalation Framework.

CR69267

Query Builder

SQL Azure: Implement Query Builder support.

CR70408

Upgrading non ansi outers (*= and =*) with ansi LEFT/RIGHT OUTER JOINs.

CR68128

Schema Compare & Sync

SQL Azure: Be able to connect to SQL Azure.

CR69799

SQL Azure: Read objects definition from SQL Azure.

CR69800

SQL Azure: Schema Compare - data model description.

CR70441

SQL Azure: Schema Compare - object script generation.

CR70439

SQL Azure: Schema Compare - synchronization script.

CR70442

Default Schema Snapshot Save Location Still Pointing to Program Files.

CR67763

Script Generation

SQL Azure: Login script generation.

CR70450

SQL Azure: User script generation.

CR70452

SQL Azure: Uddt script generation.

CR70454

SQL Azure: Schema script generation.

CR70446

SQL Azure: Stored Procedure script generation.

CR70448

SQL Azure: Synonym script generation.

CR70444

SQL Azure: Database script generation.

CR70456

SQL Azure: Table indexes script generation.

CR70458

[toad_ss_beta] Bug when editing a stored procedure

CR70960 (Reported by Charles Haines)

UI

Cannot remap keys in Toad.

CR69992

 


Known Beta Issues

Feature

Known Issue

Defect

Installation/ Upgrade/

Uninstall

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)

ST42154
Connections

If you migrate settings from a previous version, the Run script on new connection option in Tools | Options | Database | SQL Server may point to  the path from the previous version. If you later delete the Application Data Directory for the previous version, which contains the script, attempting to connect to any database results in a path not found error. You can click OK and continue working.

Workaround:
Select Tools | Options | Database | SQL Server and navigate to the location of the latest connection script in the Application Data Directory. By default, this script is located in the following directory.

Windows 2003 or XP: C:\Documents and Settings\username\Local Settings\Application Data\Quest Software\Toad for SQL Server 5.0\Templates\Scripts\InitialSqlServer.Sql

Windows Vista or 7: C:\Users\username\AppData\Roaming\Quest Software\Toad for SQL Server 5.0\Templates\Scripts\InitialSqlServer.Sql

ST68623
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.

N/A
Data For some queries, attempting to right-click a row and selecting Row Count results in a message stating that the row count could not be determined. N/A
Debugger Currently, you cannot debug scripts on SQL Server Express databases. ST65086
Editor When using the View Object at Cursor (SHIFT+F4) feature, triggers are not found. ST41627

Starting with the 4.6 release of Toad, any files that you save as Toad Editor Files (.tef) cannot be opened in a previous version of Toad. Attempting to open a newly saved .tef file in a previous version of Toad results in unreadable data.

However, you can open any .tef files created in a previous version of Toad with the Toad for SQL Server 4.6 and later releases, and everything displays properly. 

N/A
Export Wizard/One Click Export
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
Import Wizard 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

The Log Reader requires version 8.0 DDL files in the Microsoft Visual C++ 2005 SP1 Redistributable Package. If these files do not exist on the client, you will need to install them to use some functionality in the Log Reader.

Workaround:
Download and install the Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) on the client from: http://www.microsoft.com/downloads/details.aspx?FamilyID=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en

N/A
Object Explorer/ Database Explorer

Databases:

Currently, if you select the Enable database backup checking checkbox in Tools | Options | Database | SQL Server, the list of databases in the Object Explorer do not indicate the backup status until you press F5 to refresh the list.

ST63855
Table and Index Partitioning:
  • Currently, you cannot create or manage a partition on a table or index that includes a FileStream column.
  • When changing a partitioned table to a non-partitioned table, the Estimate button is disabled so you cannot estimate the compression savings.

    Workaround:
    After you finish altering the table, right-click the table and select Storage | Manage Compression to estimate the compression savings.
  • Currently, estimating index compression savings runs a full table compression savings query, so the estimation may be slow on large tables.

ST59194

ST67986

ST68131

Maintenance Plans:

(Windows 7 only) Attempting to create a maintenance plan on Windows 7 results in an exception error. 

ST68201
Service Broker Currently, Service Broker does not support SQL Server 2008. ST60874
SQL Optimizer For a list of known issues, see the SQL Optimizer release notes. N/A
Version Control If you migrate settings from Toad 4.1 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.

N/A
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

 


Third Party Known Issues

Feature

Known Issue

Defect

Export Wizard

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

Import Wizard

Importing large data sets from Excel (approximately 650,000 rows) is not recommended because of the amount of time it may take. This issue occurs because the Excel import component maintains the output in memory until the import completes. This can cause performance issues depending on the available system resources.

CR#219754

 


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

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
Hard Disk Space 133 MB of disk space for installation.


Note: The disk space required may vary based on the edition of Toad selected for installation.

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 Server 2008 R2 (64-bit)

Windows 7 (32-bit or 64-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 Software .NET Framework
Microsoft .NET Framework 3.5 (Service Pack 1)

Notes:

  • The .NET Framework Client Profile is not supported.

  • In order to run Toad, the .NET security policy must be set to Unrestricted. For information about setting this policy, refer to User Privilege Requirements.

 

(Optional) Spotlight on SQL Server

Spotlight on SQL Server 4.5 or later

 

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)

 

Maintenance Plans

Review the following requirements for using Maintenance Plans:

  • Integration Services that may be a part of the Client Tools 2005/2008 or a part of SQL Server (to take advantage of Integration Services (SSIS) in maintenance plans)
  • (For SQL Server 2008 only) Management Tools - Basic feature from the SQL Server Installer

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

Supported Databases

The following databases have been tested in this release.

  • SQL Server 2000 with SP3 or later
  • SQL Server 2005 with SP2 or later
  • SQL Server 2008

Notes:

  • SQL Server 7.0 (including 70 compatibility mode for 2000, 2005, and 2008 databases) is not supported. For SQL Server 7.0 support, use the legacy version of Toad 3.2.
  • SQL Server Compact Edition is not supported.

Additional

.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 the following:

  • Integration Services that may be a part of the Client Tools 2005/2008 or a part of SQL Server
  • (For SQL Server 2008 only) Management Tools - Basic

Citrix Requirements

Limited testing has been performed 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 Toad for SQL Server Installation Guide.

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.0 Configuration.
  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.

Debugging Requirements

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

Note: The security policy can be applied to the domain or local computer.

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. In Toad, commit or rollback the connection before starting the debugging session.

To debug remotely, perform the following:

  1. On the Toad client, do one of the following:
  1. Make sure the following permissions are set:
  1. In Toad, commit or rollback the connection 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 SP3 or SP4 is installed.

  2. In Toad, commit or rollback the connection 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.

  1. 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.

  1. In Toad, commit or rollback the connection before starting the debugging session.

 


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:


Beta Group

You can join the Toad for SQL Server beta discussion group by sending an email to: toad_ss_beta-subscribe@yahoogroups.com


© 2010 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this guide 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.

 

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.

 

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, AccessManager, ActiveRoles, Aelita, Akonix, AppAssure, Benchmark Factory, Big Brother, BusinessInsight, ChangeAuditor, ChangeManager, DeployDirector, DirectoryAnalyzer, DirectoryTroubleshooter, DS Analyzer, DS Expert, ERDisk, Foglight, GPOADmin, Imceda, IntelliProfile, InTrust, Invirtus, iToken, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, LogADmin, MessageStats, Monosphere, NBSpool, NetBase, NetControl, Npulse, NetPro, PassGo, PerformaSure, Quest Central, Quest vToolkit, Quest vWorkSpace, ReportADmin, RestoreADmin, SelfServiceADmin, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Storage Horizon, Tag and Follow, Toad, T.O.A.D., Toad World, vAutomator, vControl, vConverter, vFoglight, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vSpotlight, vStream, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vBackup, Vizioncore vEssentials, Vizioncore vMigrator, Vizioncore vReplicator, Vizioncore vTraffic, Vizioncore vWorkflow, WebDefender, Webthority, 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 document 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.