CHECKPOINT ISOLATED LOADING SQL Statement | Teradata Vantage - CHECKPOINT ISOLATED LOADING - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Syntax and Examples

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
wgr1555383704548.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1144
lifecycle
previous
Product Category
Teradata Vantage™

Sets a checkpoint for the explicit isolated load operation and commits the data that has been loaded up to that point.

Required Privileges

You must have the INSERT, UPDATE, or DELETE privilege on the base table associated with the load operation.

Usage Notes

The CHECKPOINT ISOLATED LOADING statement must be issued by the same session as the BEGIN ISOLATED LOADING statement.

When you issue the CHECKPOINT ISOLATED LOADING statement, the data that has been loaded up to that point by the session, or by all sessions in a multi-session load operation, is committed and becomes available for concurrent read operations. You can use the CHECKPOINT ISOLATED LOADING statement to enable recently loaded data to be available for concurrent read operations while the load operation continues.

The CHECKPOINT ISOLATED LOADING statement must be the last statement in an explicit transaction.