Friday, May 22, 2020
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.
Toad for IBM DB2 7.2 is a minor release with new features, security enhancements, and resolved issues.
In Toad for IBM DB2 7.2 the following new features were implemented:
You now can use Toad to connect and use new features of IBM DB2 LUW 11.5 including external tables.
We added new options for Group By functions. Right-click a column header and Select from the available Group By options according to your data.
Now you can also summarize by ListAgg function.
See Resolved Issues for more enhancements and resolved issues in this release of Toad for IBM DB2.
Get the latest product information, find helpful resources, and join a discussion with the Toad for IBM DB2 team and other community members. Join the Toad for IBM DB2 community at
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)
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 9.7.6 through 11.5.
Toad has been tested with the following versions of the DB2 Client: 9.7.6, 9.7.9 , 10.1.0, 10.1.2, 10.1.3, 10.5.0, 10.5.2, 10.5.3, and 11.1.0.
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 3800 x 2160 px.
Before installing Toad, ensure that your server meets the following minimum hardware and software requirements:
IBM DB2 for LUW 9.7, 10.1, 10.5, 10.5.0.5, 11.1, 11.5
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, 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.
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:
As a minimum requirement to manage a DB2 for z/OS subsystem in Toad, the user ID defined in the Toad connection profile for the subsystem must either have SYSADM privileges or SELECT privileges on the DB2 catalog tables. For a complete list of authorizations (and corresponding GRANT statements) a user requires to take full advantage of Toad for DB2 z/OS functionality, refer to the following document:
The following is a list of issues addressed and enhancements implemented in this release of Toad for IBM DB2:
|Publishing wizard now sets permissions of objects correctly in Automation script
|Dragging and dropping column names from Object Explorer to Editor now works correctly.
|Data Compare & Sync
|We have implemented a new performance option for exporting to Excel. Enable it in Tools | Options | Data Compare | General
|Data Compare & Sync
|An issue when Data Compare displayed incorrect results has been fixed
|Data Compare & Sync
|Error during Data Compare with a Local Storage table has been fixed
|Data Compare & Sync
|An error when not all data rows were returned in Data Compare has been fixed
|An error when parsing a TIC query with group_concat() function has been fixed
|Users that execute Automation script are not added to OS Admin group on server anymore
|Behavior of Toad at high resolutions since patch version 5.1.2 has been improved
|2320/4620661, 4623009, 4685386, 4685115
Collation property while importing data using Automation script has been modified to improve performance with certain JOINS on Tables
|Save Log option is now saved in Import Templates
|It is now possible to import blank values
|Opening associated files with SQL extension now works correctly with Toad
You now can deploy user settings during silent installation of Toad. Enter a full path to the Options Template that you generated in Tools | Options | General for a silent installation.
|An issue with migration of a Task Manager item using a password has been fixed
|Object Details (DOV)
|We fixed an issue in the DB2 z/OS Subsystem - Right-Hand-Side Dynamic Statement Cache tab where a DB2 error was being thrown when a DSC table was selected if that table creator began with an @.
|Up and Down arrows now work correctly in Tools | Options | Explorer | Objects
|We have added options for Date Grouping and Formatting in Pivot Grid
|We improved backward compatibility of Pivot Grid
|Pivot Grid now allows you to use Aggregated data values in a calculated field.
|We improved attachment of Calculated fields in Query Builder to correct columns
|Several issues when using Where clause in Query Builder have been fixed
|An issue with WHERE clauses has been fixed
|Adding additional AND clause in query tab and then visualizing does not create a Global Where clause
|You now can select LAG and LEAD in the list of functions for calculated fields in Query Builder
|Now you can ignore differences in constraint names when one of the names is system generated
|Statistics profile is now preserved when you drop and recreate a table
AutoCommit on IBM DB2 connections now works as designed
|Highlighting keyboard shortcuts now work correctly in Editor.
|QAT-15111/4542078, 4555409, 4559368, 4564671
Publishing a script with different schemas from the same database now works correctly