Nitin Dhawan CRM Discussion

A CRM Monster [MCDP, MCDS, MCTS, MCSD]

Performance & Optimization

Posted by Nitin Dhawan on June 13, 2009


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

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.

Performance is slow if the AsyncOperationBase table becomes too large in Microsoft Dynamics CRM 4.0

When you run Microsoft Dynamics CRM 4.0, the AsyncOperationBase table grows to be very large. When the table contains millions of records, performance is slow.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: