JDBC V2 Connector

Back Next

Rules and guidelines for creating a target at runtime

When you configure a mapping with the

Create New at Runtime

option, consider the following rules:

Do not edit the metadata in the target object. If you edit the metadata, the changes are not reflected at runtime.

When a target table exists, the Secure Agent uses the same target table.

When you configure an override of the schema name and table while creating a target at runtime, the Secure Agent creates an empty table in the default database.

Create a target table at runtime

Download Guide

Watch

Comments

Cloud Connectivity Homepage

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Alessio Giordani - December 10, 2024

Hello documentation team,

it should be listed here that "Create New at Runtime" is only supported for PostgreSQL or Azure SQL Database database type.

When I read the note: "Before you create a target table at runtime in PostgreSQL or Azure SQL Database, select the appropriate database type in the JDBC V2 connection." in this link https://docs.informatica.com/integration-cloud/data-integration-connectors/current-version/jdbc-v2-connector/mappings-in-jdbc-v2-connector/jdbc-v2-targets-in-mappings/create-a-target-table-at-runtime.html

it sounded to me like a specific setting to apply when using those targets, not that create table at runtime was the only supported in this case.

Regards,

Alessio

Informatica Documentation Team - December 11, 2024

Hi Alessio,

We're working to address your comment and will get back to you.

Regards,

Informatica Documentation Team

Rename Saved Search

Table of Contents

JDBC V2 Connector

JDBC V2 Connector

Rules and guidelines for creating a target at runtime

Rules and guidelines for creating a target at runtime