Chat now with support
Chat with Support

Toad for DB2 7.2 - Installation Guide

Install Toad on Citrix Systems

Toad must be installed on the Citrix server by the Citrix administrator. Users then connect to this instance through their Citrix login.

To install Toad on a Citrix system

  1. Connect to the Citrix Environment as an administrator.

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

  3. Start the Toad installation process.

  4. During installation, on the Product Selection page, select Toad for IBM DB2 and click More Info. Then select the Install for everyone checkbox.

  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:

    • Individual licenses should be entered for each user.


Upgrade Toad

To upgrade Toad

  1. Run appropriate Toad installer (ToadForDB2_version) from the DVD or downloaded file.
  2. Select the products you want to install and click Install.

If you are upgrading from a previous version of Toad, you are prompted to migrate your settings the first time you start Toad. The settings files include database connections, layout customizations, shortcut keys, and options customized in the Options pages.

To migrate the settings again, remove or rename the current version's Application Data folder and migrate the files from the previous version's Application Data folder.

Upgrade Automation Scripts

If you upgrade to a newer version of Toad, Automation scripts created in a previous version must be upgraded before you can open them in the newer version. Toad prompts you to automatically upgrade a script when you attempt to open it in a newer version.

In addition, scheduled scripts are scheduled to run using the version of Toad in which they were created. After upgrading Toad, those previously-created, scheduled scripts will not execute in the newer version until you migrate each script's scheduling task. Toad prompts you to migrate scheduling tasks when you initially launch the application after installation.

Note: If Toad was installed with the Prohibit saving passwords option selected, the Automation module is disabled and Toad does not prompt you to migrate scripts.

Upgrade Automation Scripts to Newer Version of Toad

An automation script is compatible with the version of Toad in which the script was created. If you want to open and/or modify a script using a newer version of Toad, you must upgrade the script. Toad automatically prompts you to upgrade the script the first time you open it in the newer version.

To upgrade an Automation script

  1. Open the script in Toad. Toad prompts you to upgrade the script.

  2. To upgrade the script, select Yes.

    Caution: If you upgrade an automation script, it will no longer be compatible with earlier versions of Toad.

  3. Select No (and do not elect to save the script), to keep the script compatible with the previous version.
  4. If you selected Yes, Toad upgrades your script and saves a backup copy of the original script in the following location:

    <application data directory>\Automation\bak\

  5. If the script you upgraded is also scheduled, you must migrate the scheduling task, otherwise the upgraded script will fail to run.

Migrate Scheduling Tasks to Newer Version of Toad

Each scheduled Automation script uses a Windows scheduling task. The scheduling task specifies which version of Toad to use by specifying the version's application path. Toad provides you with two easy ways to migrate your scheduled scripts' scheduling tasks when you upgrade Toad. First, Toad prompts you to migrate scheduling tasks upon initial launch of the application after installation. Next, you can migrate scheduling tasks at any time using the Job Manager.


  • If you upgrade a previously-created script by opening it in a newer version of Toad, you must also migrate the scheduling task to the newer version.
  • If you install the newer version of Toad side-by-side with the older version, previously-created, scheduled scripts will continue to execute using the older version, until you migrate the scheduling tasks (provided that you do not open the scripts in the newer version).

To migrate scheduling tasks upon initial launch

  1. After upgrading Toad, and upon initial launch of the application, the Migrate Scheduled Tasks dialog opens.
  2. Select the scheduled tasks (scheduled Automation scripts) to migrate to the new version of Toad.
  3. Click OK to close the dialog.
  4. Toad immediately prompts you for your Windows password. Enter your password to migrate the scheduled tasks.

To migrate scheduling tasks using the Job Manager

  1. Select Tools | Administer | Job Manager.
  2. Click on the Job Manager toolbar.
  3. Select the scheduled tasks to migrate and click OK.

    Note: Only currently-scheduled tasks (enabled or disabled) are listed in the Migrate Scheduled Tasks dialog.

  4. Toad immediately prompts you for your Windows password. Enter your password to migrate the scheduled tasks.

Manually Edit Scheduling Tasks

On occasion you may need to modify the application path in a Windows scheduling task. You can do this by manually editing the scheduling task using the following procedure.

To manually edit a scheduling task

  1. In the Job Manager (Tools | Administer | Job Manager), right-click a task and select Edit Task.
  2. To change the version of Toad used to run the script, in the Actions tab, change the folder name in the toad.exe path.


Files Migrated During Upgrades

When upgrading to a new version of Toad, the following files can be migrated from the previous version's Application Data Directory (click the Application Data Directory link in Help | About to open the directory).

Caution! Migrating settings from a previous version of Toad may overwrite new settings files, implemented for the current release (for example, updated reports templates, layouts, etc).




Tracks your usage within Toad. If you agree to share this data, the file is automatically sent to Quest Software on a periodic basis.


Contains all connections stored in the Connection Manager or the New Connection window.


Contains the SQL Output connection trace log file if you select Tools | Execution Trace from the menu.


Contains a log of all exceptions encountered while running Toad.


Contains a log of exceptions encountered when attempting to connect to FTP servers.


Contains connections to FTP servers stored in the FTP Connections window.


Contains the private object annotation cache options (object notes, Lookup tables, and hidden columns). You can share these options with other Toad users in Tools | Options | Database | Cache.


Contains many of the global configuration settings.

Contains the last support bundle you generated.



Automation (temporary folder)

Used by automation when executing automation scripts.


Used to spool cache database metadata to disk if enabled. The data is in binary format and can always be recreated by fetching it from the database.


Contains settings that depend on the context within Toad including the following:

  • Adapter—Custom data editing statements.

  • Filter—Unnamed filters defined in the Object Explorer or Database Explorer.

  • Named Filter—Named filters defined in the Object Explorer or Database Explorer.

  • TYPE—Tabs that display on the right when you select an object in the Object Explorer or Database Explorer.

Document Recovery

Contains backup copies of Editor, Query Builder, and Database Diagram files saved if you have enabled Document Recovery in Tools | Options | Environment | General.


Contains custom keyboard shortcut layouts.


Contains layouts for some areas in Toad, such as tool windows that automatically display in the Editor and column layouts for the Messages tab.


Contains general settings for various components in Toad, such as whether the data grid defaults to read-only, displays not null indicators, etc.


Used by Toad plugin components.


Contains desktop configurations, including toolbar customizations and tool window locations.


Contains pre-set and user created templates for formatting SQL, and the SQL statement used to preview formatting changes in the Formatting Options page.


Contains the SQL statements saved by SQL Recall.


Contains the following templates:

  • Code Templates—Templates used to define default values when creating new objects in the Object Explorer or Database Browser.

  • Scripts—Startup scripts to run when connecting.   

  • Snippets—Code Snippet entries.

  • Reports—Report entries.


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating