Wednesday, October 20, 2021
Toad® Data Point is a multi-platform database query tool built for anyone who needs to access data, understand data relationships, and quickly produce reports.
With Toad Data Point, you can:
Toad Data Point provides a full-featured Database Explorer, Query Builder, and Editor for the following databases:
Toad Data Point also provides querying and reporting functionality via the following provider types:
The purpose of the ODBC provider is to offer basic connection and querying capabilities to any database that supports an ODBC 3.0 or later driver. For a list of databases tested with the ODBC provider, see the System Requirements in the Release Notes. This form of connectivity allows connections to databases such as Netezza, IBM iSeries, Ingres, and Vertica™. Because this form of connectivity is generic, it is not full-featured and may not be as robust as the fully-exploited providers for the other databases.
Business Intelligence and NoSQL Data Sources
Toad Data Point provides users with the ability to connect to non-traditional data sources, such as Business Intelligence and NoSQL sources. You can connect to these data sources and explore data and objects, query data, report results, and automate tasks.
The following data sources are supported:
Toad Data Point 5.5 is a minor release with enhancements and resolved issues.
In Toad Data Point 5.5, the following new features were implemented:
New abilities to publish Toad Data Point Workbook to Toad Intelligence Central. (For more information, see the Toad Intelligence Central Release Notes.)
Remember, you can find blogs, videos, and forums at the Toad Data Point 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
Additional RAM Requirements: Using Local Storage, Cross-Connection Query, Business Intelligence connections, or NoSQL connections can require an additional 500 MB of RAM. These features start processes (mysqld.exe, hubproxy.exe) which persist for the Toad session.
Note: The memory required may vary based on the following:
Hard Disk Space
800 MB to install Toad
Additional Recommendations: For retrieving large queries, allow 10 GB free disk space (or more, depending on the size of the data being retrieved). After retrieving 2500 rows, Toad saves data in a TMP (.tmp) file in the user's Temp directory. These TMP files are deleted when Toad closes.
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
Teradata® .NET Data Provider
You must install the Teradata .NET Data Provider (13.10 or later) to use a Teradata native connection in Toad.
Note: To use a Teradata connection in a cross-connection query, you must also install a Teradata (13.10 or later) ODBC driver.
Visual C++ Redistributable for Visual Studio 2019. This software is required. It is included in installation using the .exe installer. If using the .msi installer, ensure that this software is installed prior to installation. See Visual C++ Redistributable for VS 2019.
For 64-bit Toad Data Point, both 32-bit and 64-bit Visual C++ packages are required.
Toad no longer installs a DB2 Client along with the Toad application. When connecting to a DB2 database, ensure that you have a DB2 Client or IBM Data Server Driver installed. Toad supports DB2 Client versions 9.7.6 through 11.1.
Toad can connect to Oracle using Direct Connect (no Oracle Client required) or using an Oracle Client or Oracle Instant Client. However, if you want to use LDAP, you must install an Oracle Client. Toad supports 9i or later Oracle Clients and Oracle Instant Clients.
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:
Toad supports the following databases:
Oracle 10g R2, 11g, 11g R2, 12c, 12c R2, 18c
Toad has been tested on Oracle Exadata 2.0 running Oracle database 11g R2.
SQL Server 2012 and SQL Server 2012 Express
SQL Server 2014 Enterprise and SQL Server 2014 Express
SQL Server 2016
SQL Server 2017
SQL Server 2019
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:
MySQL 5.0, 5.1, 5.5, 5.6, 5.7
MariaDB 5.5.5, 10.2.8, 10.3.2
SAP ASE 15.5, 15.7, 16 SP03
SAP IQ 15, 16
SAP SQL Anywhere 16
SAP HANA SPS 08, SPS 09, SPS 10, SPS 11, SPS 12, SAP HANA 2.0, SAP HANA 2.0 SPS 02
Teradata 12.0, 13.0, 13.10, 14, 15, 16
Access® 2007, 2010, 2013, 2016
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.
Excel® 2003, 2007, 2010, 2013, 2016
Note: To use Excel 2016 64-bit to connect to an Excel or .csv file in Toad, the Microsoft Access Database Engine is required and might not be included in the Excel installation. The engine must match the architecture (bitness) of Toad.
ODBC Database Server
Toad Data Point allows you to create a connection to a database that supports an ODBC 3.0 or later driver. ODBC connectivity provides basic querying capability, but may not be as full-featured as a native connection in Toad. Toad has been tested on the following databases, using an ODBC connection:
Note: For a list of databases that are not supported, see Known Issues in the Release Notes.
|Cloud Database Service||
Oracle databases running on Amazon EC2
SQL Azure and Azure SQL Data Warehouse
Note: To be able to utilize a majority of Toad functionality, please grant VIEW DEFINITION on the SQL Azure databases you want to work with.
SQL Server databases running on Amazon EC2
Toad can manage Amazon RDS and any other cloud or service offering compatible with MySQL.
Business Intelligence Connections
Toad has been tested with, and supports, the following Business Intelligence platforms:
SAP Business Objects XI 3.1, 4.1
Oracle Business Intelligence Enterprise Edition 12.2
Microsoft SQL Server Analysis Services 2016
OData version 4
SharePoint® Server 2013
Toad has been tested with, and supports, the following NoSQL platforms:
Azure Table Services
Apache Cassandra™ 3.11.0
Apache HBASE™ 1.2.6
Apache Hive™ 2.1.0
Cloudera Impala 2.9.0, 3.2.0 with CDH 6.3.2. Toad Data Point has been certified by Cloudera.
MongoDB™ 3.4.6, 3.4.9, 4.0
|Toad Intelligence Central||
This release of Toad Data Point has been tested with Toad Intelligence Central 4.3 and 5.0.
Note: Some publishing features in this release of Toad might not be supported in earlier versions of Intelligence Central. For more information about compatibility between Intelligence Central versions and Toad Data Point 5.5 features, see the New Features section of the Toad Data Point Release Notes.
|VM and Cloud Platform Environments||In general, the databases and data sources listed in this table are also supported when installed on a virtual machine (VM) or cloud platform. See the database or data source documentation for more specific information.|
Data Set Size
The following Toad Data Point functionality has been tested with data sets of up to 5 million rows: SQL Editor, Data Compare, Import Wizard, Export Wizard, Publishing Data to Intelligence Central.
For the following Toad Data Point modules, working with very large data sets can impact performance. For best results in these areas, work with data sets of less than 1 million rows: Dimensional Viewer, Pivot Grid, manually sorting a result grid, performing more than one Data Compare at a time (such as running multiple Data Compare Automation scripts simultaneously).
|Security||Starting with Toad Data Point version 5.5, the TLS protocol v1.2 or above is required to work with an encrypted MySQL connection|
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.
Toad has been tested with the following:
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:
The following is a list of issues addressed and enhancements implemented in this release of Toad Data Point:
Resolved Issues in 5.5
|Automation||"The path is not of a legal form" error is encountered when the automation script contains the Copy File step with the Relative Paths and Wild Cards in the Source File name is run||QAT-16446|
|Automation||The unnecessary subfolders are created in the generated Zip file when the automation script containing Zip/UnZip files step is run||QAT-16548|
|Automation||"You are opening a script that was created using a newer version of Automation" warning message is shown when loading an automation script created in Toad Data Point 5.3 version and older||QAT-16531|
|Code Snippets||The hyperlinks for Advanced Analytics in the Code Snippets panel are not available QAT-16546||QAT-16546|
|Compare Object||The Select Columns For Comparison window does not have the minimum size set QAT-16556||QAT-16556|
|Connection Manager||Connection to a Oracle database is failing if the tnsnames.ora file containing database alias||QAT-16495|
|Connection Manager||LDAP database names are no longer listed under the Database name drop-down list of Connection window QAT-16523||QAT-16523|
|Connection Manager||Only the firstly connected Azure SQL Database is available for quering||QAT-16229|
|Explain Plan||“System.Runtime.InteropServices.COMExceptlon Unknown error.” error is encountered when the Execute Explain Plan button is clicked in the Query Editor tab of the created workbook||QAT-16086|
|Object Details||The View script is shown in one row in the Script sub-tab under the Viewer tab||QAT-16526|
|Object Explorer||The same database is shown in the Object Explorer panel for two different Azure SQL Database connections||QAT-16595|
|Options||The script is shown in one line under the Formatter Preview tab in the Options window||QAT-16543|
|Script Results||"Missing a parameter to a query" error is encountered when the Transform and Cleanse option is clicked for a Google Analytics query result||QAT-16567|
|Scripts tab||Script is shown in one row in the Script sub-tab under the View tab for Oracle connection||QAT-16544|
|SQL Azure||The log file is deleted after the Import data process is done with errors||QAT-16527|
|Workflow||“Failed to change connection” error is encountered when loading previously created workbook with the different set of data source credentials||QAT-16392|
|Workflow||“No viable alternative at input” error is encountered when the Test button is clicked in the Build Expression window for a statement containing backslash||QAT-16439|
HTTPS connection for Microsoft Azure Table Services is supported