tSybaseOutputBulkExec – Docs for ESB 5.x

Component family

Databases/Sybase

Function

Executes the Insert action on the data provided.

Purpose

As a dedicated component, it allows gains in performance during
Insert operations to a Sybase database.

Basic settings

Property type

Either Built-in or Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

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.

Server

Database server IP address

Currently, only localhost,
127.0.0.1 or the exact IP
address of the local machine is allowed for proper functioning. In
other words, the database server must be installed on the same
machine where the Studio is installed or where the Job using
tSybaseOutputBulkExec is
deployed.

Port

Listening port number of DB server.

Database

Name of the database

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.

Bcp utility

Name of the utility to be used to copy data over to the Sybase
server.

Batch row number

Number of lines in each processed batch.

Table

Name of the table to be written. Note that only one table can be
written at a time and that the table must exist for the insert
operation to succeed.

Action on table

On the table defined, you can perform one of the following
operations:

None: No operation is carried
out.

Drop and create a table: The table
is removed and created again.

Create a table: The table does not
exist and gets created.

Create a table if not exists: The
table is created if it does not exist.

Clear a table: The table content is
deleted.

File Name

Name of the file to be generated and loaded.

Append

Select this check box to add the new rows at the end of the
records.

Schema and Edit
Schema

A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.

Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.

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.

For more details, see https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema.

Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:

Advanced settings

Use an interface file

Select this check box to specify an interface file in the field
Interface file.

Additional JDBC parameters

Specify additional connection properties in the existing DB
connection, to allow specific character set support. E.G.:
CHARSET=KANJISJIS_OS to get support of Japanese characters.

Action on data

On the data of the table defined, you can perform:

Bulk Insert: Add multiple entries
to the table. If duplicates are found, job stops.

Bulk Update: Make simultaneous
changes to multiple entries.

Field terminator

Character, string or regular expression to separate fields.

DB Row terminator

String (ex: ”
“on Unix) to distinguish rows in the DB.

First row NO. of file

Type in the number of the file row where the action should start
at.

FILE Row terminator

Character, string or regular expression to separate fields in a
file.

Include Head

Select this heck box to include the column header.

Encoding

Regarding the source data, select the appropriate encoding from
the list or select Custom and
define it manually. This field is compulsory for DB data
handling.

Sybase encoding type

Select the Sybase-specific encoding type for the data to be
processed. This encoding type allows tSybaseOutputBulkExec to properly generate the
Sybase Bulk command.

Output

Select the type of output for the standard output of the Sybase
database:

to console,

to global variable.

tStatCatcher Statistics

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

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 more information on Dynamic settings and context
variables, see Talend Studio User Guide.

Usage

This component is mainly used when no particular transformation is
required on the data to be loaded onto the database.

Limitation

This component requires installation of its related jar files. For more information about the
installation of these missing jar files, see the section describing how to configure the
Studio of the Talend Installation and Upgrade Guide.

The database server/client must be installed on the same machine
where the Studio is installed or where the Job using tSybaseOutputBulkExec is deployed, so
that the component functions properly.