Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
There is an standard script from Microsoft against the performance drop if the AsyncOperationBase table become too large : https://support.microsoft.com/en-us/kb/968520
Officially it applies to CRM 4.0 and CRM 2011.
My question is if i can use this script on CRM 2016 and if it is supported on CRM 2016.
Thanks for your time.
The principle of this script will still work for 2016 and the async operation table hasn't change masively since CRM2011 but it isn't supported by Microsoft. You should use a Bulk Delete job to clean up instead - blogs.msdn.microsoft.com/.../another-experience-with-cleaning-up-the-principalobjectaccess-table-dialogs
Hope this answers your question
Thanks for your reply.
I have more than 5 million records in my on-premise crm asyncoperationbase table. Could this be the reason of slow performance of crm?
Having more than 5000000 records on your AsyncOperationBase table could definitely be a contributing factor in the slow performance of your CRM instance. See Performance is slow if the AsyncOperationBase table becomes too large in Microsoft Dynamics CRM.
Business Applications communities