Table Input
The Table Input step reads information from a connected database using SQL statements. Basic SQL statements can be generated automatically by selecting Get SQL select statement.
General
Step name
Specify the unique name of the Table Input step on the canvas. You can customize the name or leave it as the default.
Connection
Select the database connection to use.
If you do not have an existing connection, select New or Wizard. To modify an existing connection, select Edit.
Options
SQL
SQL statement used to read data from the connected database. You can select Get SQL select statement to browse tables and generate a basic SELECT statement.
Store column info in step meta
Select to use cached metadata stored in the KTR instead of querying the database for table metadata.
Enable lazy conversion
Select to avoid unnecessary data type conversions when possible (can improve performance).
Replace variables in script?
Select to replace variables in the SQL script. This is useful for testing with or without substitutions.
Insert data from step
Specify the input step that provides parameter values. PDI inserts values at ? markers in the SQL statement.
Execute for each row?
Select to execute the query for each incoming row.
Limit size
Number of rows to read. 0 means read all rows.
Preview (button)
Opens a Preview window and shows a temporary execution log.
Example
SELECT * FROM customers WHERE changed_date BETWEEN ? AND ?This SQL statement requests two dates that are read from the Insert data from step input. You can provide the date range using the Get System Info step.
Metadata injection support
You can use ETL metadata injection to pass metadata at runtime.
The following fields of the Table Input step support metadata injection:
SQL
Limit size
Execute for each row
Replace variables in script
Enable lazy conversion
Cached row meta
Connection
Last updated
Was this helpful?