Toad Data Point 6.1
Toad Data Point 6.1
Release Notes
Tuesday, June 6, 2023
Contents
About Toad Data Point
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:
- Connect to almost any database or ODBC data source (see the Release Notes for a list of tested ODBC connections)
- Write SQL queries and join data across all platforms
- Automate and schedule frequent and repetitive tasks
- Streamline data collection
- Collaborate with team members
- Export data in a variety of file formats
Toad Data Point provides a full-featured Database Explorer, Query Builder, and Editor for the following databases:
- Oracle®
- SQL Server® and SQL Azure
- IBM® DB2® (LUW and z/OS)
- SAP® ASE, IQ, SQL Anywhere, and HANA
- Teradata®
- MySQL
- Snowflake®
Toad Data Point also provides querying and reporting functionality via the following provider types:
- ODBC
- Business Intelligence and NoSQL data sources
- Microsoft® Excel®
- Microsoft Access®
ODBC Connections
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:
| Business Intelligence |
SAP Business Objects™ | Google Analytics™ | OData | Oracle BI Enterprise | Salesforce® | SharePoint® | SQL Server Analysis Services |
| NoSQL |
Azure Table Service | Cassandra™ | Cloudera Impala | DynamoDB | HBASE™ | Hive™ | MongoDB™ |
Toad Data Point 6.1 is a minor release with new features, security enhancements, and resolved issues.
New Features
In Toad Data Point 6.1 the following new features were implemented:
The Information Page has been added to the Toad Workbook file
Adding all necessary information about the created new Toad Workbook file is now possible by creating and editing a workbook Information Page as a part of the workbook. The option for adding this page to the workbook is located in the main ribbon as a button, and clicking it will open the rich-text file editor in an additional tab. Closing that tab after adding/editing information will raise the Save dialog - if saved, the information page becomes a part of the workbook.
This page allows users to have all information present in one file to better understand why the workbook file was created in the first place and what it is used for before running or downloading it. Since the Information Page gets created along with the workbook, the content of the page will also be available in Toad Intelligence Central.
Workbook files created in earlier versions of Toad Workbook did not include this specific page. However, it is possible to add this page to those files using Toad Workbook 6.1
Option to trim char data type field when exporting data to Excel or CSV files
A new option has been added to the exporting functionality in Toad Data Point to accommodate the use case for preventing the export of spaces at the end of Char data type column values when exporting result sets (in case the values are shorter than the length specified in the column definition).
This option is located under the Options window | Environment section | Export and is unchecked by default.
Enabling this option would ensure that all columns in the exported result set containing char data types will only occupy the number of characters that match the value of the specific row by trimming extra spaces to the end of the string to match the column definition. The automatic trimming of the char data type also encompasses export pivot options, meaning that these settings will be applied when doing an export of a Pivot Grid for the following export options:
-
Excel Pivot
-
Excel Grid
-
Excel Pivot View
-
CSV
The shared reports recipient list is available for editing on the workbook run
The Shared Reports options in Toad Workbook allow you to create an email template with a list of recipients that will receive emails containing shared reports. If the "Prompt" checkbox is selected, a dialog with the recipient list will be displayed and available for editing as any other workbook variable when the workbook is run.
When sending emails to multiple recipients, it may be helpful to use distribution lists for sharing reports because the "To:" input field has a limit of 256 characters when composing an email.
Share reports settings will be saved and present in the published workbook and available for running on Toad Intelligence Central. If the "Prompt" checkbox is selected, a dialog with the recipient list will also be displayed and available for editing as any other workbook variable on Toad Intelligence Central.
Option to include Pivot Grid individual subtotals
An additional option for including individual subtotal rows in a Pivot Grid has been implemented. If the Pivot grid contains the subtotal rows, a new option in the right-click context menu allows you to choose whether the sum columns should be shown for a single row.
Search options in the data grid have been improved
The "Auto Filter Row" option is now enabled by default in the data grid to improve data search functionality by using conditional operators specific to the column's data type. An additional filter row is available in the Result set tab below the column headers.
These default settings can be changed by right-clicking on the column header and selecting the "Hide Auto Filter Row" option from the context menu.
An export option to preserve the original form of a Pivot grid
The "Excel Pivot View" option is available in the Pivot Grid drop-down menu and the Activity section of the Automation module, enabling users to export the Pivot Grid in the same form in which it is displayed in Toad Data Point.
This option is also available in Toad Workbook by adding the "Excel Pivot View" report step under the Report dialog for the Pivot Grid parent step.
Idea Pond
 |
Got a great idea for a new Toad Data Point feature or enhancement? Share it with the Development Team and the Community by posting it on Idea Pond. Visit Toad Data Point - Idea Pond where you can submit your ideas. You can also read and vote on the enhancement ideas submitted by other Toad users. |
Learn More
Remember, you can find blogs, videos, and forums at the Toad Data Point Community.
- Toad Data Point Videos - Learn about new features from product video demos.
- Toad Data Point Forum - Find answers to your questions in the forums.
- Toad Data Point Blog - Learn tips and tricks from blog posts.
- Toad Data Point - Idea Pond - Submit your idea to the Development Team.
System Requirements
Client Requirements
Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements:
| Requirement | Details |
|---|---|
|
Platform |
2 GHz processor (recommended minimum) |
|
Memory |
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. |
|
Operating System |
Windows Server® 2012 Windows Server® 2012 R2 Windows Server® 2016 Windows Server® 2019 Windows® 8.1 (32-bit or 64-bit) Windows® 10 |
| .NET Framework | Microsoft® .NET Framework 4.7.2 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. |
| Additional Software |
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. |
| Database Client |
DB2® Client 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. Oracle® Client 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. Notes:
|
| ODBC Driver |
In order to create a native Snowflake connection, you must install the ODBC Driver 2.24.2 (or later) provided by Snowflake. Upon installing and configuring the driver, Toad Data Point will be set for this type of connection. Note: New versions of the Snowflake ODBC Driver are backward-compatible, but there is no guarantee that earlier versions are forward-compatible. Active monitoring and maintaining of installed versions is advised. For more information regarding the process of creating Snowflake connections, please refer to the Installation Guide and User Guide. |
|
Additional Requirements |
Web Browser Microsoft® Internet Explorer® 11 or later Screen 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. |
Server Requirements
Before installing Toad, ensure that your server meets the following minimum hardware and software requirements:
| Requirement | Details | ||||||
|---|---|---|---|---|---|---|---|
|
|
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 Notes:
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 Salesforce.com® Microsoft SQL Server Analysis Services 2016 Google Analytics™ OData version 4 SharePoint® Server 2013 | ||||||
| NoSQL Connections |
Toad has been tested with, and supports, the following NoSQL platforms: Azure Table Services Apache Cassandra™ 3.11.0 Amazon DynamoDB 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 5.6. 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 6.1 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. | ||||||
| Additional Testing |
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). Notes:
| ||||||
| Security |
|
Virtualization Support
| Requirement | Details |
|---|---|
| Application Virtualization |
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. |
| Server Virtualization |
Toad has been tested with the following:
|
User Requirements
User Requirements to Install Toad
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:
- Associate file extensions.
- View the Toad shortcut icon on the desktop or the Toad menu options in the Windows Start menu. As a workaround, Restricted Users can create a shortcut to Toad from the install directory and place the shortcut on their desktop.
User Requirements and Restrictions for Running Toad
The following describes the requirements and restrictions for users who launch and run Toad:
-
-
- To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security features.
Resolved Issues and Enhancements
The following is a list of issues addressed and enhancements implemented in this release of Toad Data Point:
Resolved Issues in 6.1
| Feature | Resolved Issue / Enhancement | Defect ID |
|---|---|---|
| Automation | "The Embedded Automation file is too large or complex to process." error is encountered when an automation script containing another automation script that compares databases with over 800 tables and 1600 columns is run | QAT-17591 |
| Automation | Automation script containing a .tct file which includes a table without records on a DB2 Z/OS connection never finishes running | QAT-17728 |
| Automation | String variables in the automation script are wrongly formatted when the Arithmetic Operators are used as a parameter in Replace function | QAT-17767 |
| Automation | "[Teradata Database] [3706] Syntax error: expected something between the 'WHEN' keyword and the 'WHEN' keyword." error is encountered when an automation script containing Export activity is run on the Teradata connection | QAT-17939 |
| Automation | Overwrite output file function for a Data Visualization activity in an automation script is always enabled regardless of whether the option is checked or not | QAT-18060 |
| Automation | "Cannot access a closed file." error is encountered when an Automation script containing a Dimensional View activity with the "Embed files into Automation script" option checked is run | QAT-18122 |
| Automation | Timestamp suffix as part of the report names in Automation is not applied if the Overwrite option is checked | QAT-18171 |
| Automation | The Find and Replace activity in Automation does not replace the placeholder text with specified values | QAT-17763 |
| Automation Tour | SQL script cannot be chosen from the Automation Tour wizard | QAT-17315 |
| Change Connection | "Reconstruction connection problem'' error is encountered when changing a Teradata connection in the Query Builder | QAT-17696 |
| Change Connection | "Connection change error Reconstruction connection problem..." error is encountered when fully qualified object names are not used in the query and a connection is changed in Query Builder | QAT-17867 |
| Change Connection | "Object reference not set to an instance of an object. The connection cannot be changed" error is encountered when changing a Teradata connection in a reopened .tsm file | QAT-17872 |
| Change Connection | "Guid should contain 32 digits with 4 dashes (xxxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxx). The connection cannot be changed." error is encountered when changing the connection in a reopened query builder file containing a query and a subquery on a Teradata and DB2 z/OS connections | QAT-17991 |
| Change Connection | "Reconstruction connection problem'' error is encountered when changing an SAP ASE connection in the Query Builder | QAT-18113 |
| Change Connection | "Object reference not set to an instance of an object." error is encountered when changing a connection to a different data source with a user that does not have permission to see all objects as the first user (connection) and the user password is not saved | QAT-18254 |
| Change Connection | "Connection change error Reconstruction connection problem." error is encountered when fully qualified object names are not used in the query and an SAP ASE connection is changed in Query Builder | QAT-18110 |
| Data Comparison | Compare wizard generates a report with the wrong result set when comparing DATE data types on SQL Server and DB2 tables | QAT-17249 |
| Data Comparison | "InvalidCastException" error is encountered when generating a script to sync a DateTime2 datatype on SQL Server 2019 connection to Timestamp data type on DB2 z/OS connection | QAT-18357 |
| Data Grid | "Unknown column 'ROWNUM' in 'where clause'" error is encountered when retrieve data from the published snapshots on an Oracle connection | QAT-18366 |
| FTP Connections | "The negotiation of key exchange method has failed" error is encountered when connecting to an SFTP server | QAT-16741 |
| General | Toad Data Point becomes unresponsible when opening a Toad Visualization file | QAT-17520 |
| General | Query builder file cannot be saved after hovering the Menu bar options | QAT-17646 |
| General | The workbook file is not saved when the SAVE button is clicked in the Save As window | QAT-17106 |
| General | Toad Data Point closes unexpectedly when a query containing Common Table Expressions (CTE) and a LIMIT clause is run on a Vertica connection | QAT-17756 |
| Job Manager | "[Teradata Database] [2666] Invalid date supplied for..." error is encountered when a scheduled workbook containing a bind variable for a date datatype column is run on a Teradata connection | QAT-18124 |
| Job Manager | "Index was outside the bounds of the array" error is encountered when a scheduled task is set to be run on the last day of the month | QAT-17584 |
| Job Manager | The scheduled task disappears from the Job Manager window in the Task List tab when it is set to run only on the last day of the month | QAT-17585 |
| Join Visualization | The visualization under the Properties dialog does not follow changes made in the Diagram tab of Query Builder | QAT-17628 |
| Join Visualization | Venn diagram to analyze joined views in Query Builder is not displayed when the “Analyze join” button is clicked | QAT-17645 |
| Join Visualization | The query is changed when using the Venn diagram to analyze the Join and Automatically arrange tables button is clicked in the Query Builder | QAT-18153 |
| Object Explorer | Toad Data Point becomes unresponsible when expanding a database node in the Object Explorer panel on an SAP ASE connection | QAT-17509 |
| Pivot Grid | Date column values are displayed as Datetime values in an exported pivot grid file when the Date data type column is used for the Column Area | QAT-18075 |
| Pivot Grid | Data column values are improperly formatted in an exported pivot grid file when the Date data type column is used for the Data Area | QAT-18180 |
| Pivot Grid | Data column values are improperly formatted in an exported pivot grid file when the Date data type column is used for the Row Area | QAT-18232 |
| Pivot Grid | Pivot grid settings are not preserved when a DB2 z/OS connection is changed in the Pivot Grid tab | QAT-17826 |
| Publishing Wizard | Pivot Grid Excel report step is not published as a part of the published workbook | QAT-17410 |
| Publishing Wizard | "Can't find database object <Name_OfObject> " error is encountered in the Authentication field of the "Publish to Intelligence Central" window when publishing a View or Snapshot using a table alias on a DB2 z/OS connection | QAT-17639 |
| Publishing Wizard | "Quest.Toad.Exceptions.BaseException Identifier name '<folder name>' is too long" error is encountered when publishing a data set to a folder with a long name on Toad Intelligence Central | QAT-17776 |
| Publishing Wizard | "Error generating authentication info" error is encountered in the Authentication field of the "Publish to Intelligence Central" window when publishing a View or Snapshot using a table alias on a DB2 z/OS connection | QAT-17793 |
| Publishing Wizard | "ERROR:'(': Expecting: CROSS FULL INNER JOIN LEFT NATURAL ON RIGHT STRAIGHT_JOIN USING" error is encountered when publishing a view or snapshot from a Teradata connection | QAT-18148 |
| Publishing Wizard | "Object already exists” error is encountered in Publish Summary window when publishing an automation script or a workbook to the TIC folder which contains previously published automation scripts or workbooks starting with the same characters without overwriting existing files | QAT-18212 |
| Publishing Wizard | The workbook file is not republished when the “Publish” button is clicked in the “Publish to Toad Intelligence Central” window and the workbook's folder is deleted on Toad Intelligence Central | QAT-18252 |
| Publishing Wizard | "Error generating authentication info. Run the query before publishing to make sure there's no error" error is encountered in the Publish To Intelligence Central window when publishing as view or snapshot | QAT-18320 |
| Query Builder | "Implicit conversion from datatype VARCHAR to '<numeric user-defined type>' is not allowed. Use the CONVERT function to run this query" error is encountered when a query containing a WHERE clause for a numeric UDT column is run on an SAP ASE connection | QAT-17524 |
| Query Builder | Global Where and global Having clauses are duplicated when conditions are specified in separate parentheses on an SAP ASE connection | QAT-17516 |
| Query Builder | "Implicit conversion from datatype 'VARCHAR' to 'BIT' is not allowed. Use the CONVERT function to run this query" error is encountered when adding a WHERE clause to Boolean datatype through Query Builder on an SAP ASE connection | QAT-17519 |
| Query Builder | DateTime value is displayed in reverse in the Diagram tab in the Query Builder when editing a WHERE condition for a Datetime column on an SAP ASE connection | QAT-17525 |
| Query Builder | The default alias disappears under the WHERE clause when a custom alias is removed from the Diagram tab field | QAT-17546 |
| Query Builder | "[Teradata Database] [3535] A character string failed conversion to a numeric value." error is encountered when a query containing an IN statement with DATE data type value in the WHERE clause is run | QAT-17560 |
| Query Builder | The Field alias is not automatically populated when an aggregate function in the Query Builder’s Diagram tab is used | QAT-17589 |
| Query Builder | "Object reference not set to an instance of an object." error is encountered when adding an aggregate function to a calculated field through Query Builder | QAT-17590 |
| Query Builder | Avg(Distinct), Count(Distinct), Sum(Distinct) and Stddev_Samp aggregate functions are not present in the Diagram tab for INT data type on an SAP ASE connection | QAT-17593 |
| Query Builder | The calculated field column got a weird name for the field alias when adding an aggregated function | QAT-17630 |
| Query Builder | Queries with non-ANSI syntax are generated in the Query Builder for data sources without the "Convert from non-ANSI to ANSI syntax" option | QAT-17633 |
| Query Builder | Duplicated values for the DateTime data type when setting values from the "Where Condition" window on a Teradata connection | QAT-17641 |
| Query Builder | The Data Range tab is missing from the Where Condition window when the WHERE clause is deleted from a query and the Visualize Query button is clicked | QAT-17644 |
| Query Builder | Preselected values for IN and NOT IN operators are lost in the "Where Condition" window | QAT-17699 |
| Query Builder | "Implicit conversion from datatype 'VARCHAR' to '<numeric user-defined type>' is not allowed." error is encountered when adding a bind variable to a WHERE clause for any numeric UDT column on an SAP ASE connection | QAT-17700 |
| Query Builder | "Object reference not set to an instance of an object" error is encountered when adding a calculated field to the GROUP BY clause through Query Builder | QAT-17702 |
| Query Builder | "[Teradata Database] [3504] Selected non-aggregate values must be part of the associated group." error is encountered when a query containing an aggregate function for the calculated field with an alias is run | QAT-17727 |
| Query Builder | "[Teradata Database] [3939] There is a mismatch between the number of parameters specified and the number of parameters required." error is encountered when a query containing two bind variables with the same name is run on a Teradata connection | QAT-17737 |
| Query Builder | Aliases for calculated fields are used in the GROUP BY clause when generating a query through Query Builder on an SQL Server connection | QAT-17825 |
| Query Builder | Unselected "Use fully qualified object names" option is not applied when generating a query through Query Builder on an SAP ASE and DB2 z/OS connections | QAT-17865 |
| Query Builder | Wildcard characters are not included in the generated query when using Like Modifiers to search for a specified pattern in a Calculated field | QAT-17868 |
| Query Builder | Varchar type is displayed in the Bind Variables window for a DATE data type variable on a Teradata connection | QAT-17927 |
| Query Builder | Values for the Date datatype are displayed as timestamps in the Where Condition window on a Teradata connection | QAT-17988 |
| Query Builder | In the Where Condition window, the values for LIKE and NOT LIKE operators contain wildcards when the Visualize Query button is clicked in Query Builder | QAT-17992 |
| Query Builder | Calculated field names got the weird name in the Where condition window when the Visualize Query button is clicked in Query Builder | QAT-18000 |
| Query Builder | Calculated field names got the weird name in Diagram Grid when the Visualize Query button is clicked in Query Builder | QAT-18010 |
| Query Builder | "Domain error during explicit conversion of INT NULL value “ to a BIT field…" error is encountered when opening a Query Builder file with a query created on an SAP ASE connection | QAT-18023 |
| Query Builder | The subquery title got the weird name when in the Where Condition window, the "Subquery…" button is clicked | QAT-18029 |
| Query Builder | "[Teradata Database] [5628] Column <value> not found in <database.table>." error is encountered when generated query containing multiple values for a calculated field in the Where Condition window is run on a Teradata connection | QAT-18031 |
| Query Builder | Values for a DATE data type bind variables are formatted as timestamp values in the Bind Variable window | QAT-18049 |
| Query Visualization | Comments cannot be removed when the query is changed in Query Builder and the Visualize Query button is clicked | QAT-18058 |
| Query Visualization | "ERROR [42702] [IBM][DB2] SQL0203N A reference to column <column name> is ambiguous." error is encountered when a query is run after visualization on a DB2 z/OS connection | QAT-17513 |
| Query Visualization | "Incorrect syntax near '...' " error is encountered when a query containing a getdate() function in the WHERE clause is visualized and run on an SAP ASE connection | QAT-17518 |
| Query Visualization | The single quotes around the values for IN/NOT IN operators are removed the Visualize Query button is clicked in the Query Builder on a Teradata connection | QAT-17534 |
| Query Visualization | Single quotes around values for DATE datatype are added when the Visualize Query button is clicked in the Query Builder on Teradata and DB2 z/OS connections | QAT-17541 |
| Query Visualization | CASE expression in the GROUP BY clause disappears when the Visualize Query button is clicked in the Query Builder tab on a Teradata connection | QAT-17545 |
| Query Visualization | Additional parentheses are added in the WHERE clause when the Visualize Query button is clicked in the Query Builder | QAT-17551 |
| Query Visualization | The minus sign in front of the value for a number in the CASE expression is changed to ''unary_minus'' text when the Visualize Query button is clicked in the Query Builder tab | QAT-17586 |
| Query Visualization | The condition order as part of the JOIN statement is not changed when a query is visualized on a Teradata connection | QAT-17627 |
| Query Visualization | JOIN statement translates to a WHERE clause after visualizing a query containing a subquery with a WHERE clause | QAT-17636 |
| Query Visualization | "GROUP BY expressions must refer to column names." error is encountered when a query containing a calculated field in the GROUP BY clause is visualized and run | QAT-17690 |
| Query Visualization | Global Where Clause is created when a query containing table and view aliases in the WHERE clause is visualized on Teradata, DB2 z/OS, or SAP ASE connections | QAT-17937 |
| Query Visualization | Code format in Where clause is changed after visualization in Query Builder | QAT-17522 |
| Query Visualization | The name of the calculated field is changed to the table alias name after visualizing a query that contains a table that bears the same name as one of its columns | QAT-17629 |
| Query Visualization | The GROUP BY clause disappears from a query when the "Visualize Query" button is clicked on a Teradata connection | QAT-17649 |
| Query Visualization | The GROUP BY clause disappears from the Query tab output of the Query Builder after visualizing a query where numbers are used instead of column names in a GROUP BY clause | QAT-17685 |
| Query Visualization | Table alias will replace a value in WHERE condition if the alias name is the same as the value and the Visualize Query button is clicked in Query Builder | QAT-17695 |
| Query Visualization | "The query cannot be modeled" error is encountered in the Query Builder when a query containing a JOIN clause is visualized on Teradata, SAP ASE, and DB2 z/OS connections | QAT-17531 |
| Query Visualization | A column name is changed to the name of the table alias in a WHERE condition after visualization of a query containing a table that bears the same name as one of its columns | QAT-17544 |
| Script Generation | The Create script for macros is not generated in editor when selecting “Editor as Script” option on a Teradata connection | QAT-18438 |
| Script Results | “Connection does not exist“ error is encountered when the users name for a Netezza connection contains spaces or non-alphanumeric characters and a query is run | QAT-18225 |
| Script Results | "Implicit conversion from datatype 'VARCHAR' to '<numeric user-defined type>' is not allowed. Use the CONVERT function to run this query." error is encountered when a query containing the UNION operator and numeric UDT column on an SAP ASE connection is run | QAT-17514 |
| Script Results | "syntax error at or near “$1”;Error while executing the query" error is encountered when a query containing the dollar sign ($) for a variable is run on a PostgreSQL connection | QAT-17470 |
| Script Results | "Incorrect syntax near CROSS" error is encountered when a query containing a CROSS JOIN clause is run on an SAP ASE connection | QAT-17592 |
| SQL Editor | Toolbar icons are not shown when the SQL Editor is open | QAT-17684 |
| Workbook | Toad Workbook becomes unresponsible when opening a workbook file that contains subqueries, and the connection dialog is canceled | QAT-18063 |
| Workbook | An additional subquery is created in Query Builder when a query contains the UNION operator and a workbook connection is changed | QAT-17267 |
| Workbook | "Error during cloning workflow" error is encountered when cloning a workflow containing a Publish step | QAT-17398 |
| Workbook | "Attempt to locate entry in sysdatabases for database <host> by name failed - no entry found under that name. Make sure that name is entered properly." error is encountered when changing the WHERE clause in the previously saved .twf file, and the SAP ASE connection is used | QAT-17643 |
| Workbook | Diagram and Query tabs are empty when reopening a workbook file containing a query with JOIN and WHERE clauses on the DateTime data type column on an SAP ASE connection | QAT-17647 |
| Workbook | "[Teradata Database] [3706] Syntax error: expected something between the word 'Workbook_WF1_' and '-'." error is encountered when a Workflow containing a Toad View for a Teradata connection is run | QAT-17653 |
| Workbook | The name of the calculated column is changed to ''Calculated'' in the Diagram tab when opening a workbook file | QAT-17688 |
| Workbook | A Cross-Connection is created in Query Builder when changing the query containing the UNION operator, and then changing a Teradata connection in Workbook | QAT-17689 |
| Workbook | The Query tab disappears from Query Builder when reopening a workbook file containing a query with a UNION operator on a Teradata connection | QAT-17692 |
| Workbook | UNION operator and Subquery are duplicated in the Workbook Query Builder after changing a DB2 Z/OS direct connection | QAT-17777 |
| Workbook | The UNION operator and the following SELECT statement are missing in reopened workbook file when a Teradata connection is changed | QAT-17934 |
| Workbook | Toad Workbook becomes unresponsible when opening a Query Builder file containing a subquery on a Teradata connection | QAT-17941 |
| Workbook | Workflow never finishes when the connection of the workflow is changed | QAT-17943 |
| Workbook | "Access denied for user '<power user>' cannot create non-secured folder." error is encountered when Power Users publish a workbook to the "No folder assigned" folder on Toad Intelligence Central | QAT-18003 |
| Workbook | "Need more information to connect" pop-up window is encountered in Toad Workbook when changing a Teradata connection and then clicking on the ‘Edit Sample’ link in a Transform and Cleanse step | QAT-18020 |
| Workbook | The Edit Sample link is not clickable on Transform and Cleanse step in opened workbook file when a workflow is created on a Teradata connection | QAT-18021 |
| Workbook | "Object reference not set to an instance of an object." error is encountered when a workbook containing a Pivot Excel step is run | QAT-18024 |
| Workbook | "Can't convert the imported data to the specified data types" error is encountered when publishing a workbook containing a Pivot Grid step with JOIN clause on a Teradata connection | QAT-18118 |
| Workbook | Timestamp suffix as part of the report names is not applied for Pivot grid, Transform and Cleanse, and Dimensional View steps in a workbook if the Overwrite option is checked | QAT-18119 |
| Workbook | "Cannot rename a sheet to the same name as existing sheet. Export is canceled" error is encountered when a workbook containing multiple Excel Pivot View steps for exporting data into a single Excel file with different worksheet names is run | QAT-18154 |
| Workbook | "Pivot cannot be published: Duplicate column name 'oh_'" error is encountered when a workbook containing a Pivot Excel step for a Teradata connection is run | QAT-18166 |
| Workbook | Date values for bind variables are not saved in the workbook's workflows when reopening a workbook file | QAT-18168 |
| Workbook | "Failed to change connection. This Query Builder uses some objects that are not available in your connection" error is encountered when the workbook file contains a query with the UNION operator and a Teradata connection is changed | QAT-18169 |
| Workbook | A Teradata connection cannot be changed in the workbook's workflow that contains a query and a subquery when disconnecting from a previous connection and connecting to a new one | QAT-18170 |
| Workbook | The sheets order in the exported Excel file doesn't follow the order of the reports for created Pivot Grids in the workbook workflow | QAT-18172 |
| Workbook | "Remove the table from query" error is encountered in a workbook that includes a query that contains two or more SELECT statements when each SELECT statement is run separately | QAT-18175 |
| Workbook | "Key cannot be null. Parameter name: key" error is encountered in the workbook when visualizing a query in Query Builder | QAT-18198 |
| Workbook | "Can't convert the imported data to the specified data types" error is encountered when a workbook file containing a pivot grid with added grand totals for each column/row is run | QAT-18213 |
| Workbook | "Connection Not connected is not available. Select a working connection for this workflow." error is encountered when cloning a workflow containing a publish step | QAT-18441 |
| Workbook | Toad Workbook becomes unresponsible when opening a workbook file containing a subquery or a UNION operator on a Microsoft SQL Azure connection | QAT-18287 |
Enhancements in 6.1
-
The QUALIFY clause with the ROW_NUMBER function replaced the TOP n operator when generating and visualizing a query through a Query Builder on a Teradata connection. This approach removes the restrictions that come with using the TOP n operator. Queries with the TOP n operator that are not subject to any limitations can still be successfully run in Toad Data Point.