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

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
rjford11
Contributor
Contributor

Task Priority

We have 3 separate tasks (Dev/QA/Prod) which are using the same source database.

1) The source system has performed 50gb of deletes and the targets have fallen behind. Will replicate work on each task in parallel?

2) Is there a way to assign a priority to the tasks so that Production has a higher priority?

 

Thanks,

Rich

Labels (2)
2 Replies
john_wang
Support
Support

Hello @rjford11 ,

Thanks for reaching out to Qlik Community!

1) If all tasks are run concurrently, the replication job will indeed be executed in parallel. However, this approach has some disadvantages:

    i) The same redo log will be read three times, resulting in a total of 150 GB being read (50 GB * 3).

    ii) The three tasks will interfere with each other, potentially causing performance degradation.

2) in Oracle Database, you can manage the priority of sessions and users through Resource Manager. Resource Manager allows you to allocate CPU, parallel execution resources, and other system resources differently based on user accounts, sessions, or other criteria. This can be useful in scenarios like yours, where you want to give one account (e.g., "A") higher priority over another account (e.g., "B") when they execute similar queries. And you can use different accounts in your Qlik Replicate tasks.

I 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!
SushilKumar
Support
Support

Hello @rjford11 

in Such Situations you must use Logstream Steup were only one ( logstream task read from Source database) and configure 3 replicate tasks to read the changes from staging folder. 

where you can tweak replicate task settings to by allocating mor resources to configured target.

Regards,

Sushil Kumar