Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 442 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Import/Export
Is there any way, inside SQL Developer to save an import or export "specification", i.e. a group of settings that you can reuse for the same operation over and over again? This would be something along the lines of a data pump parameter file. I'm familiar with data pump (I don't want to move data between databases) and the current import/export features and I've not seen this anywhere.
Whenever you walk through an import or export operation you have to answer a whole bunch (ok, quite a few) of questions and it would be really nice if you could answer these questions, save your answers and then reuse/modify your answers until you get exactly what you want. I find myself going through the procedure about 4-5 times on imports until I get it just right, and have to answer all the questions all the way through each time.
Don't get me wrong, I really appreciate the fact that import/export have been made relatively easy with the tools SQL Developer provides. It just seems that it would be pretty trivial to save a group of settings and then recall them if you wanted to reuse them.
Does anyone else experience the same thing? Maybe I'm just doing it wrong.
Sincerely curious,
Earl
Best Answer
-
We added just that feature for Imports in 4.1
Click the 'save state' button to record your import settings (an import from Excel or CSV)
then next time you do an import -
click the 'Restore State' button
This file can also be used to script an import using the SDCLI program (it's a command line interface for SQL Developer to run formats, exports, imports, cloud uploads, unit tests, etc)
For exports - if you use the cart to do your export, you can save the settings for that too.
Answers
-
We added just that feature for Imports in 4.1
Click the 'save state' button to record your import settings (an import from Excel or CSV)
then next time you do an import -
click the 'Restore State' button
This file can also be used to script an import using the SDCLI program (it's a command line interface for SQL Developer to run formats, exports, imports, cloud uploads, unit tests, etc)
For exports - if you use the cart to do your export, you can save the settings for that too.
-
Amazing!! Thank you so much. Now I just need to get 4.1.