Hi All ,
When batch jobs execute, their execution history is stored in the batch job history. This helps in monitoring and validating proper running of (recurring) batch jobs, their execution time and possible logs. However, with a lot of recurring batch jobs, especially those with a high recurrence, will generate a lot of batch job history entries.
AX 2012 R3 has lot of out of box clean up batch jobs and MS suggests to run these batch jobs also as per analysis and client need .
But it's not clearly called out how much it would help to improve performance or other factors ? Can you all share your real world experiences over performance improvement by enabling standard batch jobs ? How can we quantify or measure the performance improvement ?
Further , any additional high volume history data also to be cleaned up apart from MS suggested standard clean up batch jobs to improve performance ?
Thanks in advance.
