dbDBCraftDocs
Overview
IGetting started
About this guideWhat DBCraft AI Studio isInstallationActivating your licenceConnecting to a databaseA tour of the workspace
IIThe workspace
The menu barThe icon toolbarThe connection chip and container switcherThe docking railThe left panel (cluster drawer)The bottom dockThe status barThe command paletteExtra windows
IIIDevelopment modules
SQL EditorResults grid and data editingGraphsObject Browser and Object ViewerPL/SQL DebuggerUnit Test ManagerReports
IVDBA modules
Schema ToolsVersion HistorySession BrowserDBA Dashboards (Health)Storage BrowserPerformance Profiler and SQL OptimizerIndex AdvisorER Diagram ModelerAutomation and JobsLoad Tester
VTools and utilities
SQL TerminalAI AssistantExport Tables and Import Tables
VIConfiguration and reference
Settings referenceKeyboard shortcutsLicence managementLogging, diagnostics and bug reportsSecurity and data handlingTroubleshootingFile and folder locationsBackend API referenceGlossary
Documentation/Tools and utilities
Chapter 35

Export Tables and Import Tables

Two wizards for moving table structure and data as a portable .sql file. Both are Oracle-only and open from Database → Export/Import Tables…, the toolbar, or the command palette.

#35.1Export Tables

Left — what to export

  • Schema — defaults to your own.
  • Filter tables… and the table checklist, with All / None links and a selected / total counter.

Right — how to export

OptionChoices
What to exportStructure + Data (default) · Structure only · Data only
Include objectsConstraints, Indexes, Triggers, Comments (all on by default), Grants (off). Disabled when exporting data only.
Where clauseAn optional row filter applied to every exported table, e.g. department_id = 10. Disabled when exporting structure only.

Export builds the script server-side (table DDL from the data dictionary plus INSERT statements) and downloads export_<SCHEMA>_<date>.sql. When it finishes you get a summary — how many tables, how many rows, how long — and any per-table errors are listed individually.

#35.2Import Tables

  1. Import file (.sql export) — choose a file produced by Export Tables.
  2. If a table already exists — five behaviours:
OptionBehaviour
Skip existing tablesExisting tables are kept as-is; their CREATE statements are skipped.
Append dataExisting tables are kept; imported rows are added.
Truncate before import⚠️ Existing rows are removed before the imported rows are inserted.
Replace (drop & recreate)⚠️ Existing tables are dropped and recreated from the file.
Create only (fail if exists)An error is reported when a table already exists.
  1. Commit — a single transaction (commit at end), or every 100 / 1000 / 10 000 rows.
  2. Continue on error — on by default; the import keeps going past a failing statement.

Import runs the script and reports statements executed, rows inserted, skipped, failed and elapsed time. A per-table results table shows whether each table was Created or already Existed, the row count (with failed rows in brackets), and any error. Show execution log expands the full log.