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
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 | Upcoming TechTalks
We installed the 2.2 version of the monitoring tool last Friday to start collecting and reviewing our system for potential improvements. For the first few days everything went well, then yesterday (Tuesday) when all of a sudden our tempdbs started to grow out of control. The went from ~2.5GB per file (we have 8 tempdb files) to triple that filling the virtual disk in seconds. Thinking this was a fluke we expanded the disk size of the drive and kept monitoring only to have another rapid increase a few hours later. Environment:
1. Dynamics AX 2012R2 RTM / unpatched. Over 7 years worth of history is contained in the DB, we have a 200+ store retail chain
2. AIF used to integrate with magento 2.0 website
3. Scheduled Power BI jobs to load data to cloud
4. Standard client access via app
We have stopped the monitoring jobs from running to avoid another instance of this for now but would like to get them turned back on once we can figure out why the above might have happened. Has anyone else seen the tempdb grow so quickly when the monitoring jobs are running and if so how was it approached to prevent drives from filling up and causing errors across AX?
Thanks in advance,
Business Applications communities