Select a type of database from the list and click
Apply.

Property type

Either Built-in or
Repository
.

Built-in: No property data is stored
centrally.

Repository: Select the repository file
in which the properties are stored. The fields that follow are completed
automatically using the data retrieved.

JDBC Provider

Select the provider of the JDBC driver to be used, either Microsoft (recommended) or Open
source JTDS.

When using this component with Datasource in Talend Runtime, you need
to use the Open source JTDS driver.

Note that when Microsoft is selected, you
need to download the Microsoft JDBC Driver for SQL Server on Microsoft Download Center, unpack
the downloaded zip file, choose a jar in the unzipped folder based on your JRE version,
rename the jar to mssql-jdbc.jar and install it manually. For more
information about choosing the jar, see the System Requirements information on Microsoft Download Center.

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.

Host

Database server IP address

Port

Listening port number of DB server.

Database

Name of the database.

Schema

Name of the 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 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 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.

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. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

Built-In: You create and store the schema locally for this component
only.

Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

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

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.

Remote File Name

Name of the file to be loaded.

Action

Select the action to be carried out.

Bulk insert, Bulk update and
Bcp query out, depending on the action selected, the
requied information varies.

Additional JDBC parameters

Specify additional JDBC parameters for the
database connection created.

This property is not available when the Use an existing connection
check box in the Basic settings view is selected.

Fields terminated by

Character, string or regular expression to separate fields.

Rows terminated

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

First row

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

Code page

OEM code pages used to map a specific set of characters
to numerical code point values.

Data file type

Select the type of data being handled.

Output

This property is available when BCP query out is
selected from the Action drop-down list.

Fire Triggers

Select this check box to execute any insert trigger defined on the table into
which data will be loaded during the bulk insert operation.

This property is available when Bulk insert is selected
from the Action drop-down list.

tStatCatcher Statistics

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

Enable parallel execution

Note that when parallel execution is enabled, it is not possible to use global
variables to retrieve return values in a subjob.

Usage rule

This component is to be used along with tMSSqlOutputBulk component. Used together, they
can offer gains in performance while feeding a MSSql database.

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

Due to license incompatibility, one or more JARs required to use
this component are not provided. You can install the missing JARs for this particular
component by clicking the Install button
on the Component tab view. You can also
find out and add all missing JARs easily on the Modules tab in the
Integration
perspective of your studio. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com).