ER works by reading the logical logs, testing if a log record needs to be replicated, and finally sending that information to the appropriate participants.
ER首先读取逻辑日志，检验日志记录是否需要复制，最后将这些信息发送给相应的参与节点。
While this section is far from complete, it should be a good starting reference to be supplemented by additional reading in the freely available source change logs.
虽然本节的内容还远远不够完全，但它应该是一个不错的起点参考资料，通过另外阅读一些可免费获得的源代码修改日志，可以补充这方面的知识。
HDR secondary goes to standard mode after reading all logs from staged.
在从暂存日志读取所有数据之后，HD r次要服务器将回到标准模式下。
The Q Capture program runs on the source system, reading DB2 recovery logs for changed source data, and writing it to WebSphere MQ queues.
QCapture程序在源系统上运行，读取已修改的源数据的DB2恢复日志，并将之写入WebSphereMQ 队列。
Execution of onmode -d standard on HDR secondary completes until HDR secondary completes reading (drain) from logs staged (waits till HDR secondary comes to normal mode).
直到HD r次要服务器完成从暂存日志读取数据的操作(在排出模式下)之后，才能在HD r次要服务器上执行onmode - d标准(等待HD r次要服务器变为常规模式)。
I've counted dozens of people who've begun attempting polyphasic sleep after reading (and crediting) my logs.
我知道的就有数十人，在读过我的博客后开始尝试多相睡眠了。
Other less frequent activities included reading instant messaging logs, using monitoring software and pretending to be another person.
其它的一些偏少的窥探行为包括：看及时通讯记录，用监测软件或者假装成另一个人，等等。
While InfoSphere DataStage has stages for accessing data from different databases, it does not have the capability to capture only changed data from reading the database logs.
尽管InfoSphereDataStage有不同的阶段用于访问不同数据库的数据，它却不能仅通过读取数据库日志获取增量数据。
Figure 1 shows capture using CD tables to store captured changes from the logs, Apply reading those tables, and then writing the changes to the target tables.
图1显示Capture使用cd表存储来自日志的抽取增量，Apply读取表，然后将增量写入目标表中。
I am reading so bad people will write in English logs, I see that this part of a clever!
我读书那么差的人，都会用英文写日志，这就看出我聪明的一部分了！
I'd recommend using separate user names on the DB side for each solution in order to differentiate when reading server DB logs.
我建议你使用单独的用户名在数据库端为每个解决方案来区分当读取服务器数据库的日志。
I'd recommend using separate user names on the DB side for each solution in order to differentiate when reading server DB logs.
我建议你使用单独的用户名在数据库端为每个解决方案来区分当读取服务器数据库的日志。
应用推荐