There is no periodic process to clean this table. In case if you have enabled the alert on most frequently change tables or fields then chances are that this table grow substantially. This table should not grow as by default the records gets deleted from this table as soon the event is processed through a batch job. EventCUD: This table is used if you are using the change based alerts. System Administration ->Inquiries -> Batch jobs -> Batch job history, however, If you want to clear the entire log then perform the unconditional delete on this form.ģ. In AX 2012 you can clear this table from path: BatchJobHistory: This table records the batch job execution log depending up on the configuration of the batch jobs. You can truncate this table directly from the SQL Server.Ģ. If you want to clean up the entire table then Microsoft has not provided a periodic process to do this. It keeps log of each and every change you are making in this module. SMMTransLog: This table belongs to the sales and marketing module. There exist some of the periodic clean up processes in Microsoft Dynamics to periodically clean this data. For one of my customer the size of BatchJobHistory has grown up to 550 GB whereas the overall size of all the other tables was not more than 30 GB. You can access this report by right clicking on your AX Db and then follow the following path:ĭo check the report if the report outcome shows tables like: BatchJobHistory, EventCUD, SMMTransLog, InventDim, BOMCalcTrans etc. There is a default report exists in SQL Server to list all the top tables by size. The first starting point is going to find out which are the largest tables in your AX DB who is using the major chunk of your disk space. I will be covering only the SQL Server data file and not the log file here. Today, I am going to discuss how to monitor the database growth and Microsoft recommendations to fix them. At the same there are some recommendations from Microsoft, if followed properly will avoid growing database unnecessarily. The database size grows with the passage of time and this is quite normal thing for a transactional system like Microsoft Dynamics AX. I came across this issue for couple of customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |