Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
JacobTews
Creator
Creator

SQL Server LOG_BACKUP full

We run Compose on-prem, writing to a SQL Server instance also on-prem. Our DBA has 4-hour backups for all the company's SQL Servers which is supposed to truncate the transaction logs for all the databases after doing so. However, the logs for both my test and production data warehouse databases seem to be immune to such truncation:

JacobTews_1-1715115490967.png

Notice in particular the fact that the log for the test data warehouse is actually bigger than the test data warehouse itself!

Any systems-knowledgeable folks out there have any insights?

Is there a setting in Compose that I have inadvertently toggled to cause such behavior?

Qlik Compose for Data Warehouses Qlik Compose 

2 Replies
JacobTews
Creator
Creator
Author

To clarify, I actually got the error messages from Qlik Replicate, not Compose, but since everything is on the same server, it seems like the DW logfiles are the issue?

JacobTews_0-1715117725977.png

sureshkumar
Support
Support

Hello @JacobTews 
I would suggest creating a post in Replicate Form on the issue

Qlik Replicate Discussions | Qlik Community

 

Regards,
Suresh