Database timeouts and high CPU load on the database server after upgrading to 4.61
Versions:
4.61,
FAQ number:
164,
Old FAQ number: 8714
The 4.61 release contains new functionality that limits the number of history entries that are saved for scheduled jobs to 100 per job. In previous versions of EPiServer the history log could grow unhindered so it is quite likely that pre-4.61 databases contain a large number of history entries. History entries are stored in the tblScheduledItemLog table.
This new function can cause problems after upgrading to 4.61 if as it will remove a lot of rows in the tblScheduledItemLog table using a lot of CPU resources on the database server and possibly causing timeouts for other database queries.
Should you experience the problems described above the solution is to manually empty the tblScheduledItemLog table, but please note that you will lose all history for all scheduled jobs in the process.
Should you not empty tblScheduledItemLog manually the problem should disappear over time as the entries in the table are gradually being removed. Depending on the number of entries this process can take several days, so it is not our recommended solution.