A tip to keep your SharePoint_config database under control
Every once in a while, the situation comes about where a developer or administrator notices that their SharePoint_Config database has grown extremely large in size. This is not a newly documented issue and you can find the detailed steps from the blog post link below. What’s happening here is the timer job “Delete Job History” at some point has to many records stored in SQL for it to be able to complete before it times out or runs out of memory.
My tip here is that if you’re creating a new environment or once you’ve cleaned up your existing environment, is to change the “Delete Job History” schedule from once a week to once a day. This will help to keep the timer job in a state that it’s able to complete its work and have the database size under control.
