Archives of the TeradataForum

Message Posted: Tue, 28 Feb 2006 @ 18:39:19 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

If you are using Export you can only provide one export file name. The name will be prefixed by a number if you are writing each output to a separate file. (Most people I have met prefered all the DDL to be written to a single file in a case like this.)

If you use Import all the DDL will be written to a single file, but 'headers' will be written between each set of DDL.

If you export only objects of a given type (eg. 'Table') within a specific database then you can use the import command:

     Show Table ?

after first issuing a Database command to set the appropriate database.

This requires an import file containing only table names (one per line) and the 'header' written to the output will be:

     ===> Tablename <===

which is written between each set of DDL as follows:

     ===> Table1 <===

     CREATE SET TABLE DBCMNGR.Table1 ,FALLBACK ,
          NO BEFORE JOURNAL,
          NO AFTER JOURNAL,
          CHECKSUM = DEFAULT
          (
           C_ByteInt BYTEINT TITLE '8 bit Int',
           ...
           ...

     ===> Table2 <===

     CREATE SET TABLE DBCMNGR.Table2 ,FALLBACK ,
          NO BEFORE JOURNAL,
          NO AFTER JOURNAL,
          CHECKSUM = DEFAULT
          (
           LastName CHAR(20) CHARACTER SET LATIN CASESPECIFIC,
           ...
           ...

This kind of output is very good for documenting your design. (But not so good if you simply want electronic copies of your source files that can be run individually.)

Mike Dempsey
Teradata Client Tools

	<Prev	Next>		<<First	<Prev	Next>	Last>>