Restrictions and Limitations
This section describes the restrictions and limitations when using the SQL Inserter
operator.
Data Types
The job cannot load ST_Geometry geospatial data.
The SQL Inserter operator is the only operator that can load LOB/JSON/XML data types.
UDT data can be loaded in its external type format.
Error Tables
The SQL Inserter operator does not have error tables like the Load, Update, and Stream
operators.
Other Notes
One SQL Inserter operator job can load a single Teradata table or view.
The target table must already exist.
Data can be loaded into an empty or populated Teradata table.
Only the Teradata SQL INSERT statement is supported. Any other Teradata SQL statements
are not supported.
One Teradata SQL INSERT statement is allowed for a single SQL Inserter operator job.
Multiple statements are not allowed.
One DML group is allowed for a single SQL Inserter operator job. Multiple DML groups
are not allowed.
The SQL Inserter operator treats the entire loading job as a single explicit transaction.
If any error is encountered during the insert operation, the SQL Inserter operator
backs out all rows of data inserted up to that point and the job terminates.
The target table cannot be rolled back after the job is complete with no errors.
Row hash level locking is used during the job. The job does not lock the target table.
The SQL Inserter operator can support multiple instances, and each instance can log
on one or more sessions based on the valued specified in the attribute MaxSessions.
The SQL Inserter operator does not require a Teradata Database load slot.