tMSSqlTableList Standard properties
These properties are used to configure tMSSqlTableList running in the Standard Job framework.
The Standard tMSSqlTableList component belongs to the Databases family.
The component in this framework is available in all Talend products.
Basic settings
Database |
Select the desired database type from the list and click Apply. |
Component list | 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. |
Advanced settings
tStatCatcher Statistics | Select this check box to collect log data at the component level. |
Global Variables
Global Variables |
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 more information about variables, see Using contexts and variables. |
Usage
Usage rule | This component is to be used along with MSSql components, especially with tMSSqlConnection. |
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 Dynamic schema and Creating a context group and define context variables in it. |