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 available in all Talend
products.
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.
Basic settings
Database |
Select a type of database from the list and click |
Property type |
Either Built-in or |
 |
Built-in: No property data stored |
 |
Repository: Select the repository |
Use an existing connection |
Select this check box and in the Component List click the relevant connection component to 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:
For an example about how to share a database connection |
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 |
DB user authentication data. To enter the password, click the […] button next to the |
Table |
Name of the table to be written. Note that only one table can be |
Action on table |
On the table defined, you can perform one of the following
None: No operation is carried
Drop and create table: The table is
Create table: The table does not
Create table if not exists: The
Drop table if exists and create:
Clear table: The table content is
Truncate table: The table content |
File Name |
Name of the file to be loaded. Warning:
This file is located on the machine specified by the URI in |
Schema and Edit |
A schema is a row description. It defines the number of fields Click Edit
|
 |
Built-In: You create and store the schema locally for this component |
 |
Repository: You have already created the schema and stored it in the When the schema to be reused has default values that are You can find more details about how to |
Advanced settings
Additional JDBC Parameters |
Specify additional JDBC parameters for the This property is not available when the Use an existing connection |
Action |
Select the action to be carried out
Bulk insert |
Field terminated by |
Character, string or regular expression to separate fields. |
tStat |
Select this check box to collect log data at the component |
Usage
Usage rule |
This dedicated component offers performance and flexibility of DB2 |
Dynamic settings |
Click the [+] button to add a row in the table The Dynamic settings table is For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic |
Related scenarios
For tPostgresPlusBulkExec related topics, see: