isolated_loading - Teradata Vantage - Analytics Database

Defines the table for load isolation (LDI). Load isolation enables concurrent read operations on committed rows while the table is being loaded.

NO

Defines the table as a non-load isolated table. This is equivalent to creating the table without this clause.

CONCURRENT ISOLATED LOADING

Enables concurrent read operations on committed rows while the table is being modified.

FOR ALL

All modifications can be concurrent load isolated.

FOR INSERT

Only INSERT operations can be concurrent load isolated.

FOR NONE

Concurrent load operations are disabled.

Example: Define an LDI Table

All operations can be concurrent load isolated on this table.

CREATE TABLE ldi_table1, WITH CONCURRENT ISOLATED LOADING  (
		c1 INTEGER,
		c2 INTEGER,
		c3 INTEGER)
PRIMARY INDEX (c1)
INDEX (c2)
;

Example: Define an LDI Table Where Only INSERT Operations are Concurrent Load Isolated

Only INSERT operations can be concurrent load isolated on this table.

CREATE TABLE ldi_table3, WITH ISOLATED LOADING FOR INSERT (
		c1 INTEGER,
		c2 INTEGER,
		c3 INTEGER)
PRIMARY INDEX (c1)
INDEX (c2)
;

Example: Define an LDI Table Where All Operations are Nonconcurrent LDI

All operations are nonconcurrent LDI because of the FOR NONE specification.

CREATE TABLE ldi_table3, WITH ISOLATED LOADING FOR NONE (
		c1 INTEGER,
		c2 INTEGER,
		c3 INTEGER)
PRIMARY INDEX (c1)
INDEX (c2)
;

Example: Define a Non-LDI table

All operations on this table are non-load-isolated. This is equivalent to creating a table without this clause.

CREATE TABLE ldi_table3, WITH NO ISOLATED LOADING (
		c1 INTEGER,
		c2 INTEGER,
		c3 INTEGER)
PRIMARY INDEX (c1)
INDEX (c2)
;