Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
gideeeh
Contributor II
Contributor II

Can Qlik Replicate load multiple source tables (same schema) into one target table/folder?

Hi,

In my source system, there are several tables that share the exact same schema, for example something like:

  • table_A1
  • table_A2
  • table_A3

When I select them in a Replicate task, each table is written to its own target folder/table in S3.

Question:

  • Is there any supported method in Replicate to combine these tables so that all rows land in one target table or one S3 folder (i.e., a merged output)?
  • If this is not supported, could someone point me to the specific documentation or limitation that states Replicate does not allow merging multiple physical source tables into a single target object?

Thanks!

Labels (1)
3 Replies
SachinB
Support
Support

Hello @gideeeh 

Qlik Replicate does not support merging multiple physical source tables into a single target table or a single target folder. Each source table defined in the task is treated as an individual replication entity, and Replicate requires a one-to-one mapping between a source table and a target table


Because of this architectural design, Replicate cannot combine or union data from multiple source tables during replication.

You can find the limitation in the guide list.

Replicate-Setup-and-User-Guide 

Regards,
Sachin B


john_wang
Support
Support

Hello @gideeeh ,

If you mean loading the tables during Full Load, then yes, there are ways to handle that. The simplest approach is to create a VIEW on the source side that combines those tables, and then load the view’s data into S3.

Hope this helps.

John.

Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Jon_Donker
Creator II
Creator II

If the target database is a RDMS; it might be possible to land the data into their individual tables on the destination and the build triggers off these tables to copy the action into a single "merged" table