Friday, February 11, 2022
With Toad, developers and database administrators can use a familiar, proven tool to manage databases. Toad empowers developers and administrators, of varying skill levels, to rapidly create and execute queries, automate database object management, and develop SQL more efficiently.
Toad also provides utilities to compare, extract and search for objects, manage projects, import/export data and administer the database, while increasing your productivity and delivering access to an active user community.
Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements:
2 GHz processor (recommended minimum)
8 GB of RAM minimum, 16 GB recommended
Note: The memory required may vary based on the following:
Hard Disk Space
800 MB to install Toad
Note: The disk space required may vary based on the edition of Toad selected for installation.
Windows Server® 2012
Windows Server® 2012 R2
Windows Server® 2016
Windows Server® 2019
Windows® 8.1 (32-bit or 64-bit)
|Deprecated Version of Windows||
Toad for DB2 customer support will not be available for the following operating systems as Microsoft has stopped providing support for these platforms.
Microsoft® .NET Framework 4.7.1
When connecting to a DB2 database/subsystem, ensure that you have a DB2 Client or IBM Data Server Driver installed. Toad supports DB2 Client versions 10.5 through 11.5.
Toad has been tested with the following versions of the DB2 Client: 10.5.0, 10.5.2, 10.5.3, 11.1.0, and 11.5.
Microsoft® Internet Explorer® 11 or later
Recommended maximum DPI settings for Toad are 125%. It is possible to use Toad up to 200% but some dialog windows will not be completely usable anymore.
Maximum tested resolution for Toad is 1920 x 1080 px.
Before installing Toad, ensure that your server meets the following minimum hardware and software requirements:
IBM DB2 for LUW 10.5.x, 11.1.x, 11.5.x
IBM DB2 for z/OS 11, 12
Note: Toad may support IBM DB2 Express and SWE in addition to listed above servers but note that no testing was performed on it.
Note: Windows 8.1, 10 and Windows Server 2012 require the following Fix Pack in order to ensure registration of DLLs in Global Assembly Cache:
Note: To use Access 2016 64-bit to connect to an Access database in Toad, the Microsoft Access Database Engine is required and might not be included in the Access installation. The engine must match the architecture (bitness) of Toad.
|Deprecated Version of Database Server||
When deploying Toad in a virtualization environment, for best results ensure the system accurately reflects the applicable client hardware and software requirements listed in this document.
Toad has been developed using Microsoft guidelines (see Remote Desktop Services programming guidelines) and can be deployed and operated in virtualization environments such as Citrix XenApp, Microsoft App-V, and VirtualBox.
Only Windows Administrators and Power Users can install Toad.
Note: The following exceptions exist for Power Users:
If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and menu items with any user—a Power User, Restricted User—on the computer.
If a Power User installs Toad, a Restricted User cannot do the following:
The following describes the requirements and restrictions for users who launch and run Toad:
To take full advantage of Toad for DB2 LUW functionality, the user ID specified in the Toad connection profile for each DB2 for LUW database connection requires the authorizations listed in the following document:
The following is a list of issues addressed in this release of Toad for IBM DB2:
Resolved Issues in 7.4
|Feature||Resolved Issues||Defect ID|
|Alter Database Script||Application is not generating the script correctly for the Alter Database operation under the SQL Script tab.||TDB-3981|
|Project Rename||Project rename functionality under the Project Manager option is not working for a newly created project.||TDB-3978|
|Publish Project||Toad for DB2 displays an error while publishing a newly created project.||TDB-3977|
The following is a list of issues known to exist at the time of this release.
|Feature||Description||Support Case/Defect ID|
|General||The Explain Plan screen is not displaying the results, when an SQL Query is executed in the Editor tab.||TDB-4003|
|General||Toad for DB2 displays an error when users try to create a new Like table from the Object Explorer pane.||TDB-4001|
|General||Application is not generating the script correctly for the Alter Database operation under the SQL Script tab.||TDB-4000|
|General||Toad for DB2 is not displaying any matching files when searched using the Find and Replace option.||TDB-3999|
|General||Toad for DB2 displays an error when users try to create a new table from the Object Explorer pane.||TDB-3997|
|General||Toad for DB2 displays an error when users try to import data using the Excel Instance option.||TDB-3980|
|SQL Script Generation||Toad for DB2 is not generating the script correctly while creating database constraints to retrieve data.||TDB-3979|
|General||Toad for DB2 displays an error even after entering the valid server details to test the connection using the FTP connection functionality. Also, system displays an inappropriate error message.||TDB-3976|
|Toad Intelligence Central||Application displays an error while registering a new user in Toad Intelligence Central.||TDB-3975|
|General||Toad for DB2 is not generating the application log while performing any operation.||TDB-3973|
|Script for Alter Table||Upon making any modifications in the existing columns of a table, application generates the updated SQL script in the comment form due to which users are not able to alter the tables.||TDB-3971|
|General||Application displays an error while opening the Spotlight application as an integrated Quest tool.||TDB-3969|
|General||Toad is not displaying the execution cancellation alert message every time users cancel/stop the execution.||TDB-3968|
|Export Connection||Since the Save button used while exporting connections is disabled, users are not able to export connections using the Connection Manager option.||TDB-3967|
|General||Toad displays an error while exporting a MS Excel linked query of an output.||TDB-3966|
|Alter Database Window||Application does not display any fields/options on the Alter Database screen under the Storage Path option.||TDB-3965|
|Object Details||When a DB2 object is created, DB2 implicitly creates authority for the user who created that object. In the system catalog tables those are shown as SYSIBM as the Grantor. When migration\compare\extended alter scripts are generated Toad does not generate GRANT statements in those scripts for authorizations granted by SYSIBM because those are granted implicit authorizations that have been created by DB2.||TDB-870|
You might encounter issues with initializing Unified Debugger sessions if the version of the DB2 for LUW server on which you are debugging is earlier than 10.1 fix pack 2.
Workaround: If the DB2 server version is earlier than DB2 for LUW 10.1 fix pack 2, copy DB2DBGM.JAR from the Toad client installation to the following location on the server:
If the DB2 server version is DB2 for 10.1 fix pack 2, use the JAR file supplied with your DB2 version. If replacing the JAR file as described in the workaround, make sure you back up the original JAR file on the server before replacing it with the one from the Toad client installation.
|Export Wizard/ One Click Export||Avoid using Excel for exporting if your data has numeric values that require a high precision because Excel's precision is limited to 15 digits. If you export numbers with more precision, the values are rounded. If you export boundary numbers (max, min), rounded numbers will exceed the data type limit.||N/A|
|Installation||Network and LAN installations are currently not supported.||N/A|
Toad uses hardcoded values instead of some variables such as %USERNAME% in several path names and therefore App-V environment is not supported.
For installation adhere to Windows Installer Best Practices, see here.
If running Toad for IBM DB2 6.0 or earlier in a pureScale environment and the QUEST.SH_SNAPSHOT procedure had been installed, the procedure will have to be redefined. Please, follow these steps:
|SQL Editor||Toad does not handle DBMS_OUTPUT in the SQL Editor.||ST90710|
|z/OS Utilities||When using Utilities as the data preservation method and the length of a column tied to columns from other tables via RI is reduced. When executing the alter script the load fails with a DSNU334I INPUT FIELD INVALID error pointing to the altered column. The load cards show the old length for the altered column which appears to be the problem.||ST44753|