In one of the recently released update rollups a new registry is now available for reducing the size of the asyncoperationbase and workflowlog tables.
Setting AsyncRemoveCompletedWorkflows to a value of dword 1 will cause all successfully completed workflows to be immediate deleted after they are run. This can be beneficial, but only to a very large crm implementation or an implementation where workflows are very heavily used.
Another open that has been around for a while in reducing the size of this table is to set AsyncRemoveCompletedJobs a value of dword 1. This will cause only jobs that are not crm workflows to be removed from this table.
We recommend setting AsyncRemoveCompletedJobs but not AsyncRemoveCompletedWorkflows. If you are looking for help please consider PowerObjects in working with you for hosted XRM development – we are one of the leading providers of hosted Microsoft CRM and XRM hosting.
For more info:
AsyncRemoveCompletedJobs
http://support.microsoft.com/kb/957871
AsyncRemoveCompletedWorkflows
http://support.microsoft.com/kb/968755
Welcome to the #1 Dynamics CRM Partner in the World
Proud winner of the 2015 Microsoft Partner of the Year for Cloud Customer Relationship Management, PowerObjects is the preferred partner for implementing, supporting, and growing CRM solutions. Through unparalleled offerings of service, support, education, and add-ons, PowerObjects can help tailor custom solutions for your business.
How Can We Help You Today?
And as always, happy CRM'ing!
Hi,
I applied this technics after clearing the DB tables.
But now every time I run a deletion operation on email activities the async job takes too much time and all the CRM freeze. Any ideas why?
Thanks.
P.S. great blog