From the main menu, the user may export table definitions with or without data. The exported objects and data are stored in sequential files, which may be imported to re-create the tables in another Mimer SQL database.
Both choices ("Export - definitions and data" or "Export - definitions only") display a second menu giving the following options:
Select: 1 -- Export - definitions and data -- 1. Export specific tables 2. Export all tables for ident 3. Export all tables in databank 4. Export all tables in schema 0. Exit
The fourth menu option will only appear when connected to a version 8.2 server (or later).
Depending on the selection made, the user is prompted for a list of table names (the list is terminated by the first "empty" or blank name), an ident name, or a databank name. In the case of tables selected by ident, schema or databank, a single set of tables will be exported by each operation.
For all export functions, the user is prompted for the name of the sequential file to be used for the export.
Extent and Authorization
In general, only the creator of a specific object can export it. Furthermore, a table can be exported by any ident having the SELECT privilege for it. With this background, exporting a complete databank may not necessarily mean that all tables within the databank will be exported.
The "Enter program ident" option in the main menu, provides a facility for specifying an alternative ident to use while performing the export operation.
The user running the Export/Import functionality must have EXECUTE privilege on the program ident in order to enter the program. Again, if export is performed for an ident, it is not assured that all tables for that ident are exported (due to privilege restrictions for the ident running the functionality).
Objects that can be exported explicitly are tables and schemas. Indexes, domains and foreign keys associated with an exported table will automatically be included in the export operation as far as access privileges allow.
If a foreign key table cannot be accessed, the foreign key definition will simply be left out from the export operation.
If columns in tables being exported belong to domains, the used domain definitions are exported together with the table definitions. If such a domain is not owned by the ident doing the export operation the domain will be replaced by the data type it is based upon, i.e. the domain is not exported and the use of it is lost.
If a synonym is specified as a table name, the appointed base table will be exported. The synonym itself will not be exported.
Export files created with version 8.1 of the UTIL program (or earlier) can be imported using the version 8.2 UTIL program, but the converse operation is not supported.
The version 8.2 UTIL program can be used towards a version 8.1 database server (or earlier).
Table, domain, and index definitions are exported in the form of CREATE statements for re-creating identical objects in the import environment.
See the Mimer SQL Reference Manual for the syntax and description of the relevant CREATE statements.
Note: The import function allows naming conflicts to be resolved interactively during import.
Table contents are exported in sequential format.
Export files begin with system information concerning Mimer SQL version, machine and operating system, file record length and data storage formats, and so on. Statistical information at the end of the file records the number of data rows exported for each table.
Upright Database Technology AB
Voice: +46 18 780 92 00
Fax: +46 18 780 92 40