|
Component family
|
Databases/Teradata
|
|
|
Function
|
tTeradataConnection opens a
connection to the database for a current transaction.
|
|
Purpose
|
This component is used to open a connection to the specified database that can then be reused in the subsequent subjob or subjobs.
|
|
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.
|
|
|
Host
|
Database server IP address.
|
|
|
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.
|
|
|
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.
Note
You can set the encoding parameters through this field.
|
|
|
Use or register a shared DB Connection
|
Select this check box to share your connection or fetch a
connection shared by a parent or child Job. This allows you to share
one single DB connection among several DB connection components from
different Job levels that can be either parent or child.
Warning
This option is incompatible with the Use dynamic job
and Use an independent process to run subjob options of
the tRunJob component. Using a shared connection
together with a tRunJob component with either of these
two options enabled will cause your Job to fail.
Shared DB Connection Name: set or
type in the shared connection name.
|
|
Advanced settings
|
Query band
|
Select this check box to use the Teradata Query Banding feature to add metadata to the query
to be processed, such as the user running the query. This can help you, for example,
identify the origin of this query.
Once selecting the check box, the Query Band parameters
table is displayed, in which you need to enter the metadata information to be added. This
information takes the form of key/value pairs, for example, DpID in the Key column and Finance in the Value
column.
This check box actually generates the SET QUERY_BAND FOR SESSION statement with the key/value
pairs declared in the Query Band parameters table. For
further information about this statement, see http://www.info.teradata.com/HTMLPubs/DB_TTU_14_00/index.html#page/SQL_Reference/B035_1144_111A/End_Logging-Syntax.027.143.html.
|
| |
Auto Commit
|
Select this check box to commit any changes to the database automatically upon the
transaction.
With this check box selected, you cannot use the corresponding commit component to commit
changes to the database; likewise, when using the corresponding commit component, this check
box has to be cleared. By default, the auto commit function is disabled and changes must be
committed explicitly using the corresponding commit component.
Note that the auto commit function commits each SQL statement as a single transaction
immediately after the statement is executed while the commit component does not commit only
until all of the statements are executed. For this reason, if you need more room to manage
your transactions in a Job, it is recommended to use the commit component.
|
|
|
tStatCatcher Statistics
|
Select this check box to collect log data at the component
level.
|
|
Usage
|
This component is more commonly used with other tTeradata*
components, especially with the tTeradataCommit and tTeradataRollback components.
|
|
Log4j
|
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User
Guide.
For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.
|
|
Limitation
|
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. For details, see https://help.talend.com/display/KB/How+to+install+external+modules+in+the+Talend+products
or the section describing how to configure the Studio in the Talend Installation and Upgrade
Guide.
|
