Qlik Replicate : Impact on SQL Server CDC and change tracking

SaiKrishnaP — Fri, 15 Nov 2024 22:53:24 GMT

In our current state, since we cannot give Qlik access to back up files, we want to use Qlik Replicate to issue "repl_done".

With this approach, we will not be able to use SQL Server CDC. But we were thinking we can still use change tracking until we saw the limitations here.

So the questions:

1) Why would change tracking not work with Qlik Replicate? Limitation states : "Table change tracking is not supported". Trying to understand the real reason behind it to understand the risks of using CT along with Qlik Replicate. Also if we have any alternatives?

2) Considering Qlik does not have access to back up files, do we have any other options to have Qlik Replicate and SQL Server CDC work together?

Thanks!

Re: Qlik Replicate : Impact on SQL Server CDC and change tracking

SwathiPulagam — Wed, 09 Mar 2022 21:00:19 GMT

Hi @SaiKrishnaP,

When you have a database where MS-CDC is configured, you can use one of the below options.

1. You can use Transactions Replication without SP_REPLDONE- The disadvantage of this option is we can read only online logs. If the task is in stop mode for a long duration, we have a chance of missing data.

2. Another option is using the MS-CDC source endpoint and reading the data which is available in the 2021.11 Replicate version.

Thanks,

Swathi

topic Qlik Replicate : Impact on SQL Server CDC and change tracking in Qlik Replicate

Qlik Replicate : Impact on SQL Server CDC and change tracking

Re: Qlik Replicate : Impact on SQL Server CDC and change tracking