Qlik Community


Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Q&A with Qlik! New Case Portal, Chat Bot and Qlik Community. Oct. 19th REGISTER TODAY

Transferred Volume(MB) size in Qlik Replicate


Transferred Volume(MB) size in Qlik Replicate

This article explains that why data size is displaying difference between  Transferred Volume(MB) and Target/Source table Table.

Customers wonder why data sizes show differently


  • All Replicate version


1. Transferred Volume(MB) size in Qlik Replicate

     Transferred Volume.png    


2. Target/Source Database



 1.  The data size Replicate read (and process) may be very different from the actual size of the data in the DB.
       For example, a string column may be stored in the DB in specific encoding, using XX bytes storage.
       However, Replicate in most cases request the data in multi-byte in order to avoid NLS issues, which might lead it to read twice as much data.

 2. 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



Version history
Revision #:
1 of 1
Last update:
‎2021-07-20 09:51 PM
Updated by: