You can now perform load operations on load isolated (LDI) tables in a single load transaction or multiple transactions within one or more sessions. When data is loaded into load isolated tables over multiple sessions, one master session controls the start and end of a load operation.
You can use the new BEGIN ISOLATED LOADING statement to start an explicit load operation. Tables continue to be in a load state until you perform an END ISOLATED LOADING statement. Multiple sessions can load tables after you start the explicit load. Any session performing a load on the tables is considered a load session. The tables remain in a pending commit state until the load is committed. A session can be a load session for an explicit load operation on one table and an implicit load transaction on another table.
- Load operations on LDI tables can span multiple transactions.
- Multiple sessions can load LDI tables.
- After you perform the BEGIN ISOLATED LOADING statement, you must set the LDILoadGroup reserved query band to the load group you want to use for the load operations.
- A load isolated table can be either in an explicit load state or an implicit load state, but not both. In an implicit load operation, the first concurrent load isolated (CLDI) operation in a transaction starts the load and is committed at the time of transaction commit.
- BEGIN ISOLATED LOADING statement
- CHECKPOINT ISOLATED LOADING statement
- END ISOLATED LOADING statement
- LDILoadGroup reserved query band
- Teradata Vantage™ SQL Data Definition Language Syntax and Examples, B035-1144
- Teradata Vantage™ - Database Administration, B035-1093