SQL Server transaction logs held open

[garethmoger]

Currently we are replicating data between SAP SQL Server (using SAP APP DB endpoint) and Snowflake however the transaction logs are being held open longer and longer in SQL Server, which left unchecked will cause performance issues for other services.

Has anyone come across this issue before, have any insight to why it's happening or how to fix?

When I look at incoming changes I can see 50k records held on disk when applying to target.  I don't know if this is the cause of the issue with transaction logs or as a result of it.

The latency is currently at 10+ hours.

Obviously we have raised these concerns with support for more help but hoping the community have additional insights.

[lyka · Accepted solution]

Hello,

For SQL Server source, are you using "Prevent truncation of unread changes from TLOG: ", if you are using this method, you need to make sure that the log reader agent job is running:

https://help.qlik.com/en-US/replicate/November2021/Content/Replicate/Main/SQL%20Server/SQLServerDBSo...

Thanks

Lyka