# tRedshiftConnection Standard properties

These properties are used to configure tRedshiftConnection running in the Standard Job framework.

The Standard tRedshiftConnection 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 .

## Basic settings

| Database | Select a type of database from the list and click<br>Apply. |
| --- | --- |
| Property type | Either Built-in or<br>Repository. |
|  | Built-in: No property data stored<br>centrally. |
|  | Repository: Select the repository file<br>in which the properties are stored. The fields that follow are completed<br>automatically using the data retrieved. |
| Host | Host name or IP address of DB server. |
| Port | Listening port number of DB server. |
| Database | Name of the database.<br><br>The bucket and the Redshift database to be used<br>must be in the same region on Amazon. This could avoid the S3ServiceException errors known to<br>Amazon. For further information about these errors, see [S3ServiceException Errors](https://docs.aws.amazon.com/redshift/latest/dg/s3serviceexception-error.html). |
| Schema | Name of the schema. |
| Username and Password | DB user authentication data.<br><br>To enter the password, click the [...] button next to the<br>password field, and then in the pop-up dialog box enter the password between double quotes<br>and click OK to save the settings. |
| Additional JDBC Parameters | Specify additional JDBC properties for the connection you are creating. The<br>properties are separated by ampersand & and each property is a key-value pair. For<br>example, *ssl=true &<br>sslfactory=com.amazon.redshift.ssl.NonValidatingFactory*, which means the<br>connection will be created using SSL. |
| Use or register a shared DB Connection | Select this check box to share your<br>database connection or fetch a database connection shared by a parent or child Job,<br>and in the Shared DB Connection Name field displayed, enter the<br>name for the shared database connection. This allows you to share one single database<br>connection (except the database schema setting) among several database connection<br>components from different Job levels that can be either parent or child.<br><br>This option is<br>incompatible with the Use dynamic job and Use an<br>independent process to run subjob options of the<br>tRunJob component. Using a shared connection together with a<br>tRunJob component with either of these two options enabled<br>will cause your Job to fail. |

## Advanced settings

| Log file | Specify the path to the log file to be generated during the<br>data retrieval process.<br><br>Note that if the logging information needs to be saved and<br>this component reuses the connection created by a tRedshiftConnection component, you must specify the property *loglevel=1/2/3* in the Additional JDBC Parameters<br>field of the tRedshiftConnection component.<br><br>There is no limitation on the size of the log file. If the<br>specificed log file already exists, it will be overwritten. |
| --- | --- |
| Logging level | Select a logging level from the drop-down list to specify<br>which kind of events will be logged in the log file. |
| Auto Commit | Select this check box to commit any changes to the database<br>automatically upon the transaction.<br><br>With this check box selected, you cannot use the corresponding<br>commit component to commit changes to the database; likewise, when using the<br>corresponding commit component, this check box has to be cleared. By<br>default, the auto commit function is disabled and changes must be committed<br>explicitly using the corresponding commit component.<br><br>Note that the auto commit function commits each SQL statement as a<br>single transaction immediately after the statement is executed while the<br>commit component does not commit only until all of the statements are<br>executed. For this reason, if you need more room to manage your transactions<br>in a Job, it is recommended to use the commit component. |
| JDBC url | Select a way to access to an Amazon Redshift database from the<br>JDBC url drop-down list.<br><br><ul> <li> <span>Standard</span>: Use the          standard way to access the Redshift database.</li> <li> <span>SSO</span>: Use the IAM          Single Sign-ON (SSO) authentication way to access the Redshift Database. Before selecting          this option, ensure that the IAM role added to your Redshift cluster has appropriate          access rights and permissions to this cluster. You can ask the administrator of your AWS          services for more details.<p>This option is available only when <span>Use an existing connection</span> check box is not selected from            the <span>Basic settings</span>. </p> </li> </ul> |
| tStatCatcher Statistics | Select this check box to gather the Job processing metadata at<br>a Job level as well as at each component level. |

## Usage

| **Usage rule** | This component is more commonly used with other tRedshift\* components,<br>especially with the tRedshiftCommit and<br>tRedshiftRollback<br>components. |
| --- | --- |
| Limitation | Due to license incompatibility, one or more JARs required to use<br>this component are not provided. You can install the missing JARs for this particular<br>component by clicking the Install button<br>on the Component tab view. You can also<br>find out and add all missing JARs easily on the Modules tab in the<br>Integration<br>perspective of your studio. For<br>details, see *Installing external modules*.<br>You can find more details about how to install external modules in<br>Talend Help Center ([https://help.talend.com](https://help.talend.com/)). |