Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
In sorter path can see some file of 1 kb. Most of times it is removed in 4 mins approx but some time it takes hours.
So want to understand what this file holds ?
And in case relying on it to confirm if data till certain time has been processed then can it be ignored ?
Hello,
Please through below article:
Replicate Sorter Files - Qlik Community - 1872860
Regards,
Suresh
Hello @RahulT , copy @Steve_Nguyen ,
This is normal behavior for SQL Server source as there are 2 open transactions which is used to prevent truncation of unread changes from TLOG. This behavior only occurs for SQL Server source endpoint.
Hope this helps.
Regards,
John.
Hello,
Please through below article:
Replicate Sorter Files - Qlik Community - 1872860
Regards,
Suresh
So as per article
Sorter files will accumulate if there if either:
But I am specifically talking about 1kb files which does not grow and size remain 1 kb which I suppose doesn't hold any data. Data files grows to certain size and is removed after data being applied.
Problem I have is some of these 1 kb file stay in sorter for n no. of hours even though data files which came later are already processed. So not sure if what ever is there in those 1 kb files been processed. If these files modified date is 7 am then not sure if all data till 7 has been processed ?
@RahulT what version of Replicate are you using?
what is the source and target endpoint of the task ?
sorter folder may have 1kb that exist in the sorter folder , which is normal.
Hi Steve,
Qlik replicate version is 2022.11.0.208
Source end point : SQL SERVER
Target end point : Snowflake
Had given e.g. of particular time like tswp 1kb file of 10 am exists till 10 pm then can we say that 10 am all data and process is completed by Qlik Replicate ?
the tswp could be there while task are running and stopping , so look to be normal.
Hello @RahulT , copy @Steve_Nguyen ,
This is normal behavior for SQL Server source as there are 2 open transactions which is used to prevent truncation of unread changes from TLOG. This behavior only occurs for SQL Server source endpoint.
Hope this helps.
Regards,
John.