DDL Extract Options

From DBArtisan
Jump to: navigation, search

Go Up to Configuring Feature Options

The DDL Extract tab of the Options Editor lets you specify results-handling preferences for use of the Extract object action.

Note: For information on opening the Options Editor, see Specifying Application Preferences and Feature Options.
Note: For information on using the Extract object action, see Extract.

Common options

The table below describes the options and functionality on the DDL Extract tab, main view, of the Options Editor:

Option Description

Extract to multiple windows

Select to extract the schema for each object into separate DDL windows. NOTE: This option only works when you extract DDL for multiple objects.

Extract in dependency order

This is the default. When you select a number of objects as part of an extraction job, this option ensures objects will be extracted in the proper dependency order. If the option is not selected, errors may result when you execute the script. It’s also true, however, that loading the dependencies can add significant overhead when you are extracting numerous objects.

Script Use Statement

This option is for Sybase. Optimizes extraction through generating Use statements in the generated script.

Grouping Extracted DDL

There are two option as to how the DDL is generated for an extract operation: Group the Drop and Create DDL for each object together - Objects are extracted one at a time. In the DDL generated by the extract, the Drop statement for a selected or referenced object is followed by the Create statement for that object. Group DDL statements by type - all Drop statements, then all Create statements - In the DDL generated by the extract, Drop statements for all selected or referenced objects are grouped to precede Create statements for those objects. This method ensures that all dependencies are respected. For more information on DROP options and dependencies, see DBMS-specific DDL Extract Options.

DBMS-specific DDL Extract Options

The DBMS-specific views of the DDL Extract tab let you specify:

  • The object types to include DROP statements for
  • The default dependent object types for each object type included in extraction/migration operations

You can choose to include DROP statements before you perform ad hoc DDL extractions. You can use this feature to modify and to re-compile database objects. To recompile a database object, drop it before recreating it. This option drops any existing objects of the same name before recreating the object. The data in the existing table is not saved when you specify a DROP statement for extracted DDL.

Caution: Because dropping an object is a destructive action, you should carefully consider including drop statements before activating this option.

You can also specify dependent object types included in extraction/migration operations. Each DBMS-specific view of the DDL Extract tab lets you specify the object dependencies for each object type. Dependent object types selected on that view are by default selected when you run an extraction/migration operation and can be overridden using those wizards. For more information see Extract.