Toad^® for IBM^® DB2^®

Beta Version 4.0.0.688

Beta Release Notes

June 24 2008

Contents

Welcome to Toad for DB2

Toad for DB2 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 DB2 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.

Back to Top

New v4.0 Functionality

Areas to focus on in this beta drop:

We have introduced the beta of the new optional Quest SQL Optimizer for DB2 LUW 3.0 Beta that is integrated with Toad.
If you have this new component installed you can launch it from a Toad DB2 SQL Editor session to perform advanced statement tuning.

Note that the Quest SQL Optimizer for DB2 LUW 3.0 Beta is available for use during this beta and will available in the Toad for DB2 LUW Xpert edition upon Toad DB2 4.0 General Availability. To download the installation for this component see the Quest SQL Optimizer for DB2 LUW page.

Under Construction

Some features that we are updating are still being developed and tested. See Known Issues for more information.
Thank you for your feedback!

Migration Wizard

The Migration Wizard remains under development.

Migration Wizard Known issues:
Toad does not include some referenced/dependent objects (CR51027).
Toad throws an exception in Migration if the user defines a schema transformation rule, then attempts to define any other transformation rule. A work around would be to define your schema transformation last (CR51222).

If you find any other issues please report those to the beta board. Thank you for your patience.

From Previous drops:

We have introduced the beta of the new optional Toad SQL Tuning for DB2 z/OS component that is integrated with Toad.
If you have this new component installed you can launch it from a Toad DB2 SQL Editor session to perform advanced statement tuning.

Note that the Toad SQL Tuning for DB2 z/OS component is available for use during this beta and will available in the Toad for DB2 z/OS Xpert edition upon Toad DB2 4.0 General Availability. To download the installation for this component see the Toad SQL Tuning for DB2 z/OS page.

DB2 on Linux, UNIX and Windows and DB2 on z/OS

Run script from cursor

We have introduced a new SQL Editor Toolbar button "Execute From Cursor" .

This button will execute the statements in the script from the cursor position through the end of the script.
This buttons is helpful when you need to restart a script from a certain location.  We have decided to not show this button by default to reduce the clutter of our Toolbars.  You may add this button as shown below:

Migration Wizard Changes

To improve the flow of the wizard, in this drop we moved the options to migrate referenced objects and dependent objects from the Filter page onto the Customize Migration page.  We also reorganized the Customize Migration page and have grouped options into more meaningful sections.

Performance Enhancements

In this drop we have made performance improvements in the following areas:

- Database browser
    - We made changes to how we fetch and format data that appears on both the left-hand side and the right-hand side of the browser

- Alter scripts
    - We made changes in the SQL we execute and in our processing to reduce the time it takes to generate scripts for when altering objects   (for native alter statements as well as for Advanced Alters - which require a drop and re-create of objects)

- Migration Wizard
    - We made changes in the Migration wizard in the SQL we execute and in our processing to reduce the time it takes to generate dependency lists and migration scripts

- Schema Compare
    - We made changes in the Schema Compare feature in the SQL we execute and in our processing to reduce the time it takes to identify differences and generate sync scripts
 

We welcome feedback on these features and are anxious to hear about the performance of these features at your site.

For DB2 on z/OS subsystems:
Note that we are still in the process of testing these changes and reviewing our list of recommended indexes to ensure they are leveraged with our recent changes.  For the time being, please continue to use the list of recommended DB2 z/OS indexes below.

DB2 on z/OS Command Snippets

We now have added DB2 z/OS command snippets to allow you to easily generate and execute those commands within an editor.

The execution of DB2 z/OS commands require the z/OS Components to be installed - please refer to that section in the release notes for additional information here.

DB2 on Linux, UNIX and Windows

Space Calculator Feature

The Space Calculator feature lets you test hypothetical object additions, deletions, or object-size changes to determine their impact on space usage in a DB2 for LUW tablespace. Space Calculator also provides options to run maintenance utilities on objects or to generate scripts that put into effect your space-usage scenarios.

Access Space Calculator from the Database Explorer or Object Explorer or from an object list.

To access Space Calculator from the Database Explorer or Object Explorer

1. In the Database Explorer or Object Explorer, select the Tablespaces, Tables, or Indexes tab.

2. Select the objects that you want to involve in making hypothetical space adjustments.

3. Right-click and select Space Management | Calculate Space.

To access the report from an object list

1. In the Database Explorer or Object Explorer, select the Object Lists tab.

2. Select the object list.

3. Within the object list, select either the tablespaces, the tables, or the indexes you want to involve in making hypothetical adjustments.

4. Right-click and select Tablespace (or Table or Index) | Space Management | Calculate Space.

The Space Calculator window opens, showing a list of the tablespaces you selected or the tablespaces to which the objects you selected belong.

The Space Calculator window initially shows space-related information (gathered from the system catalog) for each tablespace you selected, for each container that makes up a given tablespace, and for each table or index in the tablespace. As you hypothetically adjust space requirements at the container or object level, Space Calculator keeps track of how your changes affect the tablespace.

You can group by any column by dragging the column name to the area above the list as shown below.

You can hypothetically adjust space values by entering the new values in the grid or by clicking the button:

When you click the button you can enter space information and then click 'Apply':

The graphs are updated to reflect your hypothetical space changes:

You can use the buttons at the bottom of the lower left area to remove hypothetical objects, show additional columns, reset the selected objects or reload object definitions from the catalog:

Additionally, right-click menus enable you to perform maintenance procedures—such as altering a tablespace or executing REORG or RUNSTATS on one or more objects:

Support for DB2 V9.5 Array Type

You can now create, create like, alter and drop DB2 LUW V9.5 Array types.  You can invoke these actions and others from the 'Distinct Type' tab on the  database browser:

To specify an 'Array' type, select the 'Array' value in the 'Type' drop-down list in the object editor dialog. Specify the array length in the properties section of this dialog:

DB2 on Linux, UNIX and Windows and z/OS Performance fixes

For this drop we changed how we format the results from catalog queries when populating object lists in the Database Browser.  You should see that the objects listed in the Database Browser (like Tables, Tablespaces, Indexes, etc.) are displayed faster now compared to previous 4.0 beta drops.

DB2 on Linux, UNIX and Windows

Analyze Table Partitions Feature

The Table Partition Analysis tool helps you determine how best to redistribute the data among the current data partitions in a table. Using this tool, you set up data distribution scenarios. Table Partition Analysis then calculates the number of table rows that DB2 would store in each partition for the current scenario and shows a graphical depiction of this data distribution. Once you determine the best scenario for redistributing the data, you can have Table Partition Analysis generate the script that alters the data partitions using the scenario values and redistributes the table data accordingly.

To invoke this new feature right click on a data partitioned table and select Space Management...Analyze Table Partitions:

Upon entry to this feature you can click on the 'Refresh Graph' button to display a graphical representation of the table's data distribution:

You may edit the partition ranges and then click on the 'Refresh Graph' button to see the new data distribution.  You can then click on the 'Show Script' button to generate an 'Alter' script to implement your changes:

Space Usage Feature

For LUW tablespaces there now is a 'Space Usage' tab on the right hand side in the database browser.

Use this tab to easily obtain and view space information for the tablespace, its containers, and the tables and indexes in the space.

From Previous drops:

DB2 on Linux, UNIX and Windows

New multiple object Table and Tablespace editors

Now you can conveniently alter some common LUW Table and Tablespace properties using one editor. As of this Beta release when you multi-select these objects and choose 'Alter' a new multiple object editor will be launched. 

New option to rebuild Indexes, Triggers and Views

Now you can easily recreate selected LUW Indexes, Triggers, and Views with a single right-click 'Rebuild' action.

Common DB2 Changes (for both LUW and z/OS)

Previewed extended object alter scripts are now sent to the SQL Editor for execution

When performing an alter that requires a drop and recreate of the DB2 object the resulting script is no longer able to be executed from the object editor when the 'Preview script' option is in effect. With this option set the script may only be sent to the SQL Editor for execution. The SQL Editor provides greater flexibility and ease of execution.

DB2 on Linux, UNIX and Windows

Stored Procedure enhancements

Now you can easily Create, Create Like and Alter LUW Stored Procedures. Those actions are available via a right-click menu and invoke object editors to make creating and altering Stored Procedures an easy task.

Edit Catalog Statistics

Now you can easily update catalog statistics for Tables and indexes. A new right-click menu item "Edit Catalog Statistics" has been added for LUW Tables.

This new features brings up an editor that allows you to edit table, column and index statistics.
You can easily save and reload statistics in the editor.  This feature allows you to easily simulate production statistics in a test environment.

New Space Exceptions feature

A new 'Space Exception' Report feature is available from the Tools Menu or via right-click menu Tables - Send To - Exception Report.

Objects from the 'Object Explorer' can also be dragged and dropped onto the 'Space Exception' tab.
 

The Space Exceptions feature allows you to easily identify objects that need to be reorganized or objects that do not have current statistics  in the catalog.  You can use the controls at the top of the Space Exceptions tab to easily view and check objects and fix objects with REORG or statistics issues. Correcting these issues will lead to better database performance.

When you click the above 'Reorg' button, the following screen displays and allows you to easily generate scripts.

The criteria used in identifying exceptions and warnings can be viewed and modified using the Tools - Options - Database - DB2 - LUW - Space Exceptions.

New Space Estimator feature

We are introducing a new 'Space Estimator' feature. When you are creating a tablespace, you can use the 'Space Estimator' tab and enter information about the tables or indexes that you plan on defining in the tablespace.  The estimated space usage is calculated and displayed. If you are creating a database managed tablespace and already have specified the containers, when you click on the 'Apply' button, the containers are sized to accommodate the anticipated space usage.

When the 'Apply' button is clicked, the Containers tab is shown with container sizes computed.

You can also estimate size using existing table definitions. Just click the '...' button.

The following window will display and allow you to select existing tables to be used in the space usage computation.

New Set Integrity support

Toad has added the ability to quickly generate 'Set Integrity' statements for Tables. Now you can select one or more tables, right-click and select Utilities - Set Integrity.

New Utilities tab

Toad has a new 'Utilities' tab where information about currently executing commands/utilities are displayed.

You can right-click on a utility and select 'Set Utility Impact' to easily modify the utility's priority.

Applications tab enhancements

We now include Dynamic SQL and SQL statement information on the Applications tab.

DB2 on z/OS

DB2 Command support

You can now execute DB2 on z/OS commands within the SQL Editor. (This requires that the Quest z/OS Components are installed for the DB2 z/OS subsystem).

Advanced Alters - Stop/Start tablespace

Advanced alter scripts now generate -STOP and -START tablespace commands (when necessary).

Common DB2 Changes (for both LUW and z/OS)

Constraints

Toad now shows constraints as objects in the Database Explorer and Object Explorer so you can now easily view properties and columns, view dependencies, or maintain constraints.

Objects details on right hand side

Toad has enhanced the Database Explorer right hand side view to show information on objects. When you click on a node group in the tree, a list that can be sorted and arranged is displayed on right hand side view. You can right click on those objects in the list and invoke actions on those

Compare Options save and re-load

Toad now allows you to save and re-load Schema compare options. The options can be modified, saved and re-loaded from the Tools - Options - Schema Compare - panel.

Migration Wizard  Changes

The migration wizard now has individual check boxes that can be selected to migrate objects that are referenced by the selected objects as well as dependent objects. (Stay tuned for additional migration wizard enhancements).

Visual Changes

We have renamed several features and regrouped features under different menus to improve the product's organization and to simplify use.

The 'Object Palette' has been renamed to 'Object Explorer'.

The 'Database Browser' has been renamed to 'Database Explorer'.

We have moved the Migration and Compare features from the Advanced Menu to now be under the Tools Compare Menu:

For this drop we are trying to reduce the number of toolbar buttons.  We changed the run script button (F5) to the below highlighted button:

Group Execute

Group execute is now a left docked tab within the SQL Editor.

Other Features Under construction

Other features are under construction and have not completed testing at the time of this drop.  As those features become solid, we will be highlighting and explaining them in subsequent beta drops.

Back to Top

Resolved Issues and Enhancements

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

Resolved Issues and Enhancements in Beta 4.0

Back to Top

Known Beta Issues

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

Back to Top

Third Party Known Issues

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

Back to Top

Upgrade and Compatibility

Please review upgrade information in the Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Back to Top

System Requirements

Verify that your system meets the minimum requirements described in the following sections:

• Client Requirements

• Server Requirements

• User Privilege Requirements

• Citrix Requirements

• LDAP Requirements

• Compile and Debug Requirements for Stored Procedures

• Requirements for Executing DB2 for z/OS Utilities

• Recommended Indexes to Improve Toad Performance in DB2 for z/OS

• Requirements for Object Migration

• Version Control Requirements

Client Requirements

Toad for DB2 client installation requires the following.

Note: If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing to avoid losing functionality is some DB2 native tools.

Server Requirements

Each DB2 database server requires the following:

User Privilege Requirements

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

• Only Power users and Administrators can install Toad.

Note: Power users cannot install Toad on a Windows Vista Enterprise machine. This Windows limitation is due to the fact that the Power User mode is no longer used in Vista and therefore cannot install applications.

• A Power User or Restricted User must belong to the DB2ADMNS or DB2USERS group. To add the user to one of these groups, select Start | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Groups | DB2ADMNS or DB2USERS.
• If a Power user installs Toad, a Restricted user can run the application but cannot do the following:

  • Associate file extensions.

  • See the Toad for DB2 icon on the desktop or the Toad for DB2 menu options in the Windows Start menu. As a workaround, Restricted users can create a shortcut to the application from the install directory and place the shortcut on their desktop.

• If an Administrator installs Toad, the Administrator can share the Toad for DB2 desktop icon and menu items with any user on the computer.
• Network and LAN installations are currently not supported.
• In order to use Toad with DB2 for z/OS, any user who does not have SYSADM privileges must be granted SELECT permissions on the DB2 catalog tables.
• In order to run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy:

  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 lists of tasks in the right panel. An Evaluate an Assemble 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.

• In order to set or modify Toad Security settings, users must have privileges to create the QuestSoftware.ToadSecurity table if it does not already exist. If the table does exist, users must have privileges to insert, update, and delete data in the table.
• Power users and Restricted users do not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, these users can use the Import Profile function to import catalog entries to Toad.
• To load log files on the Toad client machine for a Log Reader session, the user must have the following privileges:

  • READ permissions on the log files belonging to the database and on the directory where these files are stored

  • Database administrator privileges to read the database's log.

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, refer to Install Toad on a Citrix Machine in the Toad for DB2 Getting Started Guide.

LDAP Requirements

To connect to a Lightweight Directory Application Protocol (LDAP) server, you must enable LDAP support and specify the host name and port number of the LDAP server for the DB2 client installed with Toad.

Note: You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the machine is already configured to support LDAP.

To configure Toad to use LDAP

1. Open the Command Window for the DB2 client installed with Toad by selecting Start | All Programs | IBM DB2 | <ToadCom, ToadEval, or ToadFree> | Command Line Tools | Command Window.
2. Type the following command to enable LDAP support:

db2set DB2_ENABLE_LDAP=YES

3. Type the following command to specify the TCP/IP host name and port number of the LDAP server:

db2set DB2LDAPHOST=hostname[:port]

The port number defaults to 389 (default LDAP port) if you leave the port number blank.

4. Exit the Command Window.
5. Launch Toad and open the New Connection window.

Databases on the LDAP server should be available from the Database Alias drop-down list.

Note: At this point, Toad for DB2 supports only the access of DB2 LDAP catalog entries. Toad does not support the management of these entries (such as adding or removing them) Debugger Requirements

Compile and Debug Requirements for Stored SQL Procedures

The following are the requirements for using Toad to compile and debug stored SQL procedures in DB2 for z/OS.

Toad Client Requirements

To use the Toad debugger on stored SQL procedures, the following Toad client requirement must be met:

• The Toad client is running on a Windows XP machine.
• Java Runtime 1.4 or later is installed and specified in your system path.

DB2 Subsystem Requirements

Each DB2 subsystem on which you want to compile and debug stored SQL procedures must meet these requirements:

• To compile stored SQL procedures in Toad, the DB2 stored procedure SYSPROC.DSNTPSMP must be operational on the subsystem.
• To debug stored SQL procedures in Toad, the IBM DB2 installation job DSNTIJSD must be executed on the subsystem.

Requirements for Executing DB2 for z/OS Utilities

To bind and rebind packages and plans and to invoke utilities and commands within scripts like those scripts generated by advanced ALTERs or Migrations on a DB2 for z/OS subsystem, Toad for DB2 requires the following:

• Each subsystem on which you are executing utilities must contain the DB2 objects that support the Quest DB2 z/OS dataset templates. These objects already exist on a subsystem if you have installed either of the following products on the subsystem:
  • The z/OS components for Quest Central for DB2 4.9 or later
  • The Quest IBM DB2 for z/OS component available with Toad for DB2 3 or later

If neither product is installed on a subsystem, run edit and run the DDL that creates these objects. Click the following link to open the file containing this DDL:

ToadzOSTemplateDDL.txt

• The IBM stored procedure SYSPROC.DSNUTILU must be installed and operational on each subsystem on which you are executing utilities. For additional information about SYSPROC.DSNUTILU, refer to Appendix B of the IBM UDB for z/OS Utility Guide and Reference.

Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.

• When Toad generates an ALTER script that contains multiple UNLOADs and LOADs of table data, ensure that the DSN values in the dataset templates include a &SEQ variable to create unique dataset names. For examples on including this variable, refer to the dataset template definitions in the file ToadzOSTemplateDDL.txt.
• When you migrate data from one subsystem to another, Toad invokes the IBM DB2 for z/OS UNLOAD and LOAD utilities. The definition for Reorg Unload template should define a dataset that resides on a pack (VOLSER) that is accessible by both the source and target subsystem.

Recommended Indexes to Improve Toad Performance in DB2 for z/OS

User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects in Toad. To ensure the best possible performance from Toad, create the following indexes in each subsystem to which you are connecting in Toad:

• On the TSNAME column in SYSTABLES.
• On the BNAME and DNAME columns in SYSPACKDEP.
• On the COLLID  and NAME columns in SYSPACKAGE.
• On the  SYSCOLUMNS table, as defined in the following DDL. Edit the DDL as needed for your site.

CREATE INDEX TOADIX01
ON "SYSIBM"."SYSCOLUMNS"
("TBCREATOR" ASC,
"TBNAME" ASC,
"TYPESCHEMA" ASC,
"TYPENAME" ASC,
"COLTYPE" ASC
)
USING STOGROUP "SYSDEFLT"
PRIQTY 3600
SECQTY 3600
ERASE YES
FREEPAGE 0
PCTFREE 10
GBPCACHE CHANGED
DEFINE YES
BUFFERPOOL BP0
CLOSE NO
DEFER NO
COPY NO
PIECESIZE 2097152 K;

• On the SYSTABLES table, as defined in the following DDL. Edit the DDL as needed for your site.

CREATE INDEX TOADIX02
ON "SYSIBM"."SYSTABLES"
("NAME" ASC,
"CREATOR" ASC,
"DBNAME" ASC,
"TSNAME" ASC
)
USING STOGROUP "SYSDEFLT"
PRIQTY 7200
SECQTY 7200
ERASE YES
FREEPAGE 0
PCTFREE 10
GBPCACHE CHANGED
DEFINE YES
BUFFERPOOL BP0
CLOSE NO
DEFER NO
COPY NO
PIECESIZE 2097152 K;
 

Requirements for Object Migration

Adhere to these requirements when you use the Toad's Schema Migration wizard to migrate DB2 objects and their dependencies.

Methods for Handling Target Tablespaces

You must handle target tablespaces in one of two ways:

• Use the wizard's Transformation Rules to specify target tablespaces that already exist. If the specified tablespaces (and, in DB2 for z/OS, the databases to which these tablespaces belong) do not exist, Schema Migration assumes that you will create these tablespaces (and databases) before the you run the migration script. The wizard does not generate the DDL for these objects in the migration script.

  or

• Skip the Transformation Rules section, and let the wizard generate the migration script to include the DDL that creates the target tablespaces. However, the wizard bases this DDL on the DDL for the source tablespaces. You must edit the migration script before executing it to customize the DDL for the target environment.

  Notes:

  • Schema Migration does not migrate DB2 for z/OS databases. Therefore, it does not generate the DDL for databases to which the tablespaces belong.
  • In DB2 for z/OS, Schema Migration supports migrating a target tablespace that was implicitly created on the source. The DDL generated creates an explicit tablespace that uses the same name and database as the source tablespace. Additionally, Schema Migration generates the DDL to migrate all the tables in the tablepace.

Migration of Tables with Referential-Integrity Relationships

When migrating a table that has referential-integrity relationships to other tables, select the Include dependencies option on the Select Objects for Migration page in the wizard. This option generates the statements necessary in the script to migrate the related tables. If you do not select this option, you must edit the migration script to include these statements.

Additional Special Specifications for Sources and Targets

The following requirements and restrictions exist for source and targets:

• You cannot migrate objects between a DB2 for LUW and DB2 for z/OS platform and vice versa.
• You can migrate objects between different versions of DB2 on the same platform (for example, between DB2 for LUW 8 and DB2 for LUW 9) as long as both the source and target databases (or subsystems) exist on the same computer.

  Note: When you are migrating objects between different versions, the Include statistics by default on the Select Objects for Migration page in the wizard is disabled.

• Do not map two source schemas to the same target schema. (For example, you cannot map both source Schema A and source Schema B to target Schema C.)

Version Control Requirements

Toad for DB2 supports the following version control providers for the versions and platforms listed. Testing is not complete for versions and platforms not listed:

Ensure that you install the following on the same computer on which you installed Toad:

Back to Top

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:

• Toad Editions that contain Knowledge Xpert.

The Knowledge Xpert feature is available with English language content only.

Back to Top

Getting Started

Contents of the Release Package

The Toad for DB2 release package contains the following products:

1. Toad for DB2 4.0
2. Quest IBM DB2 z/OS component
3. Product Documentation, including:
   • Getting Started Guide
   • Online Help

Installation Instructions

For important information about installing Toad for DB2, refer to the Toad for DB2 Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

For instructions on installing the Quest IBM DB2 z/OS component, refer to the Quest IBM DB2 z/OS Component Installation Guide. This guide is available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Back to Top

For More Information

Contacting Quest Software:

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

Contacting Quest Support:

(Commercial and Trial Support only)

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:

• Quickly find thousands of solutions (Knowledgebase articles/documents).
• Download patches and upgrades.
• Seek help from a Support engineer.
• Log and update your case, and check its status.

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%20Support%20Guide.pdf.

Beta Group

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

Participate in the Beta Yahoo! Board

Back to Top

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.

© 2008 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:

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.

Back to Top