Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
WEBINAR June 25, 2025: Build on Apache Iceberg with Qlik Open Lakehouse - REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
Al_gar
Creator
Creator

Distributed Source Table to multiple target databases

For a Replicate task using HANA source with trigger-based CDC, what is the best way to distribute the same source table across different target databases?  Should we just create multiple tasks reading to the same HANA table source?

 

Qlik Replicate November 2024
Source:  HANA S/4
Targets: SQL Server 2019

 

Labels (1)
2 Solutions

Accepted Solutions
john_wang
Support
Support

Hello @Al_gar ,

I'm not entirely sure how the distribution logic is defined, whether it's based on schema, primary key values, or some other criteria.

However, one practical approach is to use Log Stream to capture the changes in a single task, and write them to a staging area files. Then, you can create multiple downstream tasks that read from this staging task and distribute the data to the appropriate target databases.

This method offers better scalability and central control over data distribution logic, especially when multiple targets are involved.

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!

View solution in original post

Al_gar
Creator
Creator
Author

Hi @john_wang ,

Thanks. Following Replicate documentation I got confused for a moment on step 3 "Duplicate the source endpoint and add it to the log stream staging task" because after duplicating the source endpoint connection the "Read changes from log stream staging folder" check box wouldn't show up:

Al_gar_0-1749144577562.png

 

However, when I tried to create a new endpoint connection the check box will show up:

 

Al_gar_1-1749144661210.png

After adding the source endpoint's details I was able to get the task created and running. Thanks.

View solution in original post

7 Replies
john_wang
Support
Support

Hello @Al_gar ,

I'm not entirely sure how the distribution logic is defined, whether it's based on schema, primary key values, or some other criteria.

However, one practical approach is to use Log Stream to capture the changes in a single task, and write them to a staging area files. Then, you can create multiple downstream tasks that read from this staging task and distribute the data to the appropriate target databases.

This method offers better scalability and central control over data distribution logic, especially when multiple targets are involved.

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!
Al_gar
Creator
Creator
Author

Hi @john_wang ,

Thanks. Following Replicate documentation I got confused for a moment on step 3 "Duplicate the source endpoint and add it to the log stream staging task" because after duplicating the source endpoint connection the "Read changes from log stream staging folder" check box wouldn't show up:

Al_gar_0-1749144577562.png

 

However, when I tried to create a new endpoint connection the check box will show up:

 

Al_gar_1-1749144661210.png

After adding the source endpoint's details I was able to get the task created and running. Thanks.

Al_gar
Creator
Creator
Author

@john_wang, I forgot to ask if there's any limitation on the amount of tables that you can load on a single Log Stream task.

john_wang
Support
Support

Hello @Al_gar ,

Personally I do not see such a limitation, in our customers there are than more several thousands tables were included in a single task.

Regards,

John.

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

Hi @Al_gar 

All I would add to what @john_wang has shared is that you will need more disk space for the audit files the more tables you have in the staging task.

Thanks,

Dana

Al_gar
Creator
Creator
Author

Thanks @john_wang and @Dana_Baldwin.

john_wang
Support
Support

Thank you for your support! @Al_gar 

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