![]() ![]() ![]() |
Ispirer SQLWays Database Migration Software
DDL Options
The following options are the following:
- Tables settings:
- If the Change column names case to check box is selected, it is possible to select the case of column names in the SQL statements: Upper, Lower. If the Change column names case to check box is clear, the case of the column names is not changed and column names are used as they are provided by source database.
- If the Use constraint names of the source database in DDL statement check box is selected, constraint names of the source database will be used in generated DDL scripts. Otherwise constraint names will be skipped. By default the Use constraint names of the source database in DDL statement check box is clear.
- If the Convert identity columns check box is selected, SQLWays converts the identity properties of columns. If the Convert identity columns check box is clear, SQLWays does not extract the identity properties. Identity columns are commonly used in conjunction with primary key constraints to serve as the unique row identifier for the table.
- By default the Force NOT NULL constraints for columns that make up a primary key check box is selected, so all primary key columns are created with NOT NULL constraints. Some databases (Oracle, Sybase, Access e.g.) allow not specifying NOT NULL constraints for primary key columns explicitly when creating the table, and they change columns to NOT NULL when adding a primary key. Other databases (IBM DB2, Microsoft SQL Server, MySQL e.g.) require primary key columns to be created with NOT NULL constraints before adding a primary key.
- By default the Remove NOT NULL constraints from all columns except primary key columns check box is clear, so the NOT NULL constraints for all columns except primary key columns in the target database are not removed to avoid their conversion between databases by SQLWays.
- SQL scripts settings are:
- Omit schema names in SQL scripts: This option specifies that schema (owner) names are omitted in SQL scripts for DDL statements. This allows you to use the default schema (owner) name for the user.
- Change schema names to: This option allows you to change the schema (owner) name of the exported database objects. If a value is specified, SQLWays changes the source schema (owner) name to the specified value. If no value is specified, the schema (owner) name is not changed and the source value is used.
- Use statement termination string: This option specifies a string that is used to terminate SQL statements in SQL scripts. The default value is a semicolon (;) unless the target database is Sybase or Microsoft SQL Server. If the target database is Sybase or Microsoft SQL Server the default value is GO.
If the Generate DDL check box is selected:
- If the Generate the DROP TABLE statement for each table check box is selected, the DROP TABLE statement is generated before the CREATE TABLE statement.
- If the Generate the DROP INDEX statement for each index check box is selected, the DROP INDEX statement is generated before each CREATE INDEX statement. By default the Generate the DROP INDEX statement for each index check box is clear. This option can be helpful when the scripts for indexes are re-executed without recreating the table.
- If the Cascade referential integrity constarints check box is selected, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. For more information, see Dropping Tables. This option is only available if the target database is Oracle and the Generate the DROP TABLE statement check box is selected.
- Global Data Type Mapping: These settings show how global data types in the source database are mapped to the target one.
- Column Name Mapping: These settings show how global data types in the source database are mapped to the target one.
To specify DDL options in the command line
![]() ![]() ![]() |