Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Hello Dynamics professionals,
I have a short question coming up lately. Hope you can give us some insights.
In our company we have a maintenance job running every saturday for some hours.
The steps in the maintenance job are the following:
We are questioning why we should do the full compile for the production system.
Our support team gave us the additional information that, if they do not do this maintenance, the performance will degrade and the memory usage on some random AOS are going wild.Does this full compile make sense at all? Or are some other things AX is doing internally, when compiling all objects in AOT?If so, can these internal tasks be triggered manually?
In the past there were some issues with AOT server that lead to memory leaks. Applying the proper kernel patch would solve that.
I don’t see point of performing a restart and full compile in a production environment as a maintenance tasks. I know customers that have a stable AOS production environment without any restart for months. They only restart AOS every 2 months to deploy code into production.
Business Applications communities