Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Commit rate during full load: does it actually do a commit to the database when parameter reached ? If I set the parameter to 50000, will qlik to a commit (in my case to a DB2 database) so the database transaction logg will be freed as a result of the commit ?
When I read the documentation, I believe the answer is yes... but when i monitor the transaction log inside DB2 it seems like qlik is not performing commit accorling to parameter set (in my excample here 50000 records)
Can anyone comment on this ?
Hello @ArntJohan ,
Thanks for reaching out to Qlik Community!
The Commit rate during full load parameter in the Full Load Tuning page:
it's the unload reading batch that the maximum number of data rows can be transferred together, Qlik Replicate retrieves the number of rows (default is 10000) in every chunk from source database.
Hope this helps.
John.
Hi John !
Thanks for your quick feedback ! I saw in documentation "Commit rate during full load" is the max number of rows to be transferred in a chunk from source database... same as you mention here.
But I still wonder how qlik replicate actually handle commit when loading data. Lets say I have a 50000 row table that I want to load to a target database. I use the default value 10000 for "Commit rate during full load".
Will qlik do a physical commit after loaded/inserted the first chunk with10000 data rows ? Meaning database engine will write to db log and free the database transaction log for every 10000 rows inserted to target database ? Or... will qlik send 5 chunks with each 10000 rows before it will perform the physical commit ? So all 50000 rows inserted will be handled in 1 single commit ?
Thanks
Arnt
Hello @ArntJohan ,
The behavior maybe various depends on the different source and target endpoint combination. You may set SOURCE_UNLOAD/TARGET_LOAD to Verbose, rerun the task then check the task log file to understand Qlik Replicate how to retrieve the data from source database and write to target side.
Hope this helps.
John.