SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—544517-008
5-91
Considerations for mxexportddl
-CLEAR ON |OFF
specifies if the mxexportddl utility can overwrite the specified XML file if it
already exists. The default is OFF.
ON
overwrites the specified XML file if it already exists.
OFF
does not overwrite the specified XML file. If the file already exists, the write
operation fails.
Considerations for mxexportddl
You must be the super ID or schema owner to run mxexportddl.
You can edit the XML file manually using simple text editors. However, this method can
be error-prone and is not recommended.
Because the schema owner information in the XML file can be updated, other users
can import the schema and its objects.
Remote catalogs must be registered manually before executing mxexportddl.
mxexportddl supports the RI actions CASCADE/SET NULL/SET DEFAULT in
addition to NO ACTION and RESTRICT.
Supported by mxexportddl
•
System defaults
•
Tables and associated objects such as indexes and partitions
•
Constraints: check, not null, primary key, and unique
•
Table statistics that includes physical statistics (index level, nonempty block count,
and EOF), histograms, and histogram intervals
•
Referential integrity constraints, views, triggers, and stored procedures
Not Supported by mxexportddl
•
SQL/MP tables and aliases
Examples of mxexportddl
•
To export the catalog cat1 and schema cat2.sch1 and cat2.sch2:
mxexportddl -cat cat1 -sch cat2.sch1 cat2.sch2 -xmlfile
export.xml
•
To export the catalog cat1 without statistics:
mxexportddl -cat cat1 -xmlfile export.xml -stats off