DB2 queue replication is similar to traditional replication; however, there are no staging tables.
DB 2队列复制类似于传统复制；但是，这种复制没有使用staging表。
Part 2 of this series will detail two specific integration options: with staging tables or with MQ messages.
本系列第 2部分将详细探讨两个具体集成选项：用分级表或MQ消息。
The following sections introduce you to these two types of MQTs, as well as summary tables and staging tables.
下面的几个小节将介绍这两种类型的MQT，另外再介绍总结表和staging表。
Employing staging tables to load and transform data ahead of ingest minimizes interference with query workloads.
在摄取数据之前采用暂存表来加载和转换数据，这可以最大程度地减少对查询工作负载的干扰。
But the population of the staging tables (change tables) and the logging of these transactions require database resources.
但是填充staging表(更改表)和在日志中记录这些事务则需要数据库资源。
A capture process monitors the transaction logs for all changes to the replication source tables, placing any changes made to these tables into staging tables.
一个捕获进程监视事务日志，以发现对复制源表的任何更改，并将对这些表的更改放入到staging表中。
If dependents such as staging tables or refresh immediate MQTs exist on the partitioned table, the second phase starts automatically after these dependents are refreshed via SET INTEGRITY.
如果在已分区表上存在类似临时表或者立即刷新MQTs之类的依赖表，第二阶段会在利用SETINTEGRITY刷新了这些依赖表后自动启动。
Increased Parallelism Through Staging Tables and Other approaches.
通过staging表以及其他方法增加并行性。
Staging tables (not supported by the load utility in multiple partition database environments).
分段表(在多分区数据库环境中装载实用程序不支持这种表)。
Staging tables (not supported by the load utility in multiple partition database environments).
分段表(在多分区数据库环境中装载实用程序不支持这种表)。
应用推荐