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

Validation type

DQ rule validation: Validate data in
the database against Data Quality rules.

Property type

Either Built-in or Repository.

Built-in: No property data stored
centrally.

Repository: Select the repository
file where Properties are stored. The fields that come after are
pre-filled in using the fetched data.

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.

JDBC Provider

Drop-down list of available JDBC providers.

Host

Database server IP address.

Port

Listening port number of database server.

Database

Name of the database.

MsSQL schema

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

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.

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.

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.

Table Name

Enter the name of the table to be read.

Where clause

Enter a WHERE clause to define a row filter on the table.

You can use the WHERE clause to filter the rows you want to
analyze in the table. This WHERE clause enables you then to retrieve
valid and invalid data that match certain specified criteria or
conditions.

DQ rule list

Select from the list the rule against which you want to check the database rows.

Query type

Either Built-in or Repository:

Built-in: Fill in manually the
query statement or build it graphically using SQLBuilder.

Repository: Select the relevant query stored in the
Repository. The Query field is filled
in accordingly.

Guess query

Click the Guess Query button to generate the query
which corresponds to your table schema in the Query field.

Guess schema

Click the Guess Schema button to
retrieve the schema from the table.

Query

Enter your DB query paying particular attention to properly
sequence the fields in order to match the schema definition.

Additional JDBC Parameters

Specify additional connection properties for the DB connection you
are creating. This option is not available if you have selected the
Use an existing connection
check box in the Basic
settings.

Enable stream

Select this check box to enable streaming over buffering. This allows
reading from large tables without consuming large amount of memory in order
to optimize the performance.

Trim all the String/char columns

Select this check box to remove leading and trailing
whitespace from all the String/Char columns.

Trim column

Remove leading and trailing whitespace from defined
columns.

tStatCatcher Statistics

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

Global Variables

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an
integer.

QUERY: the query statement being processed. This is a Flow
variable and it returns a string.

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 +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage rule

This component is usually used as a start component of a Job or
subJob and it always needs an output link.

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.