A short guide on data replication types and use cases. History replication

It is very useful in situations where we need to keep track of changes made to data, such as when you have to deal with financial transactions and need to have a clear view of all the activities involved. Or when you need to have a history of the data for security audits. . Complete, incremental, or batch replication will always yield a table which contains all available data so they aren’t really fit for situations where you need to track changes.

Incremental or batch updates may keep ‘old’ data which is not present in the data source anymore. Generally, changes of data cannot be tracked, and the user is always forced to work with the most current information.

That is why if you need to know when and how the data has been changed, history update is the right replication type to use. There are several ways to implement this type of replication.

In our platform, history replication is based on performing a kind of versioning on the data records by adding two columns to the storage table where the data is replicated to. These columns, called fromtimestamp and totimestamp, provide information on the period when the given record was the current version. Here’s how this works:

Related posts:

I just have a question about https://www.annualcreditreport.com/cra/index.jsp If i get my free credit report today 10/13/12, can i get another FREE credit report on 1/1/13? or do i have to wait till…

When someone says Cloud Computing, Amazon Web Services aka AWS has always been the first thing that comes to my mind. That’s because AWS has been there for over a decade now, and they have been the…

When going to Beijing for the first time, the last thing you want to do is make mistakes. Yet season after season, travelers are caught doing the same silly things. Don’t be that traveler with these…