Table of Contents

Search

  1. Preface
  2. Introduction to PostgreSQL Connector
  3. Connections for PostgreSQL
  4. Mappings and mapping tasks with PostgreSQL Connector
  5. PostgreSQL objects in mapping tasks
  6. Lookup transformation
  7. SQL transformation
  8. Migrating a mapping
  9. PostgreSQL SQL ELT optimization
  10. Data type reference

PostgreSQL Connector

PostgreSQL Connector

Migration options

Migration options

When you migrate, you can choose from one of the following options to update the object path:

Option 1. Update the connection properties to reference the new object

When you import the mapping into Org 2, in the
Review Connections
section, you can change the existing connection to map to the connection that has access to the specified schema and table in Org 2.

Option 2. Override the properties from the advanced properties

Before the migration, specify the required schema and table name for the object from Org 2 in the advanced properties of the Org 1 mapping.
After the migration, when you run the mapping, the Secure Agent uses the configured advanced parameters to override the object specified in the mapping imported from Org 1.

Option 3. Parameterize the properties in the mapping

You can choose to parameterize the advanced attributes, such as the schema and table name before the migration. You can configure input parameters, in-out parameters, and parameter files in the mapping.
If you have used in-out parameters, you can change the schema and table attributes using the parameter file so that the changes are applied when the task runs.
You cannot override the input parameters from the parameter file in the advanced properties. You must use the in-out parameter to override the value from the parameter file.
Parameterizing only the advanced properties, but not the object in the mapping
If you want to parameterize only the advanced properties and use them at runtime, select a placeholder object in the object properties in the mapping and then specify an override to this placeholder object from the advanced properties. Ensure that the placeholder object contains the same metadata as the corresponding table that you specify as an override. When you run the mapping, the value specified in the advanced property overrides the placeholder object.
Parameterizing both the object and the advanced properties
If you want to keep both the PostgreSQL object type and the advanced fields parameterized, you must leave the
Allow parameter to be overridden at runtime
option unselected in the input parameter window while adding the parameters, and then select the required object at the task level. When you run the task, the values specified in the advanced properties take precedence.

0 COMMENTS

We’d like to hear from you!