Online Transactions and Batch Jobs Don’t Get Along

Running both online transactions and batch jobs like reporting or analytics can compromise the performance of one or the other. For example, reporting indexes could adversely affect the performance of your Oracle database to your OLTP users. Having separate instances to keep the two apart is as good as your mom separating your brothers! SharePlex can maintain the two databases in near real time synchronization so that any changes that occur on the OLTP database are immediately replicated to the reporting database providing up to date data for real time reports. Not only is your processing load balanced, but each instance can be tuned specifically for the purpose, OLTP or batch processing.

And if there are high availability needs, a data distribution model could be the answer. You might need several different reporting instances from the one application database, maybe a certain subset of data for group like accounting and a different subset for another group like HR. SharePlex can be as granular as row and column data to replicate to a target reporting server. So if HR only need the name, address and phone number from a table while the Accounting department only needs name, address and salary, SharePlex can do that “vertical partitioning” and only replicate that specific data. And then for High Availability, all the tables would be replicated to a third target. This third target would become the source should the original Oracle instance go down. On failover, the new source would then replicate back to the original as well as the two reporting instances.

 

More information about SharePlex configurations can be found on our Database Replication page.

Download a SharePlex data replication Free Trial

About the Author