Breaking news from around the world
Get the Bing + MSN extension
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
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I've been trying to find examples of on premises deployments of Dynamics AX that are not only highly available but also have zero downtime in a 24/7 production facility scenario. I haven't been able to find one so i was wondering if that is even possibly to achieve, or is it always the case that a minimal service window is needed during release update?
Zero downtime is not possible at the moment. There will be downtime when you apply updates.
Microsoft is aiming for "zero downtime" at least for the cloud version, and I would expect that the same improvements would be available in on-premises, too. If not at the same time, then later.
But I would expect even in the "zero downtime" there would be a moment where you can't have ongoing transactions in an AOS. Since the system must somehow switch from the old version to the new version.
And I don't know how they will get rid of the downtime that is needed for the database sync. New version might introduce new database fields, so the database must be synced before the application can access the new fields. If the application tries to access a field that is not in the database, you will get an excption. The sync would need to happen before updating the application.
Thanks Nikolaos for the quick reply. Although it's not the answer i would have hoped for it what i was fearing the case would be ;)
One last question if i may;
Would you know of any best practices to keep the downtime to a minimum during a service window? i.e. regular restarts of the AOS severs to keep tempdb's minimized, procedures for test and validation etc?
I don't think you have much control over the downtime duration. It's almost entirely in Microsoft's hands since they design the deployment process and scripts.
Business Applications communities