Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
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've deleted all "System Jobs" in an environment regardless of their "Status". However, 4 days have passed and the WorkflowLogBase is still taking up 200GB. Any idea why the database is still so large and how I can fix it?
Hope you are doing wonderful.
Am sure you must have followed this script to clean up the WorkflowLogBase and AsyncOperationBase:-
If the same script has been applied and the size is still taking huge, please check the size of AsyncOperationBase table as well?
Also check how many processes/workflows must have been executed in the last 4 days?
The logs created in 4 days are relevant async job created or any duplicates? verify the table records and confirm the same.
Please keep us posted with more details.
Business Applications communities