Toad for SQL Server

Version 3.1.0

Release Notes

August 2007


Contents

Welcome to Toad for SQL Server

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations
 

Getting Started

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, and 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.

All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.
 


New in This Release

Review the following:

Updates to Toad for SQL Server 3.1

Updates to Toad for SQL Server 3.0

New Features in Toad for SQL Server 3.1

Graphically create a flow of activities to run or schedule the activities to run at a later time. For example, a single script can run reports, queries, and scripts; save results in Excel spreadsheets and other files; and distribute results to the business community via email or shared file locations. You can also add the automation activities to the Project Manager and double-click them to run them automatically. 

Note: Toad Automation requires Microsoft .NET Framework 3.0. If .NET Framework 3.0 is not installed on your system, you are prompted to install it when you try to open the Automation Script Designer.

Automation Activities let you automatically:

To access this feature, select Tools | Automation Script Designer from the menu.

New Features in Toad for SQL Server 3.0

 


Resolved Issues and Enhancements

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

Resolved Issues and Enhancements in 3.1

 Feature

 Resolved Issue

 Change Request

Connections

 

Toad no longer displays an error when you attempt to browse the list of servers in the Create New Connection window.

CR#207091

Case#490520

When connected to a database, Toad now disconnects the current connection before starting, stopping, or pausing the database service for that connection. 

CR#215675
 

Data Grid

 

You can now view the full contents of a cell by clicking the arrow beside the cell. Previously, cell contents were truncated after 200 characters.

CR#193198

Case#464540

After grouping a column in the data grid, pressing CTRL+C to copy a row no longer results in an error.

CR#194958

Case#468517

Database Browser/ Obj Palette

Attempting to connect to a database with a name longer than 32 characters no longer results in an error.

CR#178372

Agent

Attempting to view the error log in SQL Agent Properties on SQL Server 2005 no longer results in an error.

CR#167581

Agent - Jobs

An error no longer occurs when you alter a job, select the Alerts page, then select an alert and click Delete

CR#217177

Databases

 

You can now take a database offline if you previously attempted to alter the database and canceled the alteration in the current session.

CR#217297

You can now copy or move a database using the Copy/Move Wizard without having to install the .NET Framework 1.1.

CR#216408

Users

An error no longer occurs when creating a user with extended properties.

CR#217159

Diff Viewer

When sending a table to the Diff Viewer from the Database Browser/Object Palette, you are now select whether to send the table or the data for that table. 

N/A

Editor

Verify SQL now executes the statement against database selected in the Editor toolbar.

CR#218351

Export Data

 

Toad no longer prompts for bind variable values when exporting string literals that contain a backslash followed by a question mark.

CR#219004

Case#484142

Toad now inserts the correct rtf value for NTEXT data types when you generate INSERT statements from the right-click menu.

CR#204159

Case#484142

The One-Click Export feature now supports the following options:

  • Excel Linked Query with pivot table

  • Excel Linked Query at active cell with pivot table

CR#214846

Schema Compare

Objects with differences in body text formatting (whitespace or gap line) display as different even though the objects are the same.

CR#214606

Case#519931

Schema Report

You can now use links to navigate a Schema Report saved as an HTML file outside of Toad by selecting the checkbox for the sqlserver:// (URL scheme protocal sqlserver extension in Tools | Options | Environment | Extensions.

CR#211323

Case#511955

 

Resolved Issues and Enhancements in 3.0

Feature

Resolved Issue

Change Request

General

Customized keyboard shortcuts are now assigned correctly (Tools | Options | Environment | Keyboard).

CR#188620

Code Snippets

When creating a new snippets folder, an error no longer occurs if you do not rename the folder.

CR#164885

Connections

When creating a new connection, the Display Name field is now editable by default.

CR#192389

You can now specify the amount of time to wait before a connection attempt times-out under Tools | Options | Database | Timeouts.

CR#206962

If the status bar is hidden, attempting to connect to a database using Toad no longer results in an error.

CR#189787

Data Grid

An error no longer displays if you press CTRL+C or CTRL+A after grouping a column in the grid.

CR#194958

Currently, the Sum and Average mathematical functions cannot be applied to a column.

CR#217319

Database Browser/ Object Palette

You can now generate a creation script for most objects from the right-click menu (Send To | Editor as Script) or the Script tab in the Database Browser.

CR#155222

CR#155224

You can send the SQL script generated when creating, altering, or dropping an object in an object editor to the SQL Editor for execution.

CR#162373

You can now generate an SQL script for altering views, stored procedures, and UDFs by right-clicking an object and selecting Generate SQL | To location | Alter Script.

CR#201033

For most objects, you can only open one object editor at a time.

CR#186004

Tables

When adding a column with a uniqueidentifier as the data type, and setting IS RowGUID to TRUE, newid() is no longer quoted in the generated script.

CR#192388

When adding a column, you can now specify precision, scale, and length values in the parenthesis for the Type column in the Table Column List.

CR#194767

Occasionally, the focus in the Table Column List changes to the previous row; and you may change properties for the previous row rather than the current one.

CR#194772

Tables that have the same name as a keyword, such as CASE or GROUP no longer display an error when browsing data from the Data tab. 

CR#195851

You can now unbind a column from a rule when the table owner is not "dbo."

CR#142201

Indexes with Included Columns are now supported

CR#200635

Setting a data filter for multiple tables, and then selecting the data tab on those tables repeatedly no longer results in an error.

CR#192550

Programmability -UDDTs

CLR user-defined data types are now supported.

CR#171053s

Databases

(Database Browser Only) The correct database size now displays in the Properties tab.

CR#179229

Activity

You can now view a complete list of processes; and can sort, filter, or group those processes under the Activity category. You can also view the Last T-SQL Command Batch and any locks from this category.

CR#180355

Debugger

In SQL Server 2000, if the code contains a blank line or comment before the CREATE PROCEDURE block, the Debugger now indicates breakpoints correctly.

CR#216036

Editor

Loading a script in some environments no longer results in an argument was out of range error.

CR#188451

CR#194961

Using the shortcut key (CTRL+SHIFT+MINUS) to uncomment a comment line no longer results in an error.

CR#192545

If you copy data to the clipboard and then paste it into the editor, a blank line is added after each line.

CR#193046

Formatting 100+ lines of code that have been copied and pasted into the Editor no longer causes Toad to hang.

CR#194963

You can now use the same parameter name more than once for multiple tables in a query.

CR#163853

You can now query tables that contain decimal data types with a precision or 29 or greater.

CR#195496

Dragging-and-dropping objects from the Database Browser/Object Palette into an editor window now places the objects in the order they were selected.

CR#211702

ER Diagrammer

You can now save ER diagrams without causing an error.

CR#195495

Export Data

When exporting data that contains more rows than set to fetch initially (default is 1000 rows), you are now prompted to read all rows before exporting.

CR#189392

Filtered data is now exported correctly.

CR#193542

When exporting data as INSERT statements, the name you specify in the Object field under Script Options now persists.

CR#192874

Import Data

When importing data, Toad now verifies that the end of a field is followed by a delimiter, a carriage return or linefeed, or an end of file.

CR#197128

When importing data, the wizard now defaults to the current database.

CR#210436

Log Reader

You can now read more than one log file at a time.

CR#206238

When reading the online transaction log, clicking Refresh no longer results in an error.

CR#189933

If a database was backed up with the Overwrite option set to Append to media, the Log Reader can now read any appended changes.

CR#192659

When filtering entries using the Show only selected option, clicking Clear now clears all selected entries.

CR#203097

Master Detail Browser

You can now specify an alias for a table or view by double-clicking the name of the table/view in the Diagram panel at the top of the window.

CR#203102

Options

An unauthorized access error no longer displays when using the Search feature on Options pages (Tools | Options).

CR#211202

Query Builder
(SQL Modeler)

The drop-down menu in the Form tab of the Where Condition window now includes "IS NULL" and "IS NOT NULL".

CR#185054

Schema Compare

Users with different names that share the same login are now synchronized correctly.

CR#103387

Schema Reports

When generating a report, an error no longer occurs if “Include Properties” is selected in the Default Settings panel.

CR#186238

SQL Tuning

For a list of resolved issues and enhancements, see the SQL Tuning release notes.
 

N/A


Known Issues

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

Feature

Known Issue

Change Request

General

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

CR#216699

Installation/ Upgrades

If a power user upgrades Toad, installation "Error 1406. Could not write value DisplayIcon to key..." displays. This issue occurs because the user does not have enough privileges to update the DisplayIcon entry in registry. You can safely Ignore this error; however, an incorrect icon may display for Toad in the Add/Remove Programs window.

CR#222728

Connections

If you are connecting to a local database, using "(local), <port #>" in the Server name field results in an error.

Workaround:
Use one of the following methods for the server name:

"localhost"

"localhost, <port #>"

"., <port #>"

CR0218603

Data Compare

Quest recommends limiting compares to 20000 rows in tables. When using Data Compare on large databases, Quest recommends excluding tables with large data sets from the comparison

CR#142208

You can compare views, but you cannot synchronize them.

CR#166497

Data Grid

When adding data to a column that has an Identity Increment value, Toad cannot determine the increment value on the client side and an error occurs if you do not enter a value for the column.

Workaround:
Enter any valid value in the identity column, and then press F5 to query the server for the correct value. This replaces the placeholder value you entered with the correctly incremented one.

CR#117786

Data Reports

Currently, you cannot create a Label Report in the Toad Data Report wizard.

CR#215945

Database Browser/ Object Palette

(Database Browser only) The Deps (Uses) & Deps (Used by) tabs display as empty if an extended stored procedure is used.  

CR#117189

Tables

If you alter a table and rename a Primary Key column that is referenced by a Foreign Key, the Foreign Key still references the original column name.

Workaround:
Manually update the column name for the Foreign Key in the SQL Script page of the Alter Table window.

CR#212357

If an existing table includes a column with a bind default, attempting to use Create Like to create a table on a database that does not already include the default results in an incorrect script being generated.

Workaround:
Manually edit the script on the SQL Script page before clicking OK.

CR#215934

(Database Browser only) You cannot unbind a column from a rule using the Unbind Column from Rule toolbar button.

Workaround:

  1. Alter the table.

  2. Select the bound column in the Columns page

  3. Remove the bound rule from the Rule Binding field.

CR#216532

Databases

When generating a DDL script for databases, the following objects are not included in the script:

  • Application roles

  • Schemas

  • Synonyms

CR#216490

Currently, you cannot drop a database if you are connected to it.

CR#211896

After backing up a database, you must press F5 to update the icon/status.

CR#213716

(Database Browser only) You cannot drop a database if you:

  • First select any tab in the right-hand side of the Database Browser other than the Properties tab, and then attempt to drop that database.

  • Click Cancel while altering the database, and then attempt to drop that database. 

Workaround:
Disconnect and then reconnect your connection and drop the database.

CR#211896

Debugger

You cannot debug stored procedures with the following input parameters in this release:

  • Binary

  • Varbinary

  • Bit

  • Timestamp

  • Image

CR#133602

CR#133634

CR#133636

In some environments, the result set returned by a stored procedure called by another stored procedure is inserted into a table; however the table definition has varchar columns that are not long enough. This results in an error message stating, "String or binary data would be truncated" and data is not inserted into the temporary table.

Workaround:
Increase the size of the varchar columns in the temporary table.

CR#211704

Editor

The following object types are not found when using the View Object at Cursor (F4) feature:

  • Triggers

  • Procedures

  • Functions

  • Users

  • Hosts

CR#164917

Export Wizard/ One Click Export

Binary data types cannot be exported in this release.

CR#170430

When exporting large results sets (approximately 500K), you may run out of memory before the operation completes.

Workaround:
Create a view for the query and export using that view.

CR#203483

Exporting more than 65,536 rows to an Excel 2007 instance causes an error.

Note: This issue does not affect Excel 2000 or 2003.

CR#211832

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.

CR#221667

Currently, selecting more than one file to import causes Toad to hang.

Workaround:

Import each file individually.  

CR0220341

Log Reader

Sometimes when installing Log Reader Server Components to a remote host, a "Write to file failed" error occurs.

Workaround:

  1. Locate xp_QuestLogReader.dll on the host where the application is installed.

  2. Copy xp_QuestLogReader.dll to the \BIN folder of the SQL Server instance where you want to install the components.

    You can use the EXEC xp_instance_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Microsoft\ MSSQLServer\Setup', N'SQLPath' command to define your server location.

  3. Execute the following commands on the SQL Server instance:

EXEC sp_addextendedproc 'xp_qlr_version', 'xp_QuestLogReader.dll'
 

EXEC sp_addextendedproc 'xp_qlr_logfile', 'xp_QuestLogReader.dll'

EXEC sp_addextendedproc 'xp_qlr_loginfo', 'xp_QuestLogReader.dll'

EXEC sp_addextendedproc 'xp_qlr_logread', 'xp_QuestLogReader.dll'

CR#216499

Schema Compare

Default constraints, check constraints, foreign keys, and case differences display in schema compares even though you select options to ignore them on the Compare Options page (Tools | Options | Schema Compare | SQL Server | Compare).

CR#215192

CR#212297

CR#212301

Schema Report

On SQL Server 2005 only, generating a Schema Report when the Include System Objects and Include Source options are selected results in an error.

CR#223188

Server Compare

When running MSDE 2000, attempting to retrieve information from DTS Packages may result in a "General Repository Error: 80041035."

CR#142205

If the target server is configured with Use Windows NT Fibers, you cannot synchronize Meta Data Service Packages.

CR#142206

If the Meta Data Service DTS Packages contain a COM object that is not registered on the target server, you may receive an exception error during synchronization.

CR#142207

Currently, you cannot rollback Meta Data Service DTS Packages.

CR#122712

SQL Tuning

For a list of known issues, see the SQL Tuning release notes.

N/A

Version Control

Toad is providing a more in-depth integration with popular VCS vendors. Currently, Toad has integrated version control with Visual Source Safe. If you are using CVS or SCC as the provider from the previous release of Toad, you currently cannot use those providers in Toad at this time. Also, you may not want to migrate settings to the current release.

N/A

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

CR#214601

 


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

Change Request

Data Compare

 

Currently, the synchronization script for each table displays using the SyntaxEditor component. This component has a storage limit of 5 MB, and should be disabled for large scripts.

CR#142210

Export Data

In order 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

 


Upgrade and Compatibility

For information about upgrading refer to the Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server install_type 3.1  | Documentation.
 


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

Memory

512 MB of RAM minimum, 768 MB 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 130 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 2000

Windows 2003

Windows XP Professional (32-bit or x64)

Windows Vista (32-bit; Ultimate edition with XP Graphics has been tested)

Note: SQL Tuning is not supported on Windows Vista (any edition).

Additional Software

.NET Framework
Microsoft .NET Framework 2.0 or 3.0

Notes: Consider the following:

  • In order to run Toad, the .NET security policy must be set to unrestricted. For more information, see User Privilege Requirements.
  • In order to use the Automation feature, the .NET Framework 3.0 must be installed.

(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 5.0 or later (for viewing the Toad for SQL Server Getting Started Guide)


Microsoft SQL-DMO 8.0
This component is included if client connectivity is installed.

Server Requirements

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

Operating System

Windows 2000 Server with SP4 or later

Windows 2000 Professional Edition with SP4 or later

Windows XP (32-bit with SP2 or later; x64)

Windows 2003 Server (32-bit or x64 with SP1 or later)

Windows Vista (32-bit; Ultimate edition with XP Graphics has been tested)


Note: Log Reader server components can now be installed on x64 servers and Windows Vista in Preview mode. Features that are in Preview Mode have not received the same level of testing as features that have been released commercially, and are not supported until a commercial version is available.

Supported Databases

Microsoft SQL Server 2000 with SP3, 2005 with SP2


Note: SQL Server Compact Edition is not supported.

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.

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server Service Pack 2 using the Metaframe Access Suite 3.0 and Citrix Presentation Server Clients 10.0. For information about installing Toad in a Citrix environment, see Citrix Installation.
 

Silent Install Requirements

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

         Microsoft .NET Framework 2.0 or later

         Microsoft SQL-DMO

For information about installing Toad silently, see Install Toad Silently in the Toad for SQL Server Getting Started 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.
 

SQL Server 2005 Prerequisites

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

  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 client machine, install the SQL Server 2005 Workstation Component option of the SQL Server 2005 installation.
  2. Copy and register the ssdebugps.dll (debugging host component) on both the client and server. This file is located by default in the following directory on the server where SQL Server 2005 is installed:

C:\Program Files\ Common Files\Microsoft Shared\SQL Debugging

To register this file, open a command prompt and enter the following command: regsrv32 ssdebugps.dll

Note: If you are unable to locate this file, you can run the remote debugging setup component (rdbgsetup.exe). This file is located by default in the following directory on the server where SQL Server 2005 is installed: C:\Program Files\Microsoft SQL Server\90\Shared\1033

  1. Make sure the following permissions are set:

sp_addsrvrolemember 'Domain\Name', 'sysadmin'

where Domain\Name is your Windows login

  1. In Toad, commit or rollback the connection 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 2005 Platforms Tested for Debugging Support

Client

Server

2003 EE

2003 EE (SP1)

2000
(SP4)

2000 Pro (SP4)

XP Pro

XP Pro (SP2)

Vista Pro

2003 EE

—

—

— — —

—

—

2003 EE (SP1)

—

X

X

X

—

X

—

2000
(SP4)

—

X

X

X

—

X

—

2000 Pro
(SP4)

—

X

X

X

—

X

—

XP Pro

—

—

—

—

—

—

—

XP Pro (SP2)

—

X

X

X

—

X

—
Vista Pro — — — — — — X

SQL Server 2000 (SP4) Platforms Tested for Debugging Support

Client

Server

2003 EE

2003 EE (SP1)

2000
(SP4)

2000 Pro (SP4)

XP Pro

XP Pro (SP2)

Vista Pro

2003 EE

X

—

— — —

—

—

2003 EE (SP1)

—

X

—

—

—

—

—

2000
(SP4)

—

—

X

—

—

—

—

2000 Pro
(SP4)

X

X

X

X

X

X

—

XP Pro

X

X

X

X

X

X

—

XP Pro (SP2)

X

X

X

—

—

X
(Local server)

—
Vista Pro — — — — — — —

SQL Server 2000 (SP3) Platforms Tested for Debugging Support

Client

Server

2003 EE

2003 EE (SP1)

2000
(SP4)

2000 Pro (SP4)

XP Pro

XP Pro (SP2)

Vista Pro

2003 EE

X

—

— — —

—

—

2003 EE (SP1)

—

X

—

—

—

—

—

2000
(SP4)

—

—

X

—

—

—

—

2000 Pro
(SP4)

X

X

X

X

—

—

—

XP Pro

X

X

X

X

X

—

—

XP Pro (SP2)

—

—

—

—

—

X
(Local server)

—
Vista Pro — — — — — — —

SQL Server 2000 (SP3a) Platforms Tested for Debugging Support

Client

Server

2003 EE

2003 EE (SP1)

2000
(SP4)

2000 Pro (SP4)

XP Pro

XP Pro (SP2)

Vista Pro

2003 EE

—

—

— — —

—

—

2003 EE (SP1)

—

X

—

—

—

—

—

2000
(SP4)

—

—

X

—

—

—

—

2000 Pro
(SP4)

X

X

X

X

—

—

—

XP Pro

—

—

—

—

—

—

—

XP Pro (SP2)

—

—

—

—

—

—

—
Vista Pro — — — — — — —

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:


Getting Started

Contents of the Release Package

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

Installation Instructions

For general installation information, refer to the Getting Started Guide available
from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server install_type 3.1 | Documentation.

 

Citrix Installation

To install Toad on a Citrix system

  1. Connect to the Citrix Environment as an administrator.

  2. Copy Toad to the Citrix server, if required.

  3. Install Toad.

  4. During installation, select the Anyone who uses this computer checkbox when prompted.

  5. Repeat steps 2 through 4 for each server in the Citrix farm.

Note: Although you must install Toad on every server in the Citrix farm, you only need to publish Toad once.

  1. Review the following considerations regarding licensing. A license supplied by an administrator always overrides a user-supplied license in a Citrix environment.


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

http://www.quest.com

Refer to 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.

 


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.

 

ฉ 2007 Quest Software, Inc. ALL RIGHTS RESERVED.

 

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, 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.

 

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
Email: legal@quest.com

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.