Restrictions and Limitations
This section describes the restrictions and limitations when using the SQL Selector
operator.
Select Statements
Only the Teradata SQL SELECT statements are supported in the SQL Selector operator's
SelectStmt attribute.
The SELECT statements in the SQL Selector operator's SelectStmt attribute cannot have
any of the following characteristics:
Contain a USING modifier
Contain a WITH or WITH BY clause
All SELECT statements in the SQL Selector operator's SelectStmt attribute are treated
as a single multi-statement request to be sent to the Teradata Database.
The entire length for the SELECT statement(s) cannot be greater than 1MB.
Data Types
The SQL Selector operator cannot export ST_Geometry geospatial data.
However, if the ST_Geometry data type is cast as VARCHAR/VARBYTE, then the data can
be exported.
The SQL Selector operator is the only operator that can export LOB/JSON/XML data types
from Teradata.
Other Notes
The SQL Selector operator can export rows from multiple tables and views as long as
the result set adheres to a single schema.
The SQL Selector operator is the only operator that can extract rows from Teradata
in field mode. All data retrieved in the field mode is converted to character strings.
In order to take advantage of this feature, ReportMode must be enabled. When ReportMode
is enabled, the columns defined in the script schema must be VARCHAR.
The SQL Selector operator can export rows from Teradata tables and views. The maximum
size for each row is 1MB.
The SQL Selector operator allows one session; it does not support multiple sessions.
The SQL Selector operator allows one instance; it does not support multiple instances.
The SQL Selector operator is not restartable if the data export has started and the
data export has not completed.
The SQL Selector operator does not require a Teradata Database load slot.