Differences
This shows you the differences between two versions of the page.
sqlways:command-line:sqlways-ini:ddl-section [July 12, 2018, 01:42:32 PM] – alexandr.kirpichny | sqlways:command-line:sqlways-ini:ddl-section [May 31, 2023, 05:28:08 PM] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
\\ | \\ | ||
- | [[http:// | + | [[https:// |
- | [[http:// | + | [[https:// |
- | [[http:// | + | [[https:// |
====== Sqlways.ini File - Section [DDL] ====== | ====== Sqlways.ini File - Section [DDL] ====== | ||
- | This article describes sqlways.ini file [DDL] section and the options it contains. | + | This article describes sqlways.ini file' |
^ Option name ^ Description | ^ Option name ^ Description | ||
| **GENERATE_DROP_TABLE** | If Yes is specified, the DROP TABLE statement is generated before each CREATE TABLE statement. The default value is No. Possible values - Yes, No. | | | **GENERATE_DROP_TABLE** | If Yes is specified, the DROP TABLE statement is generated before each CREATE TABLE statement. The default value is No. Possible values - Yes, No. | | ||
- | | **DROP_TABLE_CASCADE_CONSTRAINTS** | If Yes is specified, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. \\ This option is only available if the target database is Oracle and GENERATE_DROP_TABLE is set to Yes. The default value is No. | | + | | **GENERATE_DROP_VIEWS** | If Yes is specified, the DROP VIEW statement is generated before each CREATE VIEW statement. \\ The default value is No. \\ Possible values - Yes, No. | |
+ | | **GENERATE_DROP_PROCEDURES** | If Yes is specified, the DROP PROCEDURE statement is generated before each CREATE PROCEDURE statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_FUNCTIONS** | If Yes is specified, the DROP FUNCTION statement is generated before each CREATE FUNCTION statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_TRIGGERS** | If Yes is specified, the DROP TRIGGER statement is generated before each CREATE TRIGGER statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_PACKAGES** | If Yes is specified, the DROP PACKAGE statement is generated before each CREATE PACKAGE statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_USER_ACCOUNTS** | If Yes is specified, the DROP USER statement is generated before each CREATE USER statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_USER_DEFINED_TYPES** | If Yes is specified, the DROP TYPE statement is generated before each CREATE TYPE statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_SEQUENCES** | If Yes is specified, the DROP SEQUENCE statement is generated before each CREATE SEQUENCE statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_SYNONYMS** | If Yes is specified, the DROP SYNONYM statement is generated before each CREATE SYNONYM statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_MACROS** | If Yes is specified, the DROP MACRO statement is generated before each CREATE MACRO statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_EXCEPTIONS** | If Yes is specified, the DROP EXCEPTION statement is generated before each CREATE EXCEPTION statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **GENERATE_DROP_EVENTS** | If Yes is specified, the DROP EVENT statement is generated before each CREATE EVENT statement. The default value is No. Possible values - Yes, No. | | ||
+ | | **DROP_TABLE_CASCADE_CONSTRAINTS** | If Yes is specified, the CASCADE CONSTRAINTS option is generated in the DROP TABLE statement. Currently this option is supported by Oracle only. \\ This option is available | ||
| **GENERATE_DROP_INDEX** | If Yes is specified, the DROP INDEX statement is generated before each CREATE INDEX statement. The default value is No. Possible values - Yes, No. \\ This option can be helpful when scripts for indexes are re-executed without recreating the table. | | | **GENERATE_DROP_INDEX** | If Yes is specified, the DROP INDEX statement is generated before each CREATE INDEX statement. The default value is No. Possible values - Yes, No. \\ This option can be helpful when scripts for indexes are re-executed without recreating the table. | | ||
- | | **OUTSCHEMA** | Output | + | | **OUTSCHEMA** | This option can be used only when " |
- | | **EMPTY_SCHEMA** | for /EMPS option. Possible values - Yes, No. | | + | | **EMPTY_SCHEMA** | This option |
| **COLUMN_NAME_CASE** | This option specifies the case of column names in SQL statements. Possible values - Upper, Lower. 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. | | | **COLUMN_NAME_CASE** | This option specifies the case of column names in SQL statements. Possible values - Upper, Lower. 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. | | ||
| **USE_CONSTRAINT_NAMES** | If Yes is specified, constraint names of the source database will be used in generated DDL scripts. Otherwise, constraint names will be skipped. The default value is No. Possible values - Yes, No. | | | **USE_CONSTRAINT_NAMES** | If Yes is specified, constraint names of the source database will be used in generated DDL scripts. Otherwise, constraint names will be skipped. The default value is No. Possible values - Yes, No. | | ||
- | | **PK_COLS_NOTNULL** | This option is used to set the NOT NULL constraints in the CREATE TABLE statement for columns making up a primary key. The default value is Yes. Possible values - Yes, No. Some databases (Oracle, Sybase, Access e.g.) allow to not specify the NOT NULL constraints for primary key columns explicitly when creating a 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. \\ The default value is Yes (all primary key columns will be created with NOT NULL constraints). Possible values - Yes, No. | | + | | **PK_COLS_NOTNULL** | This option is used to set the NOT NULL constraints in the CREATE TABLE statement for columns making up a primary key. The default value is Yes. Possible values - Yes, No. Some databases (Oracle, Sybase, Access e.g.) allow not to specify the NOT NULL constraints for primary key columns explicitly when creating a 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. \\ The default value is Yes (all primary key columns will be created with NOT NULL constraints). Possible values - Yes, No. | |
| **CONVERT_IDENTITY_COLUMNS** | If Yes is specified, SQLWays converts identity properties of columns. Otherwise, SQLWays does not extract the identity properties. The default value is Yes. Possible values - Yes, No. | | | **CONVERT_IDENTITY_COLUMNS** | If Yes is specified, SQLWays converts identity properties of columns. Otherwise, SQLWays does not extract the identity properties. The default value is Yes. Possible values - Yes, No. | | ||
| **REMOVE_NOTNULL_EXCEPT_PK** | If Yes is specified, the NOT NULL constraints for all columns except primary key columns in the target database are removed to avoid their conversion between databases by SQLWays. The default value is No. Possible values - Yes, No. \\ Identity columns are commonly used in conjunction with primary key constraints to serve as a unique row identifier for a table. | | | **REMOVE_NOTNULL_EXCEPT_PK** | If Yes is specified, the NOT NULL constraints for all columns except primary key columns in the target database are removed to avoid their conversion between databases by SQLWays. The default value is No. Possible values - Yes, No. \\ Identity columns are commonly used in conjunction with primary key constraints to serve as a unique row identifier for a table. | | ||
Line 20: | Line 32: | ||
| **STATEMENT_DELIMITER** | Statement termination character. | | | **STATEMENT_DELIMITER** | Statement termination character. | | ||
| **STATISTICS_STATEMENTS** | This option specifies whether statements to calculate statistics on tables in DDL scripts for table indexes should be generated.The default value is Yes. Possible values - Yes, No. Currently SQLWays generates statistics statements for IBM DB2 only. | | | **STATISTICS_STATEMENTS** | This option specifies whether statements to calculate statistics on tables in DDL scripts for table indexes should be generated.The default value is Yes. Possible values - Yes, No. Currently SQLWays generates statistics statements for IBM DB2 only. | | ||
- | | **PK_UNIQUE_INDEXES** | This option specifies whether indexes on primary keys and unique constraints should be generated. The default value is No. This means no index scripts are generated for primary keys and unique constraints. | + | | **PK_UNIQUE_INDEXES** | This option specifies whether indexes on primary keys and unique constraints should be converted. The default value is No. This means that indexes |
| **REPLACE_NOT_ALLOWED_CHARS** | This option specifies a character or a string that replaces not allowed characters in identifiers in the target database. \\ The source database may allow users to use characters in identifiers (table and column names etc.) which are not allowed in the target database. \\ For example, users can use @ in identifiers in Microsoft SQL Server, but this character is not allowed in identifiers in Oracle. \\ If no value is specified in this option and " | | **REPLACE_NOT_ALLOWED_CHARS** | This option specifies a character or a string that replaces not allowed characters in identifiers in the target database. \\ The source database may allow users to use characters in identifiers (table and column names etc.) which are not allowed in the target database. \\ For example, users can use @ in identifiers in Microsoft SQL Server, but this character is not allowed in identifiers in Oracle. \\ If no value is specified in this option and " | ||
- | | **REMOVE_NOT_ALLOWED_CHARS** | This option is similar to the replace_not_allowed_chars option, but it allows you to remove not allowed characters in identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed | + | | **REMOVE_NOT_ALLOWED_CHARS** | This option is similar to the replace_not_allowed_chars option, but it allows you to remove not allowed characters in identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed |
| **REPLACE_NOT_ALLOWED_CHARS_FPOS** | This option specifies a character or a string that replaces not allowed characters in the first position of identifiers in the target database. \\ Characters that are allowed in the first position of identifiers in the source database may not be allowed in the target database. \\ For example, Microsoft SQL Server identifiers can begin with _ (underscore) while Oracle identifiers cannot. \\ If no value is specified in this option and " | | **REPLACE_NOT_ALLOWED_CHARS_FPOS** | This option specifies a character or a string that replaces not allowed characters in the first position of identifiers in the target database. \\ Characters that are allowed in the first position of identifiers in the source database may not be allowed in the target database. \\ For example, Microsoft SQL Server identifiers can begin with _ (underscore) while Oracle identifiers cannot. \\ If no value is specified in this option and " | ||
| **REMOVE_NOT_ALLOWED_CHARS_FPOS** | This option is similar to the replace_not_allowed_chars_fpos option, but it allows users to remove not allowed characters in the first position of identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed in the first position of identifiers in the target database. \\ The default value is Yes. Possible values - Yes, No. | | | **REMOVE_NOT_ALLOWED_CHARS_FPOS** | This option is similar to the replace_not_allowed_chars_fpos option, but it allows users to remove not allowed characters in the first position of identifiers in the target database. \\ When Yes is specified, all not allowed characters are removed in the first position of identifiers in the target database. \\ The default value is Yes. Possible values - Yes, No. | | ||
- | | **TRIM_NAMES_EXCEEDING_MAX_LEN** | Databases may have different identifier length limits. For example, the maximum identifier length in SQL Server is 128 characters while in Oracle | + | | **TRIM_NAMES_EXCEEDING_MAX_LEN** | Databases may have different identifier length limits. For example, the maximum identifier length in SQL Server is 128 characters while in Oracle |
- | | **TRIM_RULE_ALPHANUM_ONLY** | This option is used in conjunction with the " | + | | **TRIM_RULE_ALPHANUM_ONLY** | This option is used in conjunction with the " |
- | | **REPLACE_RESERVED_WORDS** | This option is used to change identifiers of the source database which served | + | | **TRIM_RULE_ALPHANUM_STOP_WHEN_LIMIT_REACHED** | This option is used in conjunction with the " |
- | | **CONVERT_DATABASE_TO_SCHEMA** | This option is used to convert fully qualified names with the database specification. \\ It is required to set this option to Yes to get it work. | | + | | **TRIM_RULE_CONSONANTS_ONLY** | This option is used in conjunction with the " |
- | | **CONVERT_PACKAGE_TO_SCHEMA** | This option is used to convert the Package name as the schema from an Oracle database. \\ It is required to set this option to Yes to get it work. | | + | | **TRIM_RULE_CONSONANTS_STOP_WHEN_LIMIT_REACHED** | This option is used in conjunction with the " |
- | | **BUILTIN_FUNCTIONS_NULLIF_CHECK** | This option is used to generate NULLIF check when converting **LTRIM**, **RTRIM**, **SUBSTRING**, | + | | **TRIM_RULE_LEFTTRIM** | This option is used in conjunction with the " |
+ | | **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 | ||
+ | | **CONVERT_DATABASE_TO_SCHEMA** | This option is used to convert fully qualified names with the database specification. \\ Please | ||
+ | | **CONVERT_PACKAGE_TO_SCHEMA** | This option is used to convert the Package name as the schema from an Oracle database. Currently this feature works for MSSQL as a target database only. \\ Please | ||
+ | | **SCHEMA_TO_OBJ_NAME** | This option is used to convert the schema name as the prefix to the object name. \\ Possible values - " | ||
+ | | **BUILTIN_FUNCTIONS_NULLIF_CHECK** | This option is used to generate NULLIF check when converting **LTRIM**, **RTRIM**, **SUBSTRING**, | ||
| **FULLY_QUALIFY_IDENTIFIERS** | This option is used to generate schema for each referenced object without schema inside a View, Stored Procedure or Function. \\ This option works only if the **EMPTY_SCHEMA** option is set to No. \\ The default value is No. Possible values - Yes, No.| | | **FULLY_QUALIFY_IDENTIFIERS** | This option is used to generate schema for each referenced object without schema inside a View, Stored Procedure or Function. \\ This option works only if the **EMPTY_SCHEMA** option is set to No. \\ The default value is No. Possible values - Yes, No.| | ||
- | | **CONVERT_ROUTINE_TO_SP_RESULTSET** | If it' | + | | **CONVERT_ROUTINE_TO_SP_RESULTSET** | If it is set to Yes, all the functions and procedures that return values must be converted to stored procedures that return resultset via the SELECT statement. |
- | | **OUT_REFCUR_FIRST_POSITION** | This option works together with CONVERT_ROUTINE_TO_SP_RESULTSET and puts OUT parameter to the first position in the parameter list. Also please note, that this option will work only for Oracle version 11 and lower. For Oracle version 12 and higher OUT parameter will not be generated, and will be used PIPELINE functionality. \\ Possible values - " | + | | **OUT_REFCUR_FIRST_POSITION** | This option works together with CONVERT_ROUTINE_TO_SP_RESULTSET and puts OUT parameter to the first position in the parameter list. Also please note, that this option will work only for Oracle version 11 and lower. For Oracle version 12 and higher OUT parameter will not be generated, and PIPELINE functionality |
| **MIGRATE_MEMBERSHIP** | This option controls the way the **Groups** are converted. When MIGRATE_MEMBERSHIP=No then groups are migrated as simple users and default permissions are used for them, E.G.: \\ For SAP ASA to Microsoft SQL Server db_datareader and db_datawriter are specified. \\ The default value is Yes. Possible values - Yes, No.| | | **MIGRATE_MEMBERSHIP** | This option controls the way the **Groups** are converted. When MIGRATE_MEMBERSHIP=No then groups are migrated as simple users and default permissions are used for them, E.G.: \\ For SAP ASA to Microsoft SQL Server db_datareader and db_datawriter are specified. \\ The default value is Yes. Possible values - Yes, No.| | ||
- | | **TARGET_FILES_GROUPING** | This option controls the way the result SQL files are generated. \\ When data export is switched off and the TARGET_FILES_GROUPING = YES, then separate SQL files are generated | + | | **TARGET_FILES_GROUPING** | This option controls the way the result SQL files are generated. \\ When data export is switched off and the TARGET_FILES_GROUPING = YES, then separate SQL files are generated for each object extracted from the source database. \\ If the TARGET_FILES_GROUPING=ALL, |
- | | **CONVERT_GLOBAL_VARIABLES_TO_LOCAL** | This option controls the way global or user variables are converted by SQLWays. \\ When the option is set to Yes, all global variables are converted to local variables declared and used inside | + | | **CONVERT_GLOBAL_VARIABLES_TO_LOCAL** | This option controls the way global or user variables are converted by SQLWays. \\ When the option is set to Yes, all global variables are converted to local variables declared and used inside |
- | | **PKG_VARIABLES** | This option controls the way global variables are stored in the target database. \\ When the option is set to UNION_BY_PACKAGE, | + | | **PKG_VARIABLES** | This option controls the way global variables are stored in the target database. \\ When the option is set to UNION_BY_PACKAGE, |
- | | **CONVERT_PK_INDEX** | This option controls the way the indexes, created on primary column in DB2, are converted by SQLWays. \\ When the option is set to Yes, the indexes on primary columns are converted to their equivalent. \\ If the option is set to No, then indexes are commented by SQLWays. | + | | **CONVERT_PK_INDEX** | This option controls the way the indexes, created on primary column in DB2, are converted by SQLWays. \\ When the option is set to Yes, the indexes on primary columns are converted to their equivalents. \\ If the option is set to No, then indexes are commented by SQLWays. |
- | | **FN_RET_MULTIPLE_VALUES_TO_TABLE_FN** | This option controls the way informix functions, which return multiple values, are converted to MSSQL Server. If this option is set as Yes, SQLWays will convert | + | | **FN_RET_MULTIPLE_VALUES_TO_TABLE_FN** | This option controls the way informix functions which return multiple values are converted to MSSQL Server. If this option is set as Yes, SQLWays will convert |
- | | **SW_SEQ_SUFFIX** | This option adds suffix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is " | + | | **SW_SEQ_SUFFIX** | This option adds suffix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is " |
- | | **SW_SEQ_PREFIX** | This option adds prefix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is " | + | | **SW_SEQ_PREFIX** | This option adds prefix to the sequences generated automatically by Ispirer SQLWays Wizard. Default value is " |
- | | **SW_TRIG_SUFFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is " | + | | **SW_TRIG_SUFFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is " |
- | | **SW_TRIG_PREFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is " | + | | **SW_TRIG_PREFIX** | This option adds suffix to the triggers generated automatically by Ispirer SQLWays Wizard. Default value is " |
- | | **ANSI_QUOTED_IDENTIFIERS** | This option controls how to handle text inside | + | | **ANSI_QUOTED_IDENTIFIERS** | This option controls how to handle |
- | | **TARGET_BL** | This option controls how business logic objects (procedures, | + | | **TARGET_BL** | This option controls how business logic objects (procedures, |
- | | **CASCADE_CONSTRAINTS_NO_ACTION** | If there is a referential relationship between a table and the parent row is altered in the parent table, an action, which should be done on child table, can be specified in constraint definition. If you set this option as " | + | | **CASCADE_CONSTRAINTS_NO_ACTION** | If a referential relationship between a table and the parent row is altered in the parent table, an action, which should be performed for child table, can be specified in constraint definition. If you set this option as " |
- | | **QUOTE_IDENTIFIERS** | This option | + | | **QUOTE_IDENTIFIERS** | This option |
| **SYNONYM_TO_VIEW** | This option controls how Oracle synonyms should be converted to PostgreSQL database. By default CREATE SYNONYM statement will be commented and all the synonyms identifiers will be changed to the original object names. If this option is set to YES, all the synonyms will be converted to views in PostgreSQL. Possible values - " | | **SYNONYM_TO_VIEW** | This option controls how Oracle synonyms should be converted to PostgreSQL database. By default CREATE SYNONYM statement will be commented and all the synonyms identifiers will be changed to the original object names. If this option is set to YES, all the synonyms will be converted to views in PostgreSQL. Possible values - " | ||
| **CONVERT_SP_RETSTATUS_OUTPARAM** | If this option is set to " | | **CONVERT_SP_RETSTATUS_OUTPARAM** | If this option is set to " | ||
- | | **CONVERT_CHECK_CONSTRAINTS** | This option defines whether check constraints should be converted. If this option is set to " | + | | **CONVERT_CHECK_CONSTRAINTS** | This option defines whether check constraints should be converted |
- | | **CONVERT_UNIQUE_CONSTRAINTS** | This option defines whether unique constraints should be converted. If this option is set to " | + | | **CONVERT_UNIQUE_CONSTRAINTS** | This option defines whether unique constraints should be converted |
- | | **SCHEMA_TO_DATABASE** | This option controls schema names conversion for all specified objects for the migration process. If this option is set to " | + | | **SCHEMA_TO_DATABASE** | This option controls schema names conversion for all specified objects for the migration process. If this option is set to " |
- | | **PARTITION_TABLESPACE** | This option controls whether source partition table tablespaces should be converted or no. In case when the option is set into " | + | | **PARTITION_TABLESPACE** | This option controls whether source partition table tablespaces should be converted or not. When the option is set into " |
- | | **REMOVE_VAR_PREFIX** | This option controls the way the source | + | | **REMOVE_VAR_PREFIX** | This option controls the way the source |
- | | **VAR_PREFIX** | This option defines | + | | **VAR_PREFIX** | This option defines |
+ | | **USE_CHAR_LENGTH** | When migrating tables from Oracle to PostgreSQL, Greenplum or Redshift, information about the column length is taken from DATA_LENGTH column from ALL_TAB_COLUMNS system table. This column stores information about the number of bytes of CHAR\VARCHAR2 and NCHAR\NVARCHAR2 columns. And if you need to use the number of characters as a length of CHAR\VARCHAR2 and NCHAR\NVARCHAR2 columns, you need to set this option to " | ||
+ | | **USE_SYSTEM_COLUMN_NAME** | This option allows to use system column names when migrating from DB2 database. \\ Possible values - " | ||
+ | | **REFCUR_NAME_FOR_RESULT_SETS** | This option allows to control the name of the refcursor OUT parameter name. | | ||
+ | | **CONVERT_INDEXES** | This option defines the types of the indexes that will be converted by SQLWays tool. \\ Possible values - " | ||
+ | | **CONVERT_TEMPORARY_TABLES_TO_PERMANENT_TABLES** | This option defines how to convert temporary tables. If this option is set to " | ||
+ | | **CONVERT_ALL_SP_TO_PACKAGE** | If this option is set to " | ||
+ | | **START_VALUE_EXTRACTION_WITH_SEQUENCE_INCREMENT** | If this option is set to " | ||
+ | | **CONVERT_COMMENTS** | This option defines whether the comments inside the sql code should be converted or not. By default this option is set to " | ||
+ | | **EXPORT_CONSTRAINTS_FOR_QUERIES** | This option controls whether the constraints should be converted when performing conversion using the queries. \\ Possible values - " | ||
+ | | **CONVERT_MM_TAB** | This option defines how multi-member tables will be converted from DB2 AS 400 into Microsoft SQL Server database. If this option is set to " | ||
+ | | **ORACLE_PKG_TO_FN** | This option allows to change package conversion structure logic for Oracle to Greenplum migration direction. By default Oracle packages are converted to sets of Greenplum functions that correspond to source package routines. Package global variables are converted using temporary tables. If the option is set to ' | ||
+ | | **APP_PARAMS_IN_SQL** | This option defines whether the application parameters are used in source Sybase ASE sql code. If this option is set to " | ||
+ | | **VARCHAR_PAR_LEN** | When migrating from Oracle to MySQL, you can specify your own length for VARCHAR parameters in procedures and functions. Specified number will be used as a length of VARCHAR parameters in MySQL procedures and functions. | | ||
+ | | **FK_SELECTED_TABLES_ONLY** | This option defines whether to generate Foreign Key constraints that references tables that were not selected for conversion. If this option is set to " | ||
+ | | **PERCENT_AS_COMMENT** | Sybase ASA database 10 version and lower allows to use " | ||
+ | | **TEMP_TAB_SCHEMA** | This option defines the schema name for temporary tables. It works only when option " | ||
+ | | **CONVERT_SYSTEM_VERSIONED_TABS** | This option defines how to MSSQL convert system versioned tables to PostgreSQL. If this option is set to Yes, then will be generated additional triggers that will emulate the same behavior in PostgreSQL. If this option is empty or set to " | ||
+ | | **OUTER_JOIN_RETURNS_NULLS** | When migrating to Oracle in JOIN is used varchar column that allows NULLs values and this option is set to Yes, then such column will be placed inside NVL function. If this option is empty or set to " | ||
**Example**: | **Example**: | ||
Line 64: | Line 100: | ||
\\ | \\ | ||
- | If you have any questions about the supported options or some features that you may need during | + | If you have any questions about the supported options or about any features that you may need for your migration project, please contact our technical team: **__[[[email protected]]]__** |
- | \\ | ||
- | [[http:// | ||
- | [[http:// | ||
- | [[http:// |