# tRedshiftRow Acts on the actual DB structure or on the data (although without handling data), depending on the nature of the query and the database. The SQLBuilder tool helps you write easily your SQL statements. tRedshiftRow is the specific component for this database query. It executes the SQL query stated onto the specified database. The row suffix means the component implements a flow in the Job design although it does not provide output. ## tRedshiftRow Standard properties These properties are used to configure tRedshiftRow running in the Standard Job framework. The Standard tRedshiftRow component belongs to the Cloud and the Databases families. The component in this framework is available in all Talend products. Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component). ## Basic settings | Properties | Description | | --- | --- | | Database | Select the desired database type from the list and click
Apply. | | Property type | Either Built-in or Repository
.

| | Use an existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined.

Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).

  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 [Sharing a database connection](https://help.qlik.com/talend/r/en-US/7.3/studio-user-guide/sharing-database-connection). | | Driver version | Select the Redshift driver version to be used: Driver v1 or
Driver v2.

Information noteNote: This option is available only when you have installed the 8.0.1-R2022-04
Talend Studio
Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | Host | Hostname or IP address of the database server. | | Port | Listening port number of the database server. | | Database | Name of the database.

The bucket and the Redshift database to be used
must be in the same region on Amazon. This could avoid the S3ServiceException errors known to
Amazon. For further information about these errors, see [S3ServiceException Errors](https://docs.aws.amazon.com/redshift/latest/dg/s3serviceexception-error.html). | | Schema | Exact name of the schema. | | Username and Password | Database user authentication data.

To enter the password, click the [...] button
next to the password field, enter the password in double quotes in the pop-up dialog box,
and click OK to save the settings. | | Use String JDBC parameters | Set JDBC properties in a string. If you select this option, enter your JDBC parameter string in
the Additional JDBC Parameters field; otherwise, enter JDBC
properties and property values in the Additional JDBC
Parameters table.

This option is not available if Driver v1 is selected from
the Driver version drop-down list.

Information noteNote: This option is available only when you have installed the 8.0.1-R2022-04
Talend Studio
Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | Additional JDBC Parameters | Specify additional JDBC properties for the connection you are creating. The
properties are separated by ampersand & and each property is a key-value pair. For
example, *ssl=true &
sslfactory=com.amazon.redshift.ssl.NonValidatingFactory*, which means the
connection will be created using SSL.

This field is not available if Driver v2 is selected
from the Driver version drop-down list and the
Use String JDBC parameters option is not
selected. | | Additional JDBC Parameters (table) | Specify JDBC properties in table rows.

To specify a JDBC property, add a row in the table by clicking the plus button on
the bottom of this table, enter the property name in the
Key column, and then enter the property value in the
Value column.

This table is available when Driver v2 is selected from the
Driver version drop-down list and the Use
String JDBC parameters option is not selected.

Information noteNote: This option is available only when you have installed the 8.0.1-R2022-04
Talend Studio
Monthly update or a later one delivered by Talend. For more information, check with your administrator. | | 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.

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

| | Table Name | Name of the table from which the data will be read. | | Query type | Either Built-in or Repository
.

| | Guess Query | Click the Guess Query button to
generate the query which corresponds to your table schema in the Query
field. | | Query | Enter your database query paying particularly attention to properly
sequence the fields in order to match the schema definition.

Information noteNote: All statements in
this field will be executed in a single transaction. To have multiple
statements executed in different transactions, put each of them in a separate
tRedshiftRow component. | | Die on error | This check box is selected by default. Clear the check box to skip the
row on error and complete the process for error-free rows. If needed,
you can retrieve the rows on error through a Row > Rejects
link. | ## Advanced settings | Properties | Description | | --- | --- | | Propagate QUERY's recordset | Select this check box to insert the result of the query into a COLUMN
of the current flow. Select this column from the use column list.

Information noteNote: This option allows the component to have a different schema from
that of the preceding component. Moreover, the column that holds the
QUERY's recordset should be set to the type of *Object* and this component is usually
followed by tParseRecordSet. | | Use PreparedStatement | Select this check box if you want to query the database using a
PreparedStatement. In the Set PreparedStatement
Parameter table, define the parameters represented by "?"
in the SQL instruction of the Query
field in the Basic Settings tab.


Parameter Index: Enter the parameter
position in the SQL instruction.


Parameter Type: Enter the parameter
type.


Parameter Value: Enter the parameter
value.

Information noteNote: This option is very useful if you need to execute the same query
several times. Performance levels are increased. | | Commit every | Number of rows to be completed before committing batches of rows
together into the database. This option ensures transaction quality (but
not rollback) and above all better performance on executions. | | JDBC url | Select a way to access to an Amazon Redshift database from the
JDBC url drop-down list.

| | tStat
Catcher Statistics | Select this check box to collect log data at the component
level. | ## Global Variables | Variables | Description | | --- | --- | | Global Variables | NB\_LINE:
the number of rows processed. This is an After variable and it returns an integer.

Note that if the Propagate QUERY's recordset option is
selected in the Advanced settings view, this variable
returns the number of single ResultSet, which is 1.


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 checkbox is
cleared, if the component has this checkbox.

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 more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component offers the flexibility benefit of the database query
and covers all possible SQL queries. | | 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](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). | | 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 Talend Studio. For
details, see [Installing external modules](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/installing-external-modules). |