Import/Export data - Toad for SQL Server - Toad World

Do you have an idea to improve or add a feature? We want to hear it!  Idea Pond is where you can tell the development team what you want, and tell us how important it is by submitting, voting, and commenting on ideas. Just sign in and click the "Submit New Idea" button to submit your idea.

Idea Pond is just for submitting enhancement suggestions. If you need help or found a bug, please contact Quest's Product Support. You can also join our forums for assistance. See our FAQ for more information about Idea Pond.

Import/Export data

Follow / 16 Mar 2017 at 8:48pm

Export Data Split to multiple Files

We use TOAD for almost everything at our company and a huge time saver would be the ability to specify a split number on an export to excel/csv. For example, my query produces 100,000 Rows and I select Export to Excel, I would like to specify a split...
0 / Active
Follow / 2 Jul 2015 at 5:29am

DDl Export

It would be fantastic to have a option to script all DDL's as individual files. Better yet, to have the option of scripting to individual files and then the utility dividing these into separate subdirs on the file system according to ddl type. ...
0 / Active
Follow / 14 Feb 2014 at 10:34pm

Import Utility

It would be very nice to be able to use the Import utility and choose where you wanted to do straight insert or if the row exists to update the row data. So the import would be an insert and or update utility.
0 / Active
Follow / 23 Jan 2014 at 1:08am

Data Import Wizard: Select Target Page - Allow addition of extra columns manuall...

Often when importing data from a customer, they do not include a key column in the raw data source. When running the import script, I want to include a new identity column that will be the primary key for the table, however the current import wizard...
0 / Active
Follow / 31 Oct 2013 at 3:22am

Please stop including Timestamp datatypes in the default column selections

When generating Export to SQL Insert statements the default field selections always include the timestamp datatype column by default, but if included the script will ALWAYS fail. I realize that for other types of exports (to Excel, etc) that you may...
0 / Active