August 17, 2023

tSybaseBulkExec – Docs for ESB 5.x



tSybaseBulkExec Properties

The tSybaseOutputBulk and tSybaseBulkExec components are generally used together as parts 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 tSybaseOutputBulkExec 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.

Component family




Executes the Insert action on the data provided.


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

Basic settings

Property type

Either Built-in or

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



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.


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:

  1. 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.

  2. 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



Database server IP address

Available when you select Bulk
from the Action on
list in the Advanced
view of tSybaseBulkExec.



Listening port number of DB server.

Available when you select Bulk
from the Action on
list in the Advanced
view of tSybaseBulkExec.



Database name


Username and

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.


Sybase Schema

Name of the database schema you want to use.


Bcp Utility

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



IP address of the database server for the Bcp utility


Batch size

Number of lines in each processed batch.



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

None: No operation is carried

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

Truncate table: The table content
is deleted. You do not have the possibility to rollback the


File Name

Name of the file to be loaded.


This file should be located on the same machine as the
database server.


Schema and Edit

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


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

  • 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

  • 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

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.


With the row/field separators compliant
with the Sybase syntax, this component allows for the use of
Sybase-orientated characters, such as x09.


Row Terminator

String (ex: ”
” in Unix) to separate lines.


Head row

Number of head lines to be ignored in the beginning of a



Select the encoding from the list, or enter the encoding between double quotes if it does
not exist in the list. This field is compulsory for database data handling.



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

to console,

to global variable.


tStataCatcher statistics

Select this check box to gather the Job processing metadata at a
Job level as well as at each 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.

Global Variables

NB_LINE_DATA: the number of rows read. This is an After
variable and it returns an integer.

NB_LINE_BAD: the number of rows rejected. This is an
After variable and it returns an integer.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio
User Guide.


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


The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User

For more information on the log4j logging levels, see the Apache documentation at


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

As opposed to the Oracle dedicated bulk component, no action on
data is possible using this Sybase dedicated component.

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.

Document get from Talend
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x