Toad® for SQL Server
Version 4.5.0
Release Notes
August 27, 2009
|
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.
Review the following sections for updates in this release and new features:
Toad now requires .NET Framework 3.5 (Service Pack 1) or later. You can download the latest .NET Framework at: http://www.microsoft.com/Net/Download.aspx
Document recovery now works with any ER Diagram or Query Builder files to avoid losing your work. When you restart Toad after an unexpected close, Toad checks the timestamp on the backup file against the original file, and opens the file that has the latest timestamp. The document recovery option is located in Tools | Options | Environment | General.
Connection information for each Editor, Query Builder, or other document window is now available by selecting the Show connection info on document tabs checkbox under Tools | Options | Environment | General.
You can close the current tab in a window or all other tabs except the current one from the right-click context menu available on each Editor tab.
You can use the new File Transfer Protocol (FTP) utility to transfer scripts, reports, or other files to and from an FTP server. Toad supports unsecured (FTP) and secure (SFTP) file transfers. To open this utility, select View | FTP Connections from the menu.
Right-click one or more files in the local or remote directory to upload, download, delete, or rename the files.
You can also add an FTP connection in the Project Manager or as an activity in an Automation script.
Most activities now include support for variables. Variables allow you to change data in your script or use a dataset collected from an activity in the automation script. For example, you can use variables to perform the following tasks:
Find content in a file and replace it with the value of a variable
See "Use Variables in Automation" in the Toad help for more information.
Support for Find and Replace and FTP file activities.
Support for new system activities, including running programs, setting variables, if conditions, while, and loop datasets.
The Select to File activity now supports Excel options.
General
Toad now includes a library of 45 Code Snippets designed to help DBAs better understand SQL activity, retrieve server, database, and object information, and perform administration functions like determining fragmentation, estimating data compression savings, and managing traces. You can execute these DBA queries from the DBA Queries folder in the Code Snippets window or search for them using the DBA or DMV keywords.
Object Explorer
You can start or stop the SQL Server agent by right-clicking the agent node in the Object Explorer.
Stored procedures and functions can now be altered in the Editor by right-clicking the object and selecting Alter <object> in Editor in the Object Explorer.
Index details are now available from the Indexes tab in the Object Viewer pane.
You can now partition tables and indexes. For tables, you can also create a Sliding Window scenario.
The Log Reader component can now be accessed by right-clicking a database in the Object Explorer and selecting Log Reader.
Master Detail Browser
When sending tables or views to the Master Detail Browser, Toad now automatically selects all columns.
General
Toad is now Federal Desktop Core Configuration (FDCC) Compliant; however changes to the architecture to ensure compliance will result in a loss of existing data filters when upgrading to this release.
You can now create pivot grids and charts directly from the results by selecting the Pivot & Chart tab.
You can now format XML data.
You can add a total value to a column of data or can add a subtotal value to grouped data if the Summary Footer Panel is displayed (right-click the data and select Show | Summary Footer Panel). To add a total value, right-click the data and select one of the options.
If you have grouped columns using the Grouping panel (right-click and select Show | Grouping Panel), you can add a subtotal value to grouped records.
Export Wizard
You can now export data to Microsoft Access files.
You can now create a new table within a database when exporting data.
Data Compare
You can right-click tables or views in the Object Explorer and select Compare Data to compare data within the context of the current connection and database.
When comparing data, you can now auto-map target columns for selected source tables.
When selecting a record, Data Compare automatically displays a side-by-side comparison of the values of the source and target row in the Row Viewer tab.
When synchronizing a script, Data Compare now opens a script in Toad using an existing connection.
Query Builder
You can now sort columns alphabetically in the Diagram pane by selecting an option from the Sort columns in diagram by name drop-down list in Tools | Options | Database | Query Builder.
You can now create a view in the Query Builder.
When saving a Query Builder file, Toad prompts you to save query results with that file.
You can now add a UNIONor UNION ALL operator to queries.
You can compare results from a Query Builder query to data from the Data tab or Editor results using the right-click menu.
Editor
If Quest SQL Optimizer is installed, you can open it from the Editor context menu.
(SQL Server 2005 and 2008) You can now open the Microsoft Database Engine Tuning Advisor from the Editor context menu.
Toad now includes four pre-defined SQL Formats. You can select a pre-defined format or create your own custom formats from Tools | Options | Editor | Formatter.
You can share Formatter settings for your team in a network share folder in Tools | Options | Editor | Formatter to ensure consistent coding standards.
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
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.
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 |
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 |
|
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 |
Debugger |
You can now debug stored procedures with the following input parameters:
|
ST#41538 ST#41539 ST#41540 |
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 |
|
During a debugging session, opening a new Editor window no longer results in an error. |
ST#64703 |
|
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 |
|
Code Completion:
|
ST#59056 ST#46871 ST#63366 ST#61989 ST#53700 |
|
ER Diagram | Setting the maximum objects to a value greater than the default value now correctly applies the setting. |
ST#58479 |
Execution Plan | Generating an estimated execution plan in some instances where a statement includes stored procedures no longer results in an error. |
ST#42562 ST#41981 |
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 |
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 |
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 ST#63234 |
|
A Securables tab now displays in the Object Details pane for Users, Server Roles, and Logins. |
ST#53706 |
|
Tables:
|
ST#52682 ST#58387 ST#50463 ST#43559 |
|
Databases:
|
ST#51164 ST#60398 ST#57078 |
|
Jobs: Jobs now use a different icon to indicate whether the job is enabled, disabled, or failed on last execution. |
ST#57772 |
|
Stored Procedures:
|
ST#44201 ST#56440 ST#53985 ST#54033 |
|
Maintenance Plans:
|
ST#52721 ST#57721 |
|
Project Manager | You can now add the "Add to Project Manager" button to a toolbar. |
ST#57280 |
Query Builder |
Update and Delete statements now include the Where clause in the Generated Query tabs. |
ST#44655 |
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 |
|
Version Control |
(TFS) The following issues have been resolved:
|
ST#55362 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 |
|
(Subversion) Toad has been tested with the CollabNet Subversion Command-Line Client 1.5.6 Notes:
See "Configure Subversion Version Control" in the Toad help for more information. |
ST#56045 ST#55937 |
|
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 |
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:
|
ST#42154 |
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:
|
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:
With User Account Control (UAC) disabled
If you install Toad as an administrator and:
|
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 |
ST#41665 |
Limitations when exporting 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:
|
CR#65049 |
Import Wizard |
Currently, you cannot import Excel 2007 files because they are saved using an xlsx format. Workaround:
|
ST#42416 |
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:
|
ST#55294 |
Tables: Currently, you cannot perform an extended alter on a table with a FileStream column. This includes the following actions:
|
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:
|
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 |
|
Version control does not support CLR objects. | ST#52089 |
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 2007 PIAs |
CR#138239 |
Before installing Toad for SQL Server, ensure your client system meets the following minimum hardware and software requirements:
Platform |
|
Hard Disk Space |
|
Memory |
512 MB of RAM minimum, 1 GB recommended Note: The memory required may vary based on the following:
|
Operating System |
Windows Server 2003 (32-bit or 64-bit) Windows XP Professional (32-bit or 64-bit) Windows Vista Windows Server 2008 Windows 7
|
Additional Requirements |
.NET Framework Microsoft .NET Framework 3.5 (Service Pack 1) Notes:
Web Browser Microsoft Internet Explorer 6.0 or later PDF Viewer
(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. |
Before installing Toad for SQL Server, ensure your server meets the following minimum hardware and software requirements:
Operating System |
|
Database |
|
Additional Requirements |
.NET Framework
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. |
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.
The following user privileges are required for installing and running Toad for SQL Server:
If a Power user installs Toad, a Restricted user can run the application but cannot
Associate file extensions.
See the Toad shortcut icon on the desktop or the Toad menu option in the Windows Start menu. As a workaround, Restricted users can create a shortcut to the application and place it on their desktop from the install directory.
- From the Windows Start menu, select Settings | Control Panel.
- Double-click Administrative Tools.
- Double-click Microsoft .NET Framework 2.0Configuration.
- 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.
- Click Evaluate Assembly from the list of tasks in the right panel. An Evaluate an Assembly window displays.
- Browse to the location of Toad.exe in the File field.
- Click Next to view permissions for Toad.exe.
- Set the permission to Unrestricted.
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.
Verify the following general requirements to ensure that the Debugger operates properly for all SQL Server installations:
Check your security policy because it may include an access lock to the remote server.
Note: The security policy can be applied to the domain or local computer.
Note: Currently, you cannot debug SQL/CLR code.
To debug locally, perform the following on the Toad client
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.
To debug remotely, perform the following
Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
sp_addsrvrolemember 'Domain\Name', 'sysadmin'
where Domain\Name is your Windows login.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.
To debug locally, perform the following on the Toad client:
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.
To debug remotely, perform the following:
On the Toad client, do one of the following:
Install the SQL Server 2005 Workstation Components option of the SQL Server 2005 installation.
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: regsvr32 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
Make sure the following permissions are set:
Your Windows account that Toad is running under must be a member of sysadmin server role in the SQL Server being debugged.
Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
To create a Server login from your Windows login and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
sp_addsrvrolemember 'Domain\Name', 'sysadmin'
where Domain\Name is your Windows login
Note: By default, Windows administrators on a machine running SQL Server are SQL Server sysadmins on that machine.
To debug locally, perform the following on the Toad client:
Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed.
If autocommit is disabled, commit or rollback the connection in Toad before starting the debugging session.
To debug remotely, perform the following:
On the Toad client, do one of the following:
Make sure that SQL Server 2000 with Service Pack 3 or Service Pack 4 is installed.
Copy and register the sqldbg.dll and sqldbreg2.exe (debugging host components) on both the Toad client and server. These files are located by default in the following directory on the server where SQL Server 2000 is installed:
C:\Program Files\Common Files\Microsoft Shared\SQL Debugging
To register these files, open a command prompt and enter the following commands:
regsvr32 sqldbg.dll
sqldbreg2.exe /RegServer
Note: The Remote Procedure Call (RPC) service should be started on both the Toad client and server.
Your server login must also be a member of the sysadmin role. This login can be your Windows user account (Windows authentication), or a SQL Server login (SQL Server authentication).
To create a server login from your Windows account and add it to the sysadmin role, a user who already has sysadmin privileges must execute the following:
sp_addsrvrolemember 'Domain\Name', 'sysadmin'
where Domain\Name is your Windows login.
DCOM Access permissions must be granted for the system account and the group or user who needs access.
To verify permissions:
Note: By default, Windows administrators on a computer running SQL Server are SQL Server sysadmins on that computer.
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 |
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.
The Toad for SQL Server release package contains the following products:
For general installation information, see the Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for SQL Server | Documentation.
|
|
|
Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
Web site |
See our web site for regional and international office information.
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.
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.
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.