Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are running SQL Server (MS-CDC) and our company does a database restore from Production to our TEST environment every week or so. We are pulling the TEST databases as a source to our lower data warehouse environments using LogStream.
When the restores happen, Replicate breaks the change processing and cannot pick up the CDC tables. Is there anyway around RELOADING all the tasks on the server? This takes an incredibly long time and is an inconvenience for our developers.
Hello @zacker20 ,
Thanks for contacting Qlik Support.
I did not understand the question well... Do you mean you have many tasks on a Replicate Server, after the TEST database (acts as source database for these tasks) restores, you want to RELOAD (perform both Full Load + CDC) startup on all these tasks, is that right?
If yes, then we may do that by script file. Let us know the details.
Regards,
John.
Hello @zacker20 ,
Thanks for the clarification.
From my understanding, you need startup tasks by CDC only run options without Full Load - because we assume the history rows were replicated from source to target already, we just want to catch up the CDC part after each time restore. The best option is resume task by timestamp
Hope this helps.
Regards,
John.
Hi @zacker20 ,
Yes, we are talking about the source db restores. Let me know if you have any concerns.
Regards,
John.
When we tried to do this load from date/time - we got a ton of apply exception errors as time went on. UPDATE statements would have 0 rows affected