I am evaluating Replicate for a specific use case. What is desired is to have a production and a reporting instance of the database. The initial version of the reporting instance would be a snapshot of production with all transactions. The production instance would then be purged to remove older transactions.
I am looking for a solution that would then allow new transactions that occur in the production environment to be replicated into the reporting (full copy) so that the end state is that the reporting instance contains inception to date transactions, the production instance would have more recent transactions, and all new transactions in production would be replicated to the production database.
The database is Oracle with a large number of tables (several thousand) and some transactional tables have millions of rows. New transaction volume is not particularly heavy, thousands of transactions daily.
Is this a use case that reasonably met with Qlik Replicate?
Welcome to Qlik Community and posting your first question.
Yes, Qlik Replicate can fulfil your needs by creating a replication task from your production instance (as source endpoint) to your reporting instance (as target endpoint). You will turn on Full Load and Apply Changes in the task. After you run the task, Qlik Replicate will first do a full load, which will replicate all your selected tables from your production Oracle to reporting Oracle, after the initial load finishes, Replicate will then run a CDC which captures the data changes stored in the redo logs of your production Oracle to reporting Oracle. In this way, your reporting instance will contain inception to date transactions replicated from your production instance.
Besides @Kent_Feng , from my understanding, the Full Load and CDC task will be triggered to startup on a specific time (eg 1:00AM every day), or an event. The replication tasks can be defined as scheduled jobs which automatically run repeatedly.
Hope this helps.
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
I watched some of the demos. In one, it showed a simple setup. One step was selecting the tables in scope. Is it possible to define this at the database level so that all tables are included without having to select them individually? Also, can structural changes be propagated automatically? For example if a new table or field is added to production, can that be automatically recognized and flow to the reporting instance in addition to data changes?
The goal here is that the reporting instance be kept identical to the production instance, except have inception to date data. We want to ensure that users have the exact same experience using either database instance except for the volume of data available.
Automatic inclusion of tables not possible in Qlik Replicate whenever the tables added at the DB level.
You need to manually add the tables into the task.
Regarding the fields/Columns, its supported, whenever we add new column into a table at the DB, based on the DDL setting at the task level, Qlik Replicate will capture those.
For more information, you need check limitations of Source and Target i.e. which kind of DDL is supported.
To add more to previous experts' comments. All replication tools are designed to replicate the User data not the System Data. And they gather all the user data or tables information from the dictionary of the tables stored inside the System tables or metadata,
if you are looking to replicate whole data then database cloning or DR or Storage replication is best to use.
