Temporary table cleanup | QueryGrid - Temporary Table Cleanup - Teradata QueryGrid

QueryGrid™ Installation and User Guide - 3.08

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Lake
Product
Teradata QueryGrid
Release Number
3.08
Published
July 2025
ft:locale
en-US
ft:lastEdition
2025-07-30
dita:mapPath
tca1747267140087.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
Product Category
Analytical Ecosystem

When running queries, QueryGrid connectors create temporary tables (or views) on the target database. You can control where these temporary objects are created by configuring one of the following NVP properties Temporary Database Name, Temporary Schema Name, Temporary Schema, or Database Name.

These tables and views are automatically cleaned up by QueryGrid once the query completes.
Disabling the automatic cleanup is not supported.

If a QueryGrid query is stopped, the connector attempts to cleanup these temporary objects as part of the rollback process. However, if the cleanup fails (or does not happen) – for example, due to a QueryGrid software restart – a manual cleanup may be required.

The temporary tables may contain metadata or customer data based on the query. If Temporary Database Name or Temporary Schema Name is not configured, QueryGrid uses the database provided in the NVP Database Name, Schema Name, or the default database/schema of the logged-in user.

When a manual cleanup is needed, locate the relevant tables either in the database/schema defined in the Temporary Database Name, Temporary Schema Name, or default Database/Schema.

The BigQuery connector's temporary tables are created as Temp Table with a 24 hour expiration for import queries, offering a safety net for eventual cleanup.
QueryGrid uses the following naming patterns for temporary objects:
  • BigQuery connector: Tables start with temp_
  • Hive connector: Temporary views are named import_query-uuid_view
  • All connectors:
    • For export clause (FT) queries: User-defined table names are appended with the query UUID, for example, xyz_query-uuid
    • For RTO remote join queries: Names follow the format Temp_sess_session-id, for example, Temp_sess_1018_req_12_0_2_0
Before dropping the temporary tables, verify that no active QueryGrid queries are running.