HIghlights #8
tcapturesupport
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Replication Server is a ‘data movement’ product, which, well, moves data from one place to another. More specifically, it captures database transactions in one database and then applies these to another database.
Because T-Capture® RepSrv captures only data changes, there is no impact on the applications already running on that database. This means that T-Capture® RepSrv can be used in pretty much any database system.
Some common uses of T-Capture® RepSrv are to facilitate migrations of databases or applications that require significant downtime; by setting up a replica with T-Capture® RepSrv, this downtime can be almost fully eliminated.
Because of its application transparency, Replication may also be seen as a mechanism to integrate different applications, by synchronising the data changes.
An increasingly popular use case for replication is for enabling real-time Business Intelligence. Business systems are typically OLTP-oriented with primary business events in the form of database transactions. Analytics typically does not co-exist well with OLTP workload in the same database
Beta Was this translation helpful? Give feedback.
All reactions