Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
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?
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.
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.
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.
Business Applications communities