DGTT has the fixed schema SESSION.
DGTT有固定的模式SESSION。
The syntax for CGTT is very similar to DGTT.
CGTT的语法与DGTT 极为相似。
Compared to CGTT, DGTT has the following limitations.
与CGTT相比，DGTT具有以下限制。
Listing 12 shows how the DGTT table can be converted to CGTT.
清单12展示了如何将dgtt表转换为CGTT。
This means that for all statements referencing DGTT, they have to be compiled prior to use.
这意味着对于所有引用DGTT的语句来说，它们在使用之前都需要进行编译。
Contrasting to DGTT, during the second session, the definition of cgttbase1 is still valid.
与DGTT相比，在第二个会话的过程中，cgttbase1的定义仍然有效。
Convert a declared global temporary table (DGTT) to a created global temporary table (CGTT).
将已声明的全局临时表(DGTT)转换为已创建的全局临时表(CGTT)。
It can also simplify tuning over DGTT because of supported use of indexes and logging options.
由于支持使用索引和日志选项，它的调优任务也比DGTT更加简单。
Prior to this release, the declared temporary table (DGTT) was the only type of user-defined temporary table.
在此发行版之前，已声明的临时表(DGTT)是唯一的一种用户定义的临时表。
If the connection is lost or the table is dropped, any statement referring to the DGTT needs to be recompiled every time the table is re-declared.
如果连接失败，或者该表已删除，那么每次重新声明这个表时，都需要重新编译引用DGTT的任何语句。
The insert statement between the DECLARE and the DROP needs to be recompiled every time because DB2 cannot know whether the DGTT will have the same property next time around.
DECLARE和DROP之间的insert语句每次都要重新进行编译，因为DB 2无法知道该DGTT下次是否将具有相同的属性。
The insert statement between the DECLARE and the DROP needs to be recompiled every time because DB2 cannot know whether the DGTT will have the same property next time around.
DECLARE和DROP之间的insert语句每次都要重新进行编译，因为DB 2无法知道该DGTT下次是否将具有相同的属性。
应用推荐