Component family |
Databases/MS SQL Server | |
Basic settings |
Property type |
Either Built-in or Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. |
|
|
Built-in: No property data stored centrally. |
|
|
Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved. |
|
File Name |
Name of the file to be generated. WarningThis file is generated on the local machine or a shared folder on the LAN. |
|
Append |
Select this check box to add the new rows at the end of the records. |
|
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. The schema is either Built-In or stored remotely in the Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. |
|
|
Built-In: You create and store the schema locally for this component only. Related topic: see Talend Studio User Guide. |
|
|
Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs. Related topic: see Talend Studio User Guide. When the schema to be reused has default values that are integers or functions, ensure that these default values are not enclosed within quotation marks. If they are, you must remove the quotation marks manually. For more details, see the article Verifying default values in a retrieved schema on |
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
| ||
Advanced settings |
Row separator |
String (ex: "\n"on Unix) to distinguish rows. |
|
Field separator |
Character, string or regular expression to separate fields. |
|
Include header |
Select this check to include the column header. |
|
Encoding |
Select the encoding from the list or select Custom and define it manually. This field is compulsory for DB data handling. |
|
tStaCatcher statistics |
Select this check box to collect log data at the component level. |
Global Variables |
NB_LINE: the number of rows processed. This is an After 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. | |
Usage |
This component is to be used along with tMSSqlBulkExec component. Used together they offer gains in performance while feeding a MSSql database. | |
Log4j | 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. |