Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT

Transferred Volume(MB) size in Qlik Replicate

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Daniel_Seo
Support
Support

Transferred Volume(MB) size in Qlik Replicate

Last Update:

Feb 14, 2023 10:47:37 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jul 20, 2021 9:51:14 PM

Data size is reported differently between Transferred Volume(MB) listed in Qlik Replicate and the Target/Source table.

In Qlik Replicate the Transferred Volume(MB) is displayed as such:

     Transferred Volume.png    

 

The target or source database may show a different volume:

     database.png

 

Resolution

The data size Qlik Replicate reads (and processes) may be very different from the actual size of the data in the database. 

For example: a string column may be stored in the DB in specific encoding, using XX bytes storage. However, Qlik Replicate will request the data in multi-byte in order to avoid NLS issues, which may lead it to read twice as much data.

In addition, data Blocks, extents and segments in table may by difference before/after transferring data from source table to target table depending on Database and Journaling file system.

 

Related Content:

Information for tables that have completed loading

Labels (1)
Comments
FrancoHR
Partner - Contributor III
Partner - Contributor III

So the transferred volume field is not a real data of the weight of the data that was replicated at the destination? Is it more than just an estimate?
I say this because a table of  3GB was replicated from  Oracle source to Aurora Postgres, in the destination it weighs 7GB but the Qlik shows that the transferred volume was 14GB.

Regards,

Version history
Last update:
‎2023-02-14 10:47 AM
Updated by: