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:

  • Access almost any source from a single tool
  • Visually drag and drop to create SQL queries
  • Profile, transform and cleanse data easily
  • Automate frequent reporting tasks

Use these links below to learn more about the most popular Toad Data Point topics!


Getting Started



Mastering
Connectivity

Writing
Queries

Import/Export


Automation

Community Discussion

Danny Torres
Follow / 14 Sep 2016 at 7:04pm / Toad Data Point
Latest post by on 10 May 2017 at 6:59pm

How to get the most out of this forum – Best practices for what information...

Expand content
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...

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)

-          http://documents.software.dell.com/toad-data-point/4.0/release-notes/release-notes/new-features

 -          Link to Download & Documentation

-          https://support.software.dell.com/toad-data-point/4.0

-          Link to Trial

-          https://software.dell.com/register/54955/

 -          Overview of new feature(s) (with link to the release notes)

http://documents.software.dell.com/toad-data-point/4.0/release-notes/release-notes/new-features

http://documents.software.dell.com/toad-data-point/4.0/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)

https://support.software.dell.com/toad-data-point/kb/195645

 2. Common Oracle connection problems (7712)

https://support.software.dell.com/toad-data-point/kb/7712

 3. Error, "ORA-12170: TNS:Connect timeout occurred" when connecting to Oracle (105610)

https://support.software.dell.com/toad-data-point/kb/105610

 4. Error connecting to database after installing on Windows 64-Bit OS: "ORA-12154" (12495)

https://support.software.dell.com/toad-data-point/kb/12495

 5. "ERROR [08001] [IBM] SQL30081N A communication error has been detected." when connecting to DB2 (47041)

https://support.software.dell.com/toad-data-point/kb/47041

Feel free to browse them. Remember to sign in to your account to view.

 

7083 4 / Create an account to join the discussion.
wlemery
Follow / 24 May 2018 at 9:26pm / Toad Data Point

cross-connection left outer join query efficiency

Expand content
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...

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.

2 0 / Create an account to join the discussion.
amlloyd
Follow / 24 May 2018 at 5:49pm / Toad Data Point

[BUG?] Attempting to edit a stored procedure in SQL Server via TDP...

Expand content
Simply selected a stored procedure in sql server 2012 or 2016, and clicked the Edit button. This error is thrown. Persisted after reboot. TDP v4.3.0.718. System.NotImplementedException The method or...

Simply selected a stored procedure in sql server 2012 or 2016, and clicked the Edit button. This error is thrown. Persisted after reboot. TDP v4.3.0.718. 

System.NotImplementedException
The method or operation is not implemented.
Stack Trace:
at DevExpress.XtraEditors.Controls.EditorButtonCollection.System.Collections.Generic.ICollection<DevExpress.XtraEditors.Controls.EditorButton>.CopyTo(EditorButton[] array, Int32 arrayIndex)
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Quest.Toad.SqlServer.Doe.Common.DataTypes.Controls.DataTypeRepositoryItem.RegisterForGrid(ToadGridControl toadGrid, Boolean bForceReplace, IConnection iconnection, String sDatabaseName, EnumStandardTypeListType enumStandardTypeListType, Boolean bDoNotGenerateText)
at Quest.Toad.SqlServer.Doe.Common.Parameters.ParametersControl.InitializeComponentOwn()
at Quest.Toad.SqlServer.Doe.StoredProcs.StoredProcEditForm.InitializeComponent()
at Quest.Toad.SqlServer.Doe.StoredProcs.StoredProcEditForm..ctor()

7 0 / Create an account to join the discussion.