We highly recommend that you diagnose the issue before you truncate the table. If you fail to diagnose the issue then it is likely that this problem will return.
Often times when this table is back logged from too much data it is cased by a task or policy executing more often than it should. Use the following query to identify what tasks are in the clienttaskinstancerequests table. Find the tasks executed most often and see if they can be optimized.
select i.name, count(*) as count from clienttaskinstancerequests ctir join taskinstances ti on ctir.taskinstanceguid = ti.taskinstanceguid join itemversions iv on ti.taskversionguid = iv.versionguid join item i on iv.itemguid = i.guid group by i.name order by count DESC
Another possible issue is that there are expired task instances in the clienttaskinstance requests table. Check to see if any tasks come up in the following query, if there are then they either need to be deleted or the clienttaskinstance table truncated:
Select * from clienttaskinstancerequests ctir left join taskinstances ti on ctir.taskinstanceguid = ti.taskinstanceguid where ti.taskinstanceguid is NULL
Imported Document ID: TECH209786
Subscribing will provide email updates when this Article is updated. Login is required.