Blog

When Tungsten Replicator extracts data, the information that has been extracted is written down into the Tungsten History Log, or THL.

When external issues cause the primary extractor to go offline, we address the issue and bring the extractor back online. However, we need to make sure we start the extraction from the correct position so that the downstream replicas receive transactional data they require. Let’s determine the position and how we set it.

Performance tuning any system provides more speed for the same hardware spend, gives the end-user a better, faster experience and typically reduces the stress on staff all around. Security tuning locks down critical data to prevent unauthorized access. Today we will explore both the security and performance enhancements available for the Tungsten Replicator THL sub-system as of version 7.x.

The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.

In this blog post we will discuss one specific aspect of the THL (Transaction History Log) - the METADATA unsafe_for_block_commit flag.