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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 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
I apologize in advance for a long post, but wanted to give as much background as possible. Plus, I am really, really new to the AX realm, so please bear with me.
I am a SQL DBA supporting / inherited an installation of AX 2009. Yay me...
I looked up several combinations of keywords from the title, few posts came up, but none had a clear and definitive answer and the only one that came close was the one regarding the DOCUVALUE table. I am looking for such an answer to back up my case with the business.
My scenario is as follows:
My suggestion for the business were as follows:
And my questions
Any pointers, links or jokes welcome
Thanks in advance.
Live long and prosper
Same questions had been discussed long time ago. Please see blog
Generally, AX access SQL in same way with other standard application. How SQL manage file is not relevant with AX. You need to balance database size and performance. And I are not recommend to save binary file in the DocuValue. It's better to only save file batch refer to file server
That's what I also expected, but people over here are reluctant in adopting this design stating it is not supported. The DocuValue table was just an example I came across that involved multiple filegroups design. I also expect that data compression be supported as it's a matter of SQL internals, unless in the synchronization phase detects it and decides to rebuild all tables.
That was the blog I was referring to in my original post, but it said that partitioning a table over multiple FGs is not really something they would recommend. My proposal doesn't use table partitioning in the traditional sense (with partition functions and schemes) but rather splitting the data and indexes over multiple FGs.
Thanks for all the points, appreciate it.
Regards and stay negative. COVID19 negative :)
Business Applications communities