End Users use Automation
I would like to have a way for my end users to kick off an Automation script so they can run their own reports when they want without having TDA installed on thier pcs.
Do you have an idea for an improvement to Toad for Data Analysts? We want to hear it!
Do you want to help choose the best ideas? Then cast your vote!
Idea Pond is where you can submit your idea for an improvement, enhancement, or new feature for Toad for Data Analysts. Your idea will be posted here for others to view and vote on, and for the TDA development team to review. You can also vote and comment on the ideas submitted by others.
Idea Pond is for enhancements only. If you want to report a bug, please contact Quest Support.
To get started, simply register (sign in), and then submit your ideas. Or browse the FAQs to find out more about TDA’s Idea Pond.
I would like to have a way for my end users to kick off an Automation script so they can run their own reports when they want without having TDA installed on thier pcs.
I would like to have TDA fix all of my automation tasks when I upgrade TDA. I have hundreds of scripts and it is too time consuming to change the paths manually. Same goes for my passwords. We have to change our passwords every three months. So between these two things the scheduled tasks take some maintainance.
I would like to have a condensed version of the schema browser available while on the editor window. For example: Take the "Left Hand window" from the schema browser and present it like the Project Manager window. Take the Right Hand and present it like the "messages/data grid/auto trace/etc..." at the bottom of the editor. This would allow browsing the schema without leaving the code.
I would like to see an Automation Server program created. Automation has been pushed as one of the major features of TDA for some time now (as well it should be, it's pretty spectacular!), but the limitations of the Windows Scheduled Tasks system leaves quite a bit to be desired. What I would like to see is a stand-alone program that can act as an automation server - this could either be installed on a real server, ...more »
I would like to see an Automation Server program created.
Automation has been pushed as one of the major features of TDA for some time now (as well it should be, it's pretty spectacular!), but the limitations of the Windows Scheduled Tasks system leaves quite a bit to be desired.
What I would like to see is a stand-alone program that can act as an automation server - this could either be installed on a real server, or a spare PC - that acts to run and manage all automation tasks. It would be specifically designed for far better error handling that TDA currently has when TDA encounters an unrelated error at batch launch (ex.: Sysbase component crashes creating an error dialog box when an automation task against Oracle launches, preventing the automation task from finishing until the error box is cleared manually). It would also be designed from the ground-up to easily manage scripts and directories, having options to default to using fully qualified paths on both local and network resources.
It would migrate scripts from one version of itself to another seamlessly (there's no reason why this couldn't be done).
There's a ton of ideas, but those are my major gripes at the moment :)
« less full details »
When importing data into an SQL Server (or any server I imagine) it would be best if the field size matched the originating DB field size. Perhaps a different work-around is to have a setting where a user can set a percentage above what the application decides what the size should be. It seems that the size is based on a preview of data and many times is too small for the actual import.
I like the new Local Storage in TDA 3.0 Pro. But I would like to have the storage server on the network so our team could share the data.
When closing down at the end of the day TDA seems to take longer to shutdown than my other applications (Outlook, IE, Chrome, Business Objects clients, etc). I don't know why TDA takes longer, but I suspect that it has to close out its database connections. I'm sure there are opportunities for improving the shutdown process.
I want to be able to save a single subreport and give it a file name. Then have the ability to add this subreport into multiple reports.
Also want to be able to update a subreport in one place and globally update all Master reports that currently use it.
Add the ability to change the Existing File "Add Date/Time Suffix to filename" so that we can either change the order from yyyy-mm-dd to mm-dd-yyyy or we can add a +/- to the current date. For example, if I run a report today, and it was for data up through two days ago, I would like the ability to adjust the date suffix to state the date 2 days ago.
When double clicking a field, the editor sends that to the end of the line rather than the point at which the cursor is place. It should go to where the cursor is. Also, when enlarging the calculation editor, the fields are no longer available. The whole calculation editor should probably be redeveloped.
Have a system wide area for variables that can be used in any script/query. This would allow easy changes to many areas without having to edit many scripts/reports. Even some of the most elegant queries can't do what is sometimes needed. I just would like to tell the system what the value is and be able to switch it easily.
Welcome to the Toad for Data Analysts Idea Pond!
It's easy to submit an idea. Just click the New Idea button. The Toad for Data Analysts development team wants to hear from you.
We are interested in your ideas. And the most popular and reasonable improvement ideas are likely to be addressed in future releases. So get involved. Let us know what you think.
I would like to have the ability to save my passwords in a password manager like KeePass. This would allow a user to save their passwords in a common repository and improve the "Save Passwords" feature.
I would like to be able to use the connection "Color" to set the background color of the editor window. In addition to the "Color status bar" it would be a much more visible indicator.
have a native postgres Connection (not ODBC).
Current issues with using an ODBC are :
Creation scripts for Views only display the select and "table_name" as the from statement and no where
Speed
see table/column comments (remarks)
keep search path
would love for the formater not to stop working once it finds a postgres cast
IE
SELECT '01/01/2012'::date
the formater get lost in the ::
SELECT '01/01/2012' : :date
Want to be able to select a cell and copy its format properties and then select an/other cell(s) in the same report and any subreports to copy font, colour and alinement properties.
Right now, with the exception of the row_count variable, there are no default, or built-in variables in TDA that I have found. Some ideas of variables that would be very useful: - A default "Current date" variable pulled from system time. Yes, we can define this ourselves, but having one we can just reference when we don't need anything specific would be great. Same goes for a default "Time" variable. - Variables ...more »
Right now, with the exception of the row_count variable, there are no default, or built-in variables in TDA that I have found.
Some ideas of variables that would be very useful:
- A default "Current date" variable pulled from system time. Yes, we can define this ourselves, but having one we can just reference when we don't need anything specific would be great. Same goes for a default "Time" variable.
- Variables that return the fully qualified paths of any items used in the automation script, including the script itself.
- A Variable to return the name of the exported file(s) from the automation script. Currently there is no way to capture this.
I'm sure there are more I will think of
« less full details »
I would like to see a Native TeraData Connection. (Not have to use ODBC). It would have all of the expected Toad features such as bulk copy for import, Query Builder, etc.
I would like to see support for tables containing fields with MDSYS.SDO_GEOMETRY data types. Without this support I am unable to use any of the utilities in TDA to view or update ORACLE tables containing fields with this data type. We then have to work with our Software Developers to create updatable views of the tables leaving out these fields. This only allows me to update or insert manually one field at a time. We ...more »
I would like to see support for tables containing fields with MDSYS.SDO_GEOMETRY data types. Without this support I am unable to use any of the utilities in TDA to view or update ORACLE tables containing fields with this data type. We then have to work with our Software Developers to create updatable views of the tables leaving out these fields. This only allows me to update or insert manually one field at a time. We have list or data files we would like to use as a mechanism to update or add to tables.
« less full details »
Social Web