Create Dump Dialog Help
This wizard serves to create a database dump. Valentina studio uses the same wizard to create a dump for different database engines. If some database provides additional dump options, the wizard shows them on the separate page.
Objects
If the dump wizard was called for the table or schema you can select few items that will be dumped.
The list filter is available only in the Pro version.
Dump Type
On this page, you should define the type and content of output data.
Excel 1997-2004 (.xls) – If selected, then dump will be created in XLS format.
Excel (.xlsx) – If selected, then dump will be created in XLSX format.
HTML – If selected, then dump will be created in
HTML format.
JSON – If selected, then dump will be created in JSON format.
SQL – If selected, then dump will contains SQL quires.
XML – If selected, then dump will be created in XML format.
Structure Only – If selected, then the dump will contain information only about database structure.
Structure And Records – If selected, then the dump will contain the information about the database structure and all data in the tables.
Records Only – If selected, then the dump will contain only data from tables.
Valentina dump formats:
PostgreSQL dump formats:
Custom – Create custom-format archive.
Directory – Create a directory with one file for each table and blob being dumped, plus a so-called Table of Contents file describing the dumped objects in a machine-readable format.
Tar – Create a tar-format archive.
Options
Database engines provide additional dump options:
PostgreSQL dump options:
Options: Queries
Include CREATE DATABASE statement – If ON then the CREATE DATABASE statement will be added to the dump.
Clean before restore – Clean (drop) database objects prior to outputting the commands for creating them.
Options: Save
Owner – Dump commands to set ownership of objects.
Privilege – Dump of access privileges.
Tablespace – Dump commands to select tablespaces.
Unlogged table data – Dump the contents of unlogged tables.
Options: Misc
Disable triggers – Include commands to temporarily disable triggers on the target tables while the data is reloaded.
Disable '$' quoting – Disable the use of dollar quoting for function bodies.
Use SET SESSION AUTHORIZATION – USE SQL-standard SET SESSION AUTHORIZATION commands instead of ALTER OWNER commands to determine object ownership.
With OID's – Dump object identifiers (OIDs) as part of the data for every table.
Verbose – Output detailed object comments and start/stop times to the dump file, and progress messages to standard error.
Force double quotes on identifiers – Force quoting of all identifiers.
Dump utility version – version of the pg_dump to create a dump. The drop-down menu allows the user to manage versions of the pg_dump utility. Detailed description of version management can be found here.
MySQL dump options:
Include CREATE DATABASE statement – If ON then the CREATE DATABASE statement will be added to the dump.
Drop before restore – Clean (drop) database objects prior to outputting the commands for creating them.
Lock tables for read – Add commands to lock tables to dump. Only the session that holds the lock can access the table.
Surround the INSERT statements with statements to disable and enable keys – Disable keys before inserting records.
Perform inserts in transaction – Add BEGIN/COMMIT statements for records of each dumped table.
Multiple rows in INSERT statement – Place multiple data rows in each INSERT statement. It makes dump loading faster.
(INSERT INTO TABLE_NAME (column_name, ...) VALUES ( ...row1... ), ( ...row2... ) )
Write REPLACE statements rather than INSERT statements – REPLACE works exactly like INSERT, except that if an old row in the table has the same value as a new row for a PRIMARY KEY or a UNIQUE index, the old row is deleted before the new row is inserted.
MSSQL dump options:
Include CREATE DATABASE statement – If ON then the CREATE DATABASE statement will be added to the dump.
Drop before restore – Clean (drop) database objects prior to outputting the commands for creating them.
Perform inserts in transaction – Add BEGIN/COMMIT statements for records of each dumped table.
Multiple rows in INSERT statement – Place multiple data rows in each INSERT statement. It makes dump loading faster.
(INSERT INTO TABLE_NAME (column_name, ...) VALUES ( ...row1... ), ( ...row2... ) )
Write REPLACE statements rather than INSERT statements – REPLACE works exactly like INSERT, except that if an old row in the table has the same value as a new row for a PRIMARY KEY or a UNIQUE index, the old row is deleted before the new row is inserted.
* Start new batch every – These options help to avoid dumping too long batches which may be harder to transmit over the network.
Write REPLACE statements rather than INSERT statements – REPLACE works exactly like INSERT, except that if an old row in the table has the same value as a new row for a PRIMARY KEY or a UNIQUE index, the old row is deleted before the new row is inserted.
SQLite dump options:
Valentina dump options:
SQL With External Data options.
Maximum data size to inline in the SQL file – All values exceeding this limit will be written to an external file.
Put string data to external file – If ON, string values may be placed to an external file (in addition to binary values).
Destination File
At this page you should define a destination file that will contain the dump.
Destination File – The path to the file, that will contain a dump.
Encoding – The encoding of the dump.
For SQL With External Data dump format of Valentina engine, it has one more option
Result Page
The last wizard page shows the dumping progress and results.