The following limitations affect use of Teradata connectors with Teradata QueryGrid:
- Dataset CSV storage is not supported.
-
Transaction semantics between systems is not supported.
After data has been exported and committed to a remote system, any subsequent errors or aborts on the local system do not roll back the remote request.
- Use of the Returns clause is not supported for Teradata-to-Teradata links.
- Teradata QueryGrid does not collect query metrics (such as CPU usage) for remote Teradata queries. The remote server sends the SessionID/QueryID through a data execution channel but is not available for Metadata/Help/Explain queries.
- User mapping with remote user authentication works only for the INVOKER security model.
- When using EXPORT clause queries, LOB UDT data type cannot be exported if no LOB/LOB UDTs are imported in FOREIGN TABLE query.