It is a general complain of any developer. Why is it so SLOOOWWWWW? And yes, it is slow. But there are performance tuning tricks. Slow is influence on 3 things
- Startup VM
- Is also startup of
- Management reporter
- Windows security
- Windows update
- Windows maintenance
- There is no SQL maintenance
- Is also startup of
You could disable the batches & management reporter. That will help. But the real issue is how the disks of that VM are configured. In general, it looks like below 16 lazy disks.
Now you can change these to faster disks , but please be aware of the prices. Also, these are managed disk, the cost fixed amount every month, so stopping the VM will not reduce below cost.
|Size||Premium SSD||Standard SSD||Standard HDD|
How does the disk migration work? The first step is migration to managed disks
Managed Disks simplify disk management for VMs by managing the Storage accounts behind the scenes. Managed Disks also provide granular access control with RBAC and better reliability for VMs in an Availability Set. Learn more about the benefits of using Managed Disks
Source unmanaged disks are not deleted after the migration. Managed Disks are created by making a copy of the source disks. You can revert back to unmanaged disks by creating a new VM with the source disks. Configuration of the VMs is not changed after the migration. Learn more about migrating to Managed Disks
In order to complete migration, we will need to start the virtual machine. Once migration is complete, you may stop the virtual machine.
Next you can change all the discs
But hold on 16 disks multiplied with 18.29 makes 292 euro on top of running the VM. This is very expensive in the relation to how you use it. So next step:
- Archive your code & database.
- Delete the VM
- Deploy a new one
And of course, do not forget to setup the auto shutdown and the azure software reductions
LCS is the place for getting all the information from Microsoft related to your Dynamics 365 for Operations projects. This Web portal also allows you to get your MS fixes to your environment and knows which Knowledge Base (KB) articles have been applied.
In the next image, for instance, we can see that there are 167 fixes applicable. So, let’s start cherry picking.
Deploying packages is a time-consuming thing. MS has improved the speed, but we partner can also help. This helping is by merging the packages. Good merged combinations are Binary updates and x++ updates, but your own code can also be combined with your customizations on your Retail (SDK) part.
Till now I was not able to merge ISV packages, so those must be deployed separately. However, there is quick dirty trick for local VM.
LCS is your friend in Dynamics 365 as long it is up-to-date. And I have seen it is not always the case. So I will share some tricks to force it.
There are some things you should know LCS is only updating 1 time a day and that is 10 o clock in the evening. But when you look in LCS you see it is not updated for a couple of days. So what’s next?
We all must use LCS when working with Dynamics 365 these days, sometimes it feels good and sometimes it is frustrating.
The next real live image of LCS shows how I feel about the experience.
We are speeding up but at the same time we have to wait.
The pitfalls one might encounter are the following:
In this post, I will explain a little bit more about the translations a customer can make use of on the products and attributes in the system. From a user point of view, it is very simple. There is a translation button available that one can click and then add the required translations. From a technical point of view though, it is less simple due to the translations being located in different tables. Getting the required translation, one has to understand how all this functionality is implemented. So where are my missing product attribute translations?
Last year I was creating an interface for products and their attributes. The funny thing was that the attributes did not appear in the interface, but on opening the form, all the attributes were there. So one begins to think what is going on! Where are my missing attributes?
If you want to know the size of a single company in Microsoft Dynamics AX or which tables consumes the largest space in the database, we were used to run the Size of company accounts report. Initially you cannot find this report in the menu structure of the new cloud version of Microsoft Dynamics AX. This post will tell you how you can run this report and how to find or run reports using AX URL parameters.
In my latest blog I showed you the options you have when it comes to updating your AX system. If you haven’t read that one yet check it out here. In this blog we will focus on the Stable Evergreen situation. This is the environment where you have an AX system that is customized to your business requirement. Once this system is delivered you decide not to do any updates whatsoever because you are content with your system right now and why change a winning team, right?
How to decide if you could use a Stable Evergreen
It is best do decide whether or not you want a stable evergreen system as early as possible, preferably before the development of your new system. Base your decision on your future plans. Are new projects coming up? Are there going to be big changes in the coming years? If the next few years seem to be steady and you see no major changes coming up, a Stable Evergreen might be the right choice for you because it can save you a lot of time and money.
Saving a Million on your AX system
A simple calculation shows that someone, who was an AX starter at Rel2009’s introduction, spent on average €1.305.000 on keeping the system up to date. This amount contains 9 CU’s and 1 major update + all the costs of implementing etc (calculation can be provided upon request).
But what if you hadn’t spent that money on updating? What if you would’ve just kept that first system operational? You would’ve saved €1.305.000 and still have a system that operates to your satisfaction. No, you don’t have that brand new and fancy system but it works right? That’s all that matters. Besides, because there were no major changes you could’ve documented every requirement. You know everything about the system so you know exactly what you want for when it is time to finally get a new system. Also, the money you saved in those years can now be used to implement that new AX system completely adjusted to your new needs and wishes.
One of the other advantages of not updating your system is that for your employees nothing changes. No new buttons, no new options. So they get used to it and learn how to use it as efficient as possible, without having to worry if they are doing it right.
Eventually not updating your system has a lot of advantages. It is not for every company. But please, next time you are planning on getting a new system think about this and you might do yourself a huge favor. Do you really need those updates? Feel free to contact us for more information.
Please do share your thoughts on updates, we want to hear your opinion. Also don`t forget to subscribe to our newsletter to receive the latest Dynamics AX news straight to your inbox!