I have a batch job to export to some tables to my Azure SQL server.
However, when the job is run it only exports one entity at a time. Very painful and slow. Why is this? Is there any way to make it run in paralell?
I have a batch job to export to some tables to my Azure SQL server.
However, when the job is run it only exports one entity at a time. Very painful and slow. Why is this? Is there any way to make it run in paralell?
Hi Agneum,
Functional dependencies limit their export order, so we need to confirm the sorting in advance, if not, they will run in parallel without order.
When you select one or more entities, and then select publish , a batch job is started.
Yes, I put them all in one batch job and set "Run sequentially" parameter to "off". The article says "If entities don’t have any functional dependencies, they can be scheduled for parallel import or export.". I got confused on that.
If there is any other way than running seperate batch jobs per entity please let me know, otherwise I will do that instead.
Did you put all entities in one batch job?
I suggest you set up one batch job for one entity. This way the system can process multiple exports in parallel.
André Arnaud de Cal... 291,703 Super User 2024 Season 2
Martin Dráb 230,433 Most Valuable Professional
nmaenpaa 101,156