Property Type

Select the way the connection details
will be set.

• Built-In: The connection details will be set
  locally for this component. You need to specify the values for all
  related connection properties manually.

• Repository: The connection details stored
  centrally in Repository > Metadata will be reused by this component. You need to click
  the […] button next to it and in the pop-up
  Repository Content dialog box, select the
  connection details to be reused, and all related connection
  properties will be automatically filled in.

DB Version

Select the version of the database.

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

Host

The IP address or hostname of the database.

Port

The listening port number of the database.

Database

The name of the database.

Schema

The schema of the database.

Username and Password

The database 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

The name of the table into which data will be written.

Action on table

Select an operation to be performed on the table defined.

• None: No operation is carried out.

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

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

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.

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

Click Edit schema to make changes to the
schema. Note that if you make changes, the schema automatically becomes built-in.

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

SCD Editor

Click the […] button and in the SCD component
editor dialog box displayed, configure the data flow for slowly changing
dimension outputs.

For more information, see SCD management methodology.

Use memory saving mode

Select this check box to maximize system performance.

Die on error

Select the check box to stop the execution of the Job when an error
occurs.

Clear the check box to skip any rows on error and complete the
process for error-free rows.

When errors are skipped, you can collect the rows on error
using a Row > Reject connection.

Additional JDBC Parameters

Specify additional JDBC parameters for the
database connection being created.

This property is not available when the Use an existing connection check box is
selected.

End date time details

Specify the time value of the SCD end date time setting in the format of
HH:mm:ss. The default value is 12:00:00.

This property is available only when the SCD Type 2 method is used and Fixed
year value is selected for creating the SCD Type 2 end date in the SCD
editor.

Debug mode

Select this check box to display each step during processing entries in a database.

tStatCatcher Statistics

Select this check box to gather the Job processing metadata at the Job level
as well as at each component level.

NB_LINE_INSERTED

The number of rows inserted. This is an After variable and it returns an integer.

NB_LINE_UPDATED

The number of rows updated. This is an After variable and it returns an integer.

NB_LINE_REJECTED

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.

Usage rule

This component is usually used as an end component of a Job or Subjob and it
always needs an input link.

Talend Studio and the
Vertica database create very fast and affordable data warehouse and data mart applications.
For more information about how to configure
Talend Studio
to connect to Vertica, see Talend and HP Vertica Tips and
Techniques.

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.