Pro2 can be customized to suit your needs. You can generate Pro2 specific fields, can add and delete index information on the target database and change table and field names.

Customizable by table, by field/column, or record/row

All tables or a subset of tables can be replicated. In addition, not all fields within the tables selected for replication need to be replicated. In addition, logic can be added to “filter” records in selected tables so that only those records that meet the specified criteria are replicated.

Custom transformations using ABL supported logic

Data can be manipulated with ABL logic before being written to the target database. For example, field values can be modified based on business logic or target side only columns can be populated with data consolidated from multiple source fields.

Generating Pro2 specific fields

Pro2 provides an option Delta DF Pro2Pro to generate only Pro2 specific fields for your target database. In cases where the source schema is already replicated to your target database, you can use Delta DF Pro2Pro to generate only Pro2 specific fields, and thereby avoid unnecessary replication of source schema.

Oracle Specialization: Use the following properties to generate Oracle specific output:
  • ORACLE_USE_LOGICAL—This property is responsible for converting logical field to number (1).
  • ORACLE_USE_SCALE—This property is responsible for adding precision and scale for decimal fields.
By default, the value of these properties is set to NO. To use these properties, set the value to YES.

Target side index information

Customers can add and delete index information on the target database without interfering with Pro2 Replication as long as no unique keys are added and as long as the PRROWID key is not modified. Pro2 compiles the CREATE INDEX statements into a separate file named <dbname>-<targettype>-index.sql file. These index statements are applied to the target only if the customer wants them.

Standard modifications to table and field names

You can modify table and field names in Pro2.
  • Extent fields—Array fields from the OpenEdge source database are created as individual fields in the target database schema.
  • Reserved words—Any table or column names that are reserved words in the target database server or in OpenEdge must be renamed. Often this is done by appending an underscore “_” to the end of the column name, however, the column can be renamed to anything that is not a reserved word.