About Ispirer Systems
Ispirer Home Page Database Migration Application Conversion Downloads
Sqlways_db.ini File - Section [DDL]
This article describes sqlways_db.ini file's [DDL] section and the options it contains.
| Option name | Description |
|---|---|
| DROP_TABLE_CASCADE_CONSTRAINTS | When this option is enabled (set to “Yes”), the CASCADE clause (or CASCADE CONSTRAINTS for Oracle target) is added to the generated DROP TABLE statement. Possible values: “No”, “Yes” or Empty. Default value: “Yes”/Empty. Usage Example. |
| CONVERT_PACKAGE_TO_SCHEMA | This option is used when converting Oracle packages. By default, a separate schema is created for each package, and all procedures and functions contained in the package are placed into this new schema. If this option is set to “No”, the original schema is preserved, and the procedures and functions are created in that schema with the package name added as a prefix. Possible values: “No”, “Yes” or Empty. Default value: “Yes”/Empty. Usage Example. |
| CONVERT_SP_RETSTATUS_OUTPARAM | If this option is set to “Yes”, the source procedure is converted into a target procedure with an additional OUT parameter that returns the execution status of the procedure. If this option is set to “No”, the execution status is omitted. Possible values - “No”, “Yes” or Empty. Default value: “Yes”/Empty. Usage Example. |
| PARAM_PREFIX | This option specifies the prefix applied to parameter names when migrating from databases such as Firebird, Microsoft SQL Server, or Sybase ASE. If PARAM_PREFIX is set to an empty value, no prefix is added to parameter names in the converted code. If PARAM_PREFIX is not specified in the options file, SQLWays removes the source-specific parameter prefix (for example, @) and prepends the default prefix, v_, to the parameter name. If PARAM_PREFIX is explicitly specified, the configured prefix is used for all parameter names in the converted code. Default value: v_. Usage Example. |
| VAR_PREFIX | This option specifies the prefix to be applied to variable names during code conversion from Firebird, Microsoft SQL Server, or Sybase ASE. The specified value is used as the prefix for variable names. If the option is set to an empty value, no prefix is added to variable names. If the option is not specified, the default prefix v_ is applied Default value: v_. Usage Example. |
| SQLWAYS_FRAMEWORK_SCHEMA | When the target database does not provide a direct equivalent for certain source database constructs, helper functions are generated to emulate the original behavior. All such helper objects are created in the schema specified by this option. Default value: sqlways_utils. Usage Example. |
| SYNONYM_TO_VIEW | This option controls how synonyms are converted to PostgreSQL for source databases that support synonyms, such as Oracle, DB2, Informix, and others. By default, CREATE SYNONYM statements are commented out, and all references to synonyms are replaced with the names of the underlying objects. If this option is set to “Yes”, synonyms that reference tables are converted into PostgreSQL views that retain the original synonym names. Possible values - “No”, “Yes”. Default value: “No”. Usage Example. |
| EMPTY_SCHEMA | This option defines whether the schema names should be used in the generated target script. If it is set to “Yes” - schema names will be removed. If set to “No” - schema names in generated target code will be left the same as in the source code. If set to 'Default' - only default schema names if exist will be removed in the generated target code, all other schema names will be left as is. Possible values - “No”, “Yes” or ”Default”. Default value: “Yes”/Empty. |
| OUTSCHEMA | This option can be used only when “EMPTY_SCHEMA” option is set to “No”. In this option user can specify a schema name that will be used in the generated target code, instead of original one. When this option is empty, used original schema names. Default value: Empty. |
| CONVERT_DATABASE_TO_SCHEMA | This option controls the conversion of object names. If this option is set to Yes, the name of the current database is used as the target schema name, and the original schema name is omitted. Possible values - “Yes”, “No” or Empty . Default value: “No”/Empty. Usage Example. |
| CONVERT_DBLINK_TO_SCHEMA | This option controls the conversion of object names that reference objects in another database for source DBMSs that support cross-database references, such as Microsoft SQL Server (MSSQL), Sybase ASE, Informix, and others. It is intended for migration to target DBMSs that do not support this type of reference. If this option is set to Yes, the source database name is used as the target schema name, and the original source schema name is omitted. ex.: db.dbo.tab (MSSQL) → db.tab(PostgreSQL). Possible values - “Yes”, “No” or Empty . Default value: “No”/Empty. Usage Example. |
| SCHEMA_TO_OBJ_NAME | This option is used to convert the schema name into an object name prefix. Possible values - “Yes”, “No” or Empty . Default value: “No”/Empty. Usage Example. |
| QUOTE_IDENTIFIERS | This option encloses identifier names in quotes in target scripts. Possible values - “Always”, Empty . Default value: Empty. |
| REPLACE_RESERVED_WORDS | This option is used to change identifiers of the source database which serve as reserved words in the target database. The option specifies a template for reserved words replacement. For example, if %RWORD%_ is specified, underscore character is added to the right of all reserved words. The default value of the template is %RWORD% which means that the reserved words are not changed and are delimited in SQL statements for the target database. The delimiter depends on the database. Default value: %RWORD%. |
| COLUMN_NAME_CASE | This option specifies the case of column names in SQL statements. If no value is specified, the case of the column names is not changed and column names are used as they are provided in the source database. Possible values - “Upper”, “Lower”, Empty . Default value: Empty. |