The following is a list of issues addressed and enhancements implemented in this release of Toad Data Studio:
Resolved Issues in 1.1
| Feature | Resolved Issue / Enhancement | Defect ID |
|---|---|---|
| Automation | “There is no connection description, Connection failed” error is encountered when running script with an embedded .tct file | QAT-19438 |
| Automation | "Could not resolve connection for TRL: sqlserver<SQL Azure connection URL> error is encountered when running an automation script containing an Export or Import template | QAT-16883 |
| Connection Manager | GUID number is encountered in the name of the SQL Azure connection when editing the import template | QAT-18135 |
| Export Wizard | Duplicated data in exported files for Date, DateTime, and Timestamp datatypes on an Oracle connection | QAT-18726 |
The following is a list of issues known to exist at the time of this release.
| Feature | Known Issue | Defect ID |
|---|---|---|
| Connection |
The issue occurs when the 'Create New Connection' button is clicked and the scaling is set to 125%: Glitches are present, and the Group display is missing. Workaround Reduce scaling to 100%. This option can be found in the Windows Display settings. |
IMTDS-2455 |
| Schema Compare |
Loading of objects in the Schema Compare wizard takes too long for Oracle data source |
IMTDS-1194 |
| Source Control | The loading of objects, refreshing Action Center, and committing changes to the repository for an Oracle database takes too long. |
IMTDS-1189 |
| Source Control | Unable to link database to Source Control when using an RSA key with a GitHub repository. |
IMTDS-1196 |
| Object Explorer | Toad Data Studio closes unexpectedly when navigating between tables with XML data in Object Explorer on an Oracle connection. |
IMTDS-1698 |
| Results (Object Explorer) | Toad Data Studio closes unexpectedly after editing and saving XML data in Oracle. |
IMTDS-1625 |
| Results | "System.Runtime.InteropServices.COMException" error is encountered when the Explain Plan tab is selected from the Results section on a PostgreSQL connection. |
IMTDS-1478 |
| Results(XML/JSON Editor) | Unable to save changes in XML entry after switching to Column tab in the Data grid. |
IMTDS-1664 |
The following is a list of third party issues known to exist at the time of release of Toad Data Studio 1.1.
| Feature | Platform | Known Issue | ID |
|---|---|---|---|
|
Connect to Database |
DB2 | If you are using the DB2 Client version 9.5, 9.7, or 10.1 in a Windows 8 or Windows Server 2012 environment, follow the instructions in IBM DB2 Technote 1618434: http://www-01.ibm.com/support/docview.wss?uid=swg21618434. | N/A |
|
Connect to Database |
Excel |
The following error is encountered when attempting to create a connection to an extremely large Excel file (for example, 20 MB or larger): "Microsoft. ODBC Excel Driver. System resource exceeded." For more information, see https://forums.toadworld.com/t/error-in-importing-large-excel-files/26457/9. Workaround: Convert the Excel file to a CSV file. |
N/A |
|
Connect to Database |
Oracle
|
(Oracle 10.2.0.1 client only) Attempting to connect to an Oracle database From Toad using the 10.2.0.1 Oracle client results in the following error: “ORA-24909: call in progress. Current operation canceled”. This is a known issue with this Oracle client. Workaround: Upgrade your Oracle client to a later version and connect to the Oracle database. |
N/A
|
|
Connect to Database |
Oracle 11 only |
When connecting to Oracle 11, you must enter the password in the proper case because passwords are case-sensitive. | N/A |
|
Data |
ODBC- DB2 z/OS |
In compatibility mode, the ODBC driver does not return enough information for the CommandBuilder to correctly generate update or insert statements. |
N/A |
| Editor | Teradata |
If you experience performance issues using a Teradata connection, especially when using code completion in the Editor, use the Teradata Non-X views (instead of the X views). To use Teradata Non-X views
|
N/A |
|
Export Wizard/ |
All |
To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. |
N/A |
|
Export Wizard/ |
Excel | 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 |
| Import Wizard | DB2 | When importing data using the Add Query feature and selecting a Single new table, TIMESTAMP data types are mapped to DATETIME data types. | N/A |
| Object Explorer | Cloudera Impala |
A view is represented as a table in Impala, so views display as tables in Toad. For more information, see https://issues.cloudera.org/browse/IMPALA-1697. |
N/A |
| Object Explorer/ Database Explorer | Teradata |
You may experience issues if you attempt to view object details and your Teradata .Net Data Provider version does not correspond to the Teradata database version to which you are connecting. Issues include:
Workaround: Install the Teradata .Net Data Provider version that corresponds with the Teradata database version to which you are connecting. For example, if connecting to Teradata database version 14, use Teradata .Net Data Provider 14.11. |
N/A |
| Object Explorer/ Database Explorer | DB2 iSeries | The primary Key column of an iSeries table displays as Nullable in the Database Explorer even though the Not Null checkbox was not selected when creating the table. | N/A |
|
Query Builder |
Sybase ASE |
Cross-connection query: Sybase has difficulty dealing with numeric literals in queries. You may encounter the following error: Implicit conversion from datatype 'CHAR' to 'INT' is not allowed. Use the CONVERT function to run this query. when attempting to execute a cross-connection query such as: Select * from table where numeric_column = 50 Work-around: Change the query to something similar to the following using the cast function: Select * from table where numeric_column = CAST(50 AS SIGNED) |
ST96868 |
| Query Builder | Cassandra and Excel/Access |
Cross-connection query: A query between Cassandra and either Excel 2010 or Access 2010 might fail to execute and display a lost-connection error. Workaround: Upgrade to Excel 2013 or Access 2013 (or later). |
N/A |
The Toad release package contains the following products:
See the Toad Data Studio Installation Guide for more information.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
