We are running into performance issues and noticed that we have 6.5 million records in the RollupJobBase table going back to early 2017. We are on CRM 2015 Update 1.1 onprem which looks like was supposed to fix this issue. It does seem to be increasing. Just one day it increased by 85K records. We only have 6 rollup fields in the org and the data in the fields doesn't get updated often. The system jobs to update counts are scheduled with the default of 1 hr. Are these records we can just delete? Should we try to remove the rollup fields first, then delete the data and then add the fields back in? Thanks for any advice we could get on this.
*This post is locked for comments
Glad to hear that ! Please don't forget to close the thread verifying any of above useful answers.
So I did drop all of the rollup fields. That automatically cleared out the RollupJobBase table. I added the fields back, same conditions. The mass update ran as well as some incremental rollups. We currently have 0 records in the RollupJobBase table. It seems something was amiss with our current fields. Maybe since they were created prior to the 2015 1.1 update. Thanks for the input.
They're just a count of records in related tables. The count only changes when there's an election so I've turned off the rollup jobs for now but we really need it during election time and that's when we need the system performance too. If my first idea doesn't work I'll put in a ticket.
Yes , if the rollup fields create that much records so you should not go with the rollup fields for your current requirement .Make your rollup fields as much as simple and if it's needed hourly basis then I would recommend go with the custom code.
BTW , is it possible to share the condition of rollup fields here to understand what it contains.
You may raise ticket to MS if you feel as this is OOB functionality and you don't have any control for those record creation.
The thing is it's all of our rollup fields. My thought is to delete the fields, delete the data, and then re-add the fields. Or go to the alternate option as you suggested. This issue was supposed to be fixed it 2015 1.1.
I think something went wrong with the roll-up field conditions . This is strange in a day 85 k records created and the table you mentioned , seems you can not delete data from there using bulk deletion functionality , so I would suggest identify the Rollup field which causes data creation and go for some alternate options like workflow or plugin.
We are currently removing the system jobs so they are not there. The issue is that the RollupJobBase table still has 6.5 million rows and it seems to be running an update on all of those records when the rollup job runs. We would like to get rid of those but not sure if we can just delete the older records or all of them from the table.
Hi,
Take a look at System Jobs and see if you can find these records there. Basically Rollup field create a system job for each execution. If these records are in completed state then you can simply create a bulk delete job and delete these records. You can also schedule the job to do this periodically.
crmtipoftheday.com/.../scheduling-daily-bulk-delete-jobs
Also, as you mentioned that the data in these fields doesn't changed that frequently, you can change the frequency of these jobs as well.
dynamicscrmpros.com/changing-rollup-calculation-frequency-microsoft-dynamics-crm-2015
Hope this helps.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,228 Super User 2024 Season 2
Martin Dráb 230,056 Most Valuable Professional
nmaenpaa 101,156