Toad Intelligence Central on Quest.com
Toad Intelligence Central Community on ToadWorld
Product Information on Quest.com
Toad Data Point Release Notes and Product Guides
Toad Data Point v4.3 is now available
Get more from Toad Data Point... with onsite training
Toad™ Data Point is a multi-platform data preparation tool that’s built for anyone who needs to access data from multiple sources, quickly integrate and prepare data to produce datasets and reports for analysis. It dramatically simplifies data access, writing SQL queries and data preparation – all from a single tool and without needing to be a SQL expert. With Toad, you can:
Use these links below to learn more about the most popular Toad Data Point topics!
The better a problem is described, the better the assistance tends to be.
In order to better assist with your issue at hand, please include the following information in your initial post:
- Product, Version, and relevant environment details.
- Include a screenshot of the problem
- Describe the problem fully. What result was expected?
- Can the issue be created on demand or is it intermittent?
- If the problem can be generated faithfully, what are the exact steps to recreate the problem?
- Any other pertinent information (see below)
Create Support Bundles
You can create a support bundle and send it to Dell Support or to the Toad Data Point community Web site (peer-to-peer support). The support bundle provides information (about your application and the database) that is used to help troubleshoot problems.
Select Help | Support Bundle. It may take time for Toad to generate the support bundle depending on your system configuration.The file name of the generated support bundle is ToadSupportBundleToad Data Point.zip.
Create Support Bundle for a SQL Query Issue
If your issue is a SQL query or cross-connection query issue, it is helpful if additional log files are included in the support bundle. These log files are automatically included if you generate a support bundle immediately after executing the query in either the Editor or Query Builder.
Use the following procedure to ensure that the SQL log files are generated and included in the support bundle. These additional log files (proxy.log located in the DataHubSupportBundle.zip and SQLAnalyze.log) are important to assist Support in troubleshooting the issue.
For issues related to SQL or cross-connection query optimization, use the following procedure as well. These logs are also helpful for optimization issues.
To create a support bundle for a SQL query or cross-connection query issue
In the Editor or Query Builder, reproduce the error or issue.
After reproducing the error, immediately select Help | Support Bundle to generate a support bundle.
Toad asks if you want to log the row count for each table used in the query. If you select Yes, Toad determines the size of each table used in the query. This adds additional time to the generation process, but also provides additional information about your issue.
When Toad is finished generating the support bundle, attach it.
Note: For best results, always send the entire support bundle.
*Note: Please refrain from including private data in your posts
Be as thorough as you can with the provided info. We will reply to you as quick as possible.
We are glad to assist you.
Latest Release Information:
This announcement includes information on our latest releases, links to our downloads and documentation and overview of new features. This way you can stay as informed as possible:
- What’s New Section (why they would want to pay attention to this new version)
- Link to Download & Documentation
- Link to Trial
- Overview of new feature(s) (with link to the release notes)
Top 5 Knowledge Base Articles:
On this post, you can find our top trending knowledge articles that other customers are inquiring about and popular solutions.
This month’s Top Knowledge Base Articles
1. This month’s Top Knowledge Base ArticlesVideo - Making Effective Use of Data with Toad Data Point (195645)
2. Common Oracle connection problems (7712)
3. Error, "ORA-12170: TNS:Connect timeout occurred" when connecting to Oracle (105610)
4. Error connecting to database after installing on Windows 64-Bit OS: "ORA-12154" (12495)
5. "ERROR  [IBM] SQL30081N A communication error has been detected." when connecting to DB2 (47041)
Feel free to browse them. Remember to sign in to your account to view.
I have a cross-connection query that queries a very large file (file_a) and an Excel spreadsheet (file_b). The where clause selects just a few rows from file_a. A simple join runs quickly. However, I want to do a left join so that I get all of my selected file_a rows, plus whatever happens to match with file_b. This takes forever to run. Here is the relevant portion of the SQL: FROM `SFMRT (MSNMEDSCHMIS), UWPROD`.UWPROD.DETAIL_PAYROLL_PJN_TRANS file_a LEFT OUTER JOIN `fy 18 forward summary`.AutoRange_fy_18_forward_summary file_b ON (file_a.EMPLOYEE_ID = file_b.`EMPL ID`) WHERE (file_a.SFS_BUSINESS_UNIT = 'UWMSN') AND (file_a.SFS_FISCAL_YEAR = '2018') AND (file_a.SFS_DEPTID IN ('530311', '530312', '530313') OR file_a.PROJECT_ID = 'AAB7574') AND (file_a.SFS_ACCOUNT LIKE '10%') Quest tells me that Toad is set up to obtain all rows from file_a, all rows from file_b, and then join the two sets locally. Since file_a is very large, this explains my experience. My work-around is to first run a query on file_a and save it to Excel. Then I join the the file_a results with file_b.. Does anyone out there have a better solution? I would rather not have to export to excel and re-import. I strongly recommend that Quest makes their cross-connection query smarter to handle situations like this. Thanks to everyone for your help.
I am using version 4.3 Base Edition of Toad Data Point and trying to create automation in it. I have used different versions of Toad Data point in the past and never had this issue before. I can create small automations here on this version but when it comes to creating complex automation, the automation file gets corrupted and can no longer open it in the toad. I open the .tas file in the notepad to see the issue and found that there is unexpected end to the XML file - The XML file is partial. Is this an issue with this particular version? or there is a setting that needs to be updated?