cgtt

If you do not, the script will be unable to define the CGTTs used by the delta table functions.

First, CGTT behaves more like a regular table for SQL programmers, but with the potential of a performance advantage.

Because there is no locking requirement (all data is local), CGTT performs better than regular tables.

Class enrollment, where each student has all of the course schedule selections, each student having his own bucket in the CGTT.

Create a table function that wraps the underlying monitoring table function and takes deltas against the baseline data stored in the CGTT.

Use a created global temporary table (CGTT) for per-session storage of the baseline data (use one CGTT per table function).

CGTTs do not support unique constraints or primary keys, but you can create a unique index.

CGTT tables can be defined up front, and users can use them much like regular tables.

CGTTs can also be used in the body of the trigger.

The procedure simply selects from the monitoring table function and inserts the data returned into the CGTT in order to take a baseline.

To adapt the method to support global reset, simply change the table creation statements to create regular tables rather than CGTTs.

You will convert this DGTT to a CGTT in a later listing.

Unlike DGTTs, CGTTs are created in a session and persist after the session is terminated.

Listing 2 defines a CGTT for storing the baseline monitoring data for tables.

Once they commit their selections, they are moved from the CGTT to the real tables.

Because CGTTs are persistent, they can be created and shared for all sessions during system setup.

CGTT essentially moves the table setup process outside the session.

Convert a declared global temporary table (DGTT) to a created global temporary table (CGTT)