# tSQLiteOutput Executes the action defined on the table and/or on the data contained in the table, based on the flow incoming from the preceding component in the job. tSQLiteOutput writes, updates, makes changes or suppresses entries in an SQLite database. As it embeds the SQLite engine, no need of connecting to any database server. ## tSQLiteOutput Standard properties These properties are used to configure tSQLiteOutput running in the Standard Job framework. The Standard tSQLiteOutput 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 [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component). ## Basic settings | Properties | Description | | --- | --- | | Database | Select the desired database type from the list and click
Apply. | | Property
type |

Either Built-in or Repository .
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.

| | Use an existing
connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined.

Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).

In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels,
see [Sharing a database connection](https://help.qlik.com/talend/r/en-US/7.3/studio-user-guide/sharing-database-connection). | | ![](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/Save_Icon.png) | Click this icon to
open a database connection wizard and store the database connection
parameters you set in the component Basic settings view.

For more information about setting up
and storing database connection parameters, see [Centralizing database metadata](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/centralizing-database-metadata). | | Database | Filepath to the
Database file | | Table | Name of the table to
be written. Note that only one table can be written at a
time | | Action on
table | On the table
defined, you can perform one of the following operations:

None: No operation is carried out.

Drop and create a table: The table is
removed and created again.

Create a
table: The table does not exist and gets created.

Create a table if not exists: The table
is created if it does not exist.

Drop a table if exists
and create: The table is removed if it already exists
and created again.

Clear a table: The table
content is deleted. | | Action on
data | On the data of the table defined, you can
perform:

Insert: Add new entries to the table. If
duplicates are found, job stops.

Update: Make
changes to existing
entries.

Information noteNote: In cases where all the schema
columns are set as keys, this action yields an error and the Job fails.

Insert or
update: Insert a new record. If the record with the given reference
already exists, an update would be
made.

Information noteNote: In cases where all the schema
columns are set as keys, this action yields a warning message and the Job
continues.

Update or
insert: Update the record with the given reference. If the record does
not exist, a new record would be
inserted.

Information noteNote: In cases where all the schema
columns are set as keys, this action yields a warning message and the Job
continues.

Delete: Remove entries corresponding to
the input flow.

Information noteWarning:

*It
is necessary to specify at least one column as a primary key on
which the Update and Delete operations are based. You
can do that by clicking Edit Schema and selecting the
check box(es) next to the column(s) you want to set as primary
key(s). For an advanced use, click the Advanced
settings view where you can simultaneously
define primary keys for the Update and Delete
operations. To do that: Select the Use field options check box and
then in the Key in
update column, select the check boxes next to
the column names you want to use as a base for the Update
operation. Do the same in the Key in delete column for the
Delete operation.* | | 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. When you create a Spark Job, avoid the reserved word line when naming the fields.
Built-In: You create and store the schema locally for this component only.
Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.

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 information, see Retrieving table schemas.
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
- View schema: choose this option to view the schema only.
- Change to built-in property: choose this option to change the schema to Built-in for local changes.
- Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.
  
  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

| | Die on
error | This check box is
selected by default. Clear the check box to skip the row on error and
complete the process for error-free rows. If needed, you can retrieve
the rows on error via a Row>Rejects link. | ## Advanced settings | Properties | Description | | --- | --- | | Commit
every | Enter the number
of rows to be completed before committing batches of rows together into
the DB. This option ensures transaction quality (but not rollback) and,
above all, better performance at execution. | | Additional
Columns |

This option is not offered if you create (with or without drop) the DB table. This option allows you to call SQL functions to perform actions on columns, which are not insert, nor update or delete actions, or action that require particular preprocessing.
Name: Type in the name of the schema column to be altered or inserted as new column
SQL expression: Type in the SQL statement to be executed in order to alter or insert the relevant column data.
Position: Select Before, Replace or After following the action to be performed on the reference column.
Reference column: Type in a column of reference that the tDBOutput can use to place or replace the new or altered column.

| | Use field
options | Select this check
box to customize a request, especially when there is double action on
data. | | Debug query mode | Select this check box to display each step during processing entries
in a database. | | Use Batch | Select this check box to activate the batch mode for data processing.

Information noteNote:

This check box is available only when you have
selected the Insert, Update, or Delete option in the Action on data
option. | | Batch
Size | Specify the number of records to be processed in each batch.

This field is available only when the Use batch mode
check box is selected. | | tStat
Catcher
Statistics | Select this check
box to collect log data at the component level. | | Enable parallel
execution | Select this check box to perform high-speed data processing, by treating
multiple data flows simultaneously. Note that this feature depends on the database or
the application ability to handle multiple inserts in parallel as well as the number of
CPU affected. In the Number of parallel executions
field, either:

Enter the number of parallel executions desired.
Press Ctrl+Space and select the appropriate context variable from the list. For further information about context variables, see Using contexts and variables.

Note that when parallel execution is enabled, it is not possible to use global
variables to retrieve return values in a subJob.

The Action on table field is not available with the parallelization function. Therefore, you must use a tCreateTable component if you want to create a table.
When parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.

| ## Global Variables | Variables | Description | | --- | --- | | Global
Variables | NB\_LINE:
the number of rows processed. This is an After variable and it returns an integer.

NB\_LINE\_UPDATED: the number of rows updated.
This is an After variable and it returns an integer.

NB\_LINE\_INSERTED: the number of
rows inserted. This is an After variable and it returns an integer.

NB\_LINE\_DELETED: the
number of rows deleted. This is an After variable and it returns an integer.

NB\_LINE\_REJECTED: the number of rows rejected. This is an After
variable and it returns an integer.

QUERY: the query statement processed. This
is an After variable and it returns a string.

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 checkbox is
cleared, if the component has this checkbox.

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](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage
rule** | This component
must be connected to an Input component. It allows you to carry out
actions on a table or on the data of a table in an SQLite database. It
also allows you to create reject flows using a Row > Reject link to
filter erroneous data. For an example of tSQLiteOutput in use, see [Retrieving data in error with a Reject link](https://help.qlik.com/talend/en-US/components/8.0/mysql/tmysqloutput-tmap-tfileoutputdelimited-tfileinputdelimited-retrieving-data-in-error-with-reject-link-standard-component-this). | | 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.

The Dynamic settings table is
available only when the Use an existing
connection check box is selected in the Basic settings view. 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](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). | **Related concepts** * [Filtering SQlite data](https://help.qlik.com/talend/en-US/components/8.0/sqlite/tsqliteinput-tsqliteoutput-tsqliteoutput-filtering-sqlite-data-standard-component-this)