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

Rules and guidelines for migrating a mapping

Rules and guidelines for migrating a mapping

Consider the following rules and guidelines when you use the same or a different object path for the migrated mapping:
  • The following table lists the transformation, object type, and the fields in the advanced properties of a mapping that you can retain when you migrate to the new environment:
    Transformations
    Object Type
    Advanced Fields
    Source
    Single object
    Schema and table name
    Lookup
    Single object
    Applicable for unconnected, and connected cached and uncached.
    Target
    Single object
  • You cannot dynamically refresh the data object schema at runtime. You must maintain the same metadata for the table selected in the source, target, or lookup transformations and the corresponding advanced field overrides as schema change handling is not applicable.
  • You cannot migrate a mapping that uses the Hosted Agent as the runtime environment.
  • If the mapping contains an advanced filter for the object in the query options section and an override to the object in the advanced properties, you must use the object that you specify as an override in the advanced properties to define the condition.
  • You cannot override the schema and table name from the advanced properties if the mapping contains multiple objects.

0 COMMENTS

We’d like to hear from you!