Deze blog bespreekt de mogelijkheden voor de automatisering van post-refresh cleanup taken (na een database restore) via scripting.
Deze blog bespreekt Microsoft’s LCS ”Self-Service Database Refresh” voor het terugzetten van een productiedatabase in een sandboxomgeving.
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:
When you want to work with the new Microsoft Dynamics AX, you have some options to deploy the environment. You can choose between deploying an environment on Azure or download a local machine. The purpose of the local machine is mainly a development box, but can also be used for demonstrations (with some limitations). The local environment always contains a predefined demonstration database. What if you want to start with an empty AX database or test with configurations that will be used by the customer? Continue reading and you will know how to start with another database.
Congrats to the Microsoft Dynamics AX team. They had completed the Release to Web (RTW) version of Microsoft Dynamics AX last Monday. This version has build number 7.0.1265.3015 and has been made available for deployments now. A downloadable virtual machine (VM) will follow soon.