The AsyncOperationBase and WorkflowLogBase tables grow very large and performance issues occur when you use many workflows in Microsoft Dynamics CRM 4.0

You use many workflows in Microsoft Dynamics CRM 4.0. The AsyncOperationBase and WorkflowLogBase tables grow very large, and performance issues occur.

This issue occurs because, when the workflow rules are fired, a workflow instance and a workflow record are created in the AsyncOperationBase and WorkflowLogBase tables of the MSCRM database. However, when the workflow instance is completed, the workflow record remains in the database. Therefore, the AsyncOperationBase and WorkflowLogBase tables continue to grow. Eventually, performance decreases.

Note The AsyncOperationType property for these records is set to 10.

This problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To enable this hotfix, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate the following subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
3. Determine whether a DWORD registry entry that is named AsyncRemoveCompletedWorkflows exists. The value data of the AsyncRemoveCompletedWorkflows registry entry must be 1.
4. If the AsyncRemoveCompletedWorkflows registry entry does not exist, add the entry. To do this, follow these steps:
   1. Right-click MSCRM, point to New, click DWORD Value, and then type AsyncRemoveCompletedWorkflows in the Name box.
   2. Double-click AsyncRemoveCompletedWorkflows, and then type 1 in the Value data box.
   3. Click Start, click Run, type iisreset, and then click OK.
      
      Note If the value in the Value data box for the AsyncRemoveCompletedWorkflows DWORD value reverts to 0, Microsoft Dynamics CRM will continue to retain the Workflow records in the database even if the tasks are completed.

Note This hotfix is proactive only. Therefore, when the hotfix is installed and activated, only new workflow records are deleted automatically. If the AsyncOperationBase and WorkflowLogBase tables are already large because of these workflow records, you must perform a cleanup of these tables by using the Microsoft SQL Server cleanup script that is included in the following Microsoft Knowledge Base article:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base: