nuodb-migrator dump

--source.driver=driver

Yes

JDBC driver class name

--source.url=url

Yes

Source database connection URL in the standard syntax: jdbc:subprotocol:subname

--source.username=username

Yes

Source database username.

--source.password=password

No

Source database password.

--source.properties=properties

No

Additional connection properties encoded as URL query string, e.g. “property1=value1&property2=value2…​” (see Connection Properties).

--source.catalog=catalog

No

Default database catalog name to use

--source.schema=schema

No

Default database schema name to use

--source.auto.commit={ true | false }

No

If set to true, each individual statement is treated as a transaction and is automatically committed after it is executed. The default is false.

--source.transaction. isolation=value

No

Sets the transaction isolation level for the migration execution. A valid value can be either a symbolic name or an integer constant representing transaction isolation levels as defined in the JDBC java.sql.Connection class. Valid values include:

NuoDB does not support all of the levels, only read.committed or 2, serializable or 8 and two additional levels that are not in the JDBC standard. See Supported Transaction Isolation Levels for more information.

--output.type={ csv | xml | bson }

Yes

Output type to generate - default is csv.

--output.path=output_path

No

Path on the file system where the output should be generated. If the `--schema=true command line parameter option is used, the schema DDL SQL script file will also be written to this directory. The file is named with extension .sql.

--output.{csv | xml}.attribute_name=attribute_value

No

Output format attributes. These are specific to the type of output being generated, as defined by the command line option parameter --output.type. In other words, the choice between csv or xml must match the value specified as --output.type. For csv, the valid attributes (attribute_name=attribute_value) are:

For xml, the valid attributes (attribute_name=attribute_value) are:

--data={ true | false }

No

Enables or disables data being dumped. Default is true.

--schema={ true | false }

No

Enables or disables generation of DDL SQL script file to generate schema objects. This enforces the same behavior as running nuodb-migrator schema. Default is true.

--data=true --schema=true

dump both data and metadata from the source database. This is the default value.

--data=false --schema=true

nuodb-migrator dump only, the metadata from the source database

--data=true --schema=false

nuodb-migrator dump only, data from the source database

--table=table_name[,table_name…​]

No

Table(s) specified for data to be dumped

--table.type=table_type[,table_type,…​]

No

Comma separated list of types of table objects (TABLE, VIEW, SYSTEM TABLE, GLOBAL TEMPORARY, ALIAS, SYNONYM, etc) to process. The default behavior is only TABLE types are processed. Views, triggers, functions, and stored procedures are not supported by the nuodb-migrator tool.

--table.catalog_name[schema_name.] table_name.filter=query_filter

No

Selects table rows to be dumped from the table specified as table_name (optionally catalog and/or schema qualified), using a WHERE clause specified by query_filter. nuodb-migrator will dynamically generate a SELECT statement, selecting all table columns from the table, and apply the query_filter as the WHERE clause. If query_filter contains spaces, it must be enclosed in double quotes.

--threads=thread_val

No

Number of concurrent processing threads, defined by thread_val as integer (i.e. a value of 1 would cause single thread processing). The default value is the number of CPU cores.

--query=query

No

A SELECT statement that will filter table records to be dumped. Only the result set of the query will be dumped.

--query.limit=query_limit

No

Query limit is a maximum number of rows to split a table into chunks with LIMIT limit OFFSET offset syntax in a database specific way, where each chunk is written to a separate file. If a query limit is not given or is not supported by nuodb-migrator for a particular database, queries are not split.

--time.zone=time_zone

No

Time zone enables date columns to be dumped and reloaded between servers in different time zones

Various schema command line options

No

Various optional schema command options are also supported when the --schema=true command line option is passed to nuodb-migrator dump. For more information, see migration modes and nuodb-migrator schema.