Oracle Conversion Settings

General Conversion Settings

  1. Transform Synonyms: Flag to indicate whether or not Synonyms should be transformed. By default, it's set to true.

  2. Transform Packages to new Schemas: Flag to indicate whether or not the Packages should be transformed to new Schemas.

    Please check the naming of the procedure enabling and disabling the flag:

IN -> Oracle_01.sql
CREATE OR REPLACE PACKAGE emp_mgmt AS
PROCEDURE remove_emp (employee_id NUMBER );
END emp_mgmt;

CREATE OR REPLACE PACKAGE BODY emp_mgmt AS 
PROCEDURE remove_emp (employee_id NUMBER) IS 
   BEGIN 
      DELETE FROM employees 
      WHERE employees.employee_id = remove_emp.employee_id; 
      tot_emps := tot_emps - 1; 
   END; 
END emp_mgmt; 
  1. Transform Date as Timestamp:

Flag to indicate whether SYSDATE should be transformed into CURRENT_DATE or CURRENT_TIMESTAMP. This will also affect all DATE columns that will be transformed to TIMESTAMP.

IN -> Oracle_02.sql
CREATE TABLE DATE_TABLE(
    DATE_COL DATE
);

SELECT SYSDATE FROM DUAL;
  1. Transform OUTER JOINS to ANSI Syntax: Flag to indicate whether Outer Joins should be transformed to only ANSI syntax.

  2. Comment objects with missing dependencies: Flag to indicate if the user wants to comment on nodes that have missing dependencies.

  3. Disable EWI comments generation (errors, warnings and issues): Flag to indicate whether EWIs comments (Errors, Warnings, and Issues) will not be generated on the converted code. The default is false.

  4. Set encoding of the input files: The encoding code page number is used for parsing the source files. We only accept encodings supported by .NET Core. Here are the ones supported at the moment:

To review the Settings that apply to all supported languages, go to the following article.

DB Objects Names Settings

  1. Schema: The string value specifies the custom schema name to apply. If not specified, the original database name will be used. Example: DB1.myCustomSchema.Table1.

  2. Database: The string value specifies the custom database name to apply. Example: MyCustomDB.PUBLIC.Table1.

  3. Default: None of the above settings will be used in the object names.

Prepare Code Settings