# tELTInput Adds as many Input tables as required for the SQL statement to be executed. The three ELT components are closely related, in terms of their operating conditions. These components should be used to handle DB schemas to generate Insert statements, including clauses, which are to be executed in the DB output table defined. ## tELTInput Standard properties These properties are used to configure tELTInput running in the Standard Job framework. The Standard tELTInput component belongs to the ELT family. The component in this framework is available in all Talend products. ## Basic settings | Properties | Description | | --- | --- | | Schema and Edit
schema |

A schema is a row description, it defines the nature and number of fields to be processed. The schema is either built-in or remotely stored in the Repository. The Schema defined is then passed on to the ELT Mapper to be included to the Insert SQL statement.

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.
Built-in: The schema is created and stored locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.
Repository: The schema already exists and is stored in the Repository, hence can be reused. For more information about a component schema in its Basic settings tab, see Basic settings tab.

| | Default Table Name | Type in the default table name. | | Default Schema Name | Type in the default schema name.

If the default schema is specified, the table specified in the
Default Table Name field under the schema will be
used as the input table; otherwise, the table specified in the
Default Table Name field under the database will be
used. | | Mapping | Specify the metadata mapping file
for the database to be used. The metadata mapping file is used for the data
type conversion between database and Java. For more information about the
metadata mapping, see the related documentation for Type mapping.

Information noteNote: You can use Hive mapping to support Databricks Delta
Lake. | ## Advanced settings | Properties | Description | | --- | --- | | tStatCatcher Statistics | Select this check box to gather the Job processing metadata at a Job level as well
as at each component level. | ## Global Variables | Variables | Description | | --- | --- | | Global Variables | 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** | tELTInput is to be used along with the
tELTJDBCMap. Note that the Output
link to be used with these components must correspond strictly to the syntax of
the table name.

Information noteNote:

Note that the ELT components do not handle actual data flow but only schema
information. | **Related concepts** * [Aggregating Snowflake data using ELT components](https://help.qlik.com/talend/en-US/components/8.0/elt-jdbc/teltinput-teltmap-tsnowflakeinput-tlogrow-aggregating-snowflake-data-using-context-variables-as-table-and-connection-names "This scenario shows you an example of aggregating Snowflake data from two source tables STUDENT and TEACHER to one target table FULLINFO using the ELT components.")