Transferred Volume(MB) size in Qlik Replicate

Daniel_Seo — Tue, 14 Feb 2023 15:47:37 GMT

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:

The target or source database may show a different volume:

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.

Re: Transferred Volume(MB) size in Qlik Replicate

FrancoHR — Thu, 09 Nov 2023 16:54:39 GMT

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,

article Transferred Volume(MB) size in Qlik Replicate in Official Support Articles

Transferred Volume(MB) size in Qlik Replicate

Resolution

Related Content:

Re: Transferred Volume(MB) size in Qlik Replicate