Completed workflows are now disappearing in Microsoft Dynamics CRM – managing the size of the AsyncOperationBase Table

Posted on July 15, 2010 by JoeCRM

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

My Twitter profileMy Google+ profile

JoeCRM

Microsoft Dynamics CRM Expert at PowerObjects
Joe CRM is a CRM superhero who runs on pure Microsoft Dynamics CRM adrenaline. As the face of PowerObjects, Joe CRM’s mission is to reveal innovative ways to use Dynamics CRM and bring the application to more business and organizations around the world.
This entry was posted in CRM 2011. Bookmark the permalink.
  • Marco Silva

    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