# 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.

For more technologies supported by Talend, see [Talend components](https://help.qlik.com/talend/r/en-US/7.3/components/elt-jdbc).

Note that it is highly recommended to use the ELT components for a specific type of database (if any) instead of the ELT components. For example, for Teradata, it is recommended to use the tELTTeradataInput, tELTTeradataMap and tELTTeradataOutput components instead.

### In this section

* [tELTInput Standard properties](https://help.qlik.com/talend/en-US/components/7.3/elt-jdbc/teltinput-standard-properties)

**Related concepts**

[Aggregating Snowflake data using context variables as table and connection names](https://help.qlik.com/talend/en-US/components/7.3/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. In this example, set all input and output table names and connection names to context variables.")