Log Stream Staging Task with SQL Server Source

[iti-attunity-sup]

Hello Experts.

I am currently working with Qlik Replicate 2024.11,
and I have a question regarding the Log Stream Staging (LSS) task when working with SQL Server as the source.

In my scenario, an active transaction is already in progress when the LSS task is started.
The logs indicate the following output:

---
[SORTER] I: Transaction consistency. Start from oldest transaction (sorter_transaction.c:349)
---

From this, it appears that the task begins capturing changes from the oldest transaction that was already in progress.

My question is as follows:
1. Does Qlik Replicate guarantee that the task will always capture from the oldest transaction in such cases?
2. Is there a possibility that long-running, uncommitted transactions will not be captured by the LSS task?

I would appreciate your clarification on how the transaction consistency is handled when starting an LSS task with SQL Server as the source, especially with respect to active and uncommitted transactions.

Thank you for your assistance.

Regards,

Kyoko Tajima

[OritA]

Hi Kyoko Tajima, 

In general, for all source endpoint, when task is started,   if there are open transactions, it will wait the 'Transaction consistency timeout' (default is set to 600sec)and then will start capturing information. (see Replicate users guide : https://help.qlik.com/en-US/replicate/November2024/Content/Global_Common/Content/SharedEMReplicate/C...)

This time can be set as part of the task setting. It would be best practice to set this time as long as the transaction timeout that is set in the source db so that in case of long transaction it will not start caturing uncomminted events. 

Regards,

Orit