Controlling The Size Of Your Microsoft CRM Database—Automatically Deleting Completed System Jobs

Source

If you have many workflows or other system jobs, the AsynchronousBase table can grow very large.

PowerObjects posted about some options to keep the CRM Asynchronousbase table from growing out of control recently on their blog http://www.powerobjects.com/blog/2010/07/15/completed-workflows-are-now-disappearing-in-microsoft-dynamics-crm-%E2%80%93-managing-the-size-of-the-asyncoperationbase-table/ .

Setting AsyncRemoveCompletedWorkflows to a value of 1 will automatically cause completed workflow instances to be deleted. AsyncRemoveCompletedJobs will remove successful job records that are not workflows, such as expansion tasks.

This is a big help in keeping your database size in check. Keep in mind that it only kicks in for new jobs after you make the change–if you have existing completed jobs or workflows you will have to clear them out.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

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: