
The tMSSqlOutputBulk and tMSSqlBulkExec components are used together in a two step process. In
the first step, an output file is generated. In the second step, this file is used in
the INSERT operation used to feed a database. These two steps are fused together in the
tMSSqlOutputBulkExec component, detailed in a
separate section. The advantage of using a two step process is that the data can be
transformed before it is loaded in the database.
Component family |
Databases/MSSql |
|
Function |
Executes the Insert action on the provided data. |
|
Purpose |
As a dedicated component, tMSSqlBulkExec offers gains in performance while |
|
Basic settings |
Property type |
Either Built-in or Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-in: No property data is |
|
|
Repository: Select the repository |
|
Use an existing connection |
Select this check box and in the Component List click the NoteWhen a Job contains the parent Job and the child Job, if you need to share an existing
For an example about how to share a database connection across Job levels, see |
|
Host |
Database server IP address |
|
Port |
Listening port number of DB server. |
|
Database |
Name of the database. |
|
Schema |
Name of the schema. |
|
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
|
Table |
Name of the table to be written. Note that only one table can be |
|
Action on table |
On the table defined, you can perform one of the following
None: No operation is carried
Drop and create table: The table is
Create table: The table does not
Create table if not exists: The
Drop table if exists and create:
Clear table: The table content is
Truncate table: The table content |
|
Schema and Edit |
A schema is a row description. It defines the number of fields to be processed and passed on Since version 5.6, both the Built-In mode and the Repository mode are |
|
|
Built-In: You create and store the schema locally for this |
|
|
Repository: You have already created the schema and When the schema to be reused has default values that are integers or functions, ensure that For more details, see https://help.talend.com/display/KB/Verifying+default+values+in+a+retrieved+schema. |
Click Edit schema to make changes to the schema. If the
|
||
|
Remote File Name |
Name of the file to be loaded. WarningThis file is located on the machine specified by the URI in |
Advanced settings |
Action |
Select the action to be carried out
Bulk insert Bulk update Bcp query out Depending on the action |
Bulk insert & Bulk update |
Additional JDBC parameters |
Specify additional connection properties for the DB connection you |
|
Fields terminated |
Character, string or regular expression to separate fields. |
|
Rows terminated |
Character, string or regular expression to separate rows. |
|
First row |
Type in the number of the row where the action should start |
|
Code page |
This value can be any of the followings: OEM (by default value) ACP RAW User-defined |
|
Data file type |
Select the type of data being handled. |
|
Output |
Select the type of output for the standard output of the MSSql to console, to global variable. |
|
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Bcp query out |
Fields terminated |
Character, string or regular expression to separate fields. |
|
Rows terminated |
Character, string or regular expression to separate rows. |
|
Data file type |
Select the type of data being handled. |
|
Output |
Select the type of output to pass the processed data onto:
to console: data is viewed in the
to global variable: data is put in |
|
tStat |
Select this check box to collect log data at the component |
Dynamic settings |
Click the [+] button to add a row in the table and fill The Dynamic settings table is available only when the For more information on Dynamic settings and context |
|
Usage |
This component is to be used along with tMSSqlOutputBulk component. Used together, they can |
|
Log4j |
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User 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. |
|
Limitation |
Due to license incompatibility, one or more JARs required to use this component are not |
For use cases in relation with tMSSqlBulkExec, see
the following scenarios: