Comparison of a DDL file or migrate-type worklist to a DDL file or migrate-type worklist

Versions of an application’s data structures are often contained in DDL files or migrate-type worklists.

When you generate CDL by using a DDL file or a migrate-type worklist, the CDL shows the changes between the two versions of the data structures.

A DDL file (or a migrate-type worklist) to another DDL file (or a migrate-type worklist) comparison is generally used to maintain versions of your DDL. This comparison scenario assumes that you are comparing an older DDL file to a newer DDL file.

Important

The DDL file or migrate-type worklist should define the application’s data structures completely. For example, the file cannot contain an ALTER statement that modifies the primary quantity of a table space without containing a CREATE statement that establishes the table space.

GUID-2612C25A-E4FF-49C8-B44A-611F69025AE1-low.png

With a DDL file to a DDL file comparison, you can generate CDL for all changes that have occurred to your DDL. Any name changes will be eliminated either before or after the comparison is actually performed (by using an outbound migrate profile) or will cause renamed objects to appear as DROP and CREATE statements in the CDL file.



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*