Databases/MS SQL Server
Select the tMSSqlConnection component in the list if more than one connection are planned for the current job.
Where clause for table name selection
Enter the Where clause to identify the tables to iterate on.
Select this check box to collect log data at the component level.
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 Scenario 3: Reading data from MySQL databases through context-based dynamic connections and Scenario: 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.
CURRENT_TABLE: the name of the table currently iterated upon. This is a Flow variable and it returns a string.
NB_TABLE: the number of tables iterated upon so far. This is a Flow variable and it returns an integer.
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.
This component is to be used along with MSSql components, especially with tMSSqlConnection.
If you are using a subscription-based version of the Studio, 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.