Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We have migrated the AX to Azure and changed the SQL Server 2014 to SQL Server 2016. The servers is better than the on premise servers, but the performance is so bad! The on premise servers were using the SQL Server 2014, but now is not possible to rollback the migration from SQL Server 2016 to SQL Server 2014. We did some tests, but nothing was detected before the Azure Go Live. We are working to create new indexes, but it is so strange. Anyone have had the same issue?
You have to start monitoring what could cause the issue. Is it latency, SQL server settings, indexes, storage or insufficient hardware resources? You can only find out by monitoring hardware resources and looking at SQL performance reports. You can also ask this questions on the SQL server forum as it is in fact not directly related to Dynamics AX.
Did you use Premium Storage (SSD) for the database servers? That's the first thing to check. I don't think your problem is related to SQL Server version, most likely it's something else. And the most common reason for general slowness in AX is poor disk performance of the database server.
You can use DynamicsPerf tools with PAL tool (Performance Analysis of Logs) to analyze the disk speed and many other things. Basically it uses Windows Performance Monitor to capture certain metrics and then generates a report for you.
Or you can just check the disk related counters yourself. Disk read/write wait time, disk read/write queue length for example.
We are using the Standard_DS14_v2. This option has SSD disk.
When using this machine type, you have choice to use standard HDD, a standard SSD or premium SSD for the disks. Ensure it is Premium SSD.
Andre is right, DS machines support SSD disks but you have to choose to use Premium Storage when you deploy the system from LCS.
Hi Andre! We are using the SSD Ultra (Premium).
Then you can use the DynamicsPerf tools mentioned earlier to gather diagnostics information about your system.
Is it overall sluggish or are only some processes slower than in your old system?
Sql 2016 should be faster. However, how its configured for you we don't know.
I suggest review this help first: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/lifecycle-services/ax-2012/plan-2012-r3-deployment-azure
Particularly these links
In general I have poor experience of azure - most systems I have seen have been undersized, and poorly configured.
For Azure VMs running on Windows Server® 2008 R2 and previous releases, the only striping technology available is striped volumes for dynamic disks. Storage space was a new function made available in Windows 8.0+ and Windows 2012+. Which are you using?
IO is key . so ensure that database settings consider how the IO can be reduced.
A standard disk in Azure has IOPs limits. A storage account has a maximum IOPs limit of 20,000. Avoid storing multiple heavily used data disks in the same storage account. Multiple data disks can be used to stripe storage space, or OS striping to increase the IOPs. You can create a single storage pool with 16 data disks. This helps provision 8000 IOPs for the volume. Exceeding the IOPs limit of the given volume would create random high latency.
If you have not configured the disk properly, then you will see error log messages:
You can also try the steps outline here: https://blogs.msdn.microsoft.com/axinthefield/dynamics-ax-performance-step/
Business Applications communities