Skip to main content Skip to complementary content

tNetezzaClose Standard properties

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

The Standard tNetezzaClose component belongs to the Databases family.

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 Dynamic database components.

Basic settings

Database

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

Component list

Select the tNetezzaConnection component in the list if more than one connection are planned for the current Job.

Advanced settings

tStat Catcher Statistics

Select this check box to collect log data at the component level.

Usage

Usage rule

This component is to be used along with Netezza components, especially with tNetezzaConnection and tNetezzaCommit.

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.

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.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!