tPostgresPlusBulkExec

Improves performance during Insert operations to a DB2 database.

The tPostgresPlusBulkExec executes
the Insert action on the data provided.

The tPostgresplusOutputBulk and tPostgresplusBulkExec components are generally used together as part of
a two step process. In the first step, an output file is generated. In the second step,
this file is used in the INSERT operation used to feed a database. These two steps are
fused together in the tPostgresPlusOutputBulkExec
component, detailed in a separate section. The advantage of using two separate
components is that the data can be transformed before it is loaded in the
database.

tPostgresPlusBulkExec Standard properties

These properties are used to configure tPostgresPlusBulkExec running in the Standard Job framework.

The Standard
tPostgresPlusBulkExec component belongs to the Databases family.

The component in this framework is generally available.

Basic settings

Property type	Either Built-in or Repository .
	Built-in: No property data stored centrally.
	Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved.
Use an existing connection	Select this check box and in the Component List click the relevant connection component to reuse the connection details you already defined. Note: When a Job contains the parent Job and the child Job, if you need to share an existing connection between the two levels, for example, to share the connection created by the parent Job with the child Job, you have to: In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection. In the child level, use a dedicated connection component to read that registered database connection. For an example about how to share a database connection across Job levels, see Talend Studio User Guide.
DB Version	List of database versions.
Host	Database server IP address
Port	Listening port number of DB server.
Database	Name of the database
Schema	Name of the DB schema.
Username and Password	DB user authentication data. To enter the password, click the […] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.
Table	Name of the table to be written. Note that only one table can be written at a time
Action on table	On the table defined, you can perform one of the following operations: None: No operation is carried out. Drop and create table: The table is removed and created again. Create table: The table does not exist and gets created. Create table if not exists: The table is created if it does not exist. Drop table if exists and create: The table is removed if it already exists and created again. Clear table: The table content is deleted. Truncate table: The table content is deleted. You do not have the possibility to rollback the operation.
File Name	Name of the file to be loaded. Warning: This file is located on the machine specified by the URI in the Host field so it should be on the same machine as the database server.
Schema and Edit Schema	A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available: View schema: choose this option to view the schema only. Change to built-in property: choose this option to change the schema to Built-in for local changes. Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the [Repository Content] window.
	Built-In: You create and store the schema locally for this component only. Related topic: see Talend Studio User Guide.
	Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide. When the schema to be reused has default values that are integers or functions, ensure that these default values are not enclosed within quotation marks. If they are, you must remove the quotation marks manually. You can find more details about how to verify default values in retrieved schema in Talend Help Center (https://help.talend.com).

Advanced settings

Action	Select the action to be carried out Bulk insert Bulk update Depending on the action selected, the required information varies.
Field terminated by	Character, string or regular expression to separate fields.
tStat Catcher Statistics	Select this check box to collect log data at the component level.

Action

Select the action to be carried out

Bulk insert
Bulk update Depending on the action selected, the
required information varies.

Field terminated by

Character, string or regular expression to separate fields.

tStat
Catcher Statistics

Select this check box to collect log data at the component
level.

Usage

Usage rule	This dedicated component offers performance and flexibility of DB2 query handling.
Dynamic settings	Click the [+] button to add a row in the table and fill the Code field with a context variable to choose your database connection dynamically from multiple connections planned in your Job. This feature is useful when you need to access database tables having the same data structure but in different databases, especially when you are working in an environment where you cannot change your Job settings, for example, when your Job has to be deployed and executed independent of Talend Studio . The Dynamic settings table is available only when the Use an existing connection check box is selected in the Basic settings view. Once a dynamic parameter is defined, the Component List box in the Basic settings view becomes unusable. For examples on using dynamic parameters, see Scenario: Reading data from databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic settings and context variables, see Talend Studio User Guide.

Usage rule

This dedicated component offers performance and flexibility of DB2
query handling.

Dynamic settings

Click the [+] button to add a
row in the table and fill the Code field
with a context variable to choose your database connection dynamically from
multiple connections planned in your Job. This feature is useful when you
need to access database tables having the same data structure but in
different databases, especially when you are working in an environment where
you cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of
Talend Studio
.

The Dynamic settings table is
available only when the Use an existing
connection check box is selected in the Basic settings view. Once a dynamic parameter is
defined, the Component List box in the
Basic settings view becomes unusable.

For examples on using dynamic parameters, see Scenario: Reading data from databases through context-based dynamic connections and Scenario: Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
settings and context variables, see
Talend Studio User Guide.

Related scenarios

For tPostgresPlusBulkExec related topics, see:

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 6.x

0 Comments

Inline Feedbacks

View all comments

tPostgresPlusBulkExec – Docs for ESB 6.x