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 1 Discover 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 Timeline
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 are migrating crm 2013 to crm 2016 onpremise.We have huge attachments .Annotation table size is 245 GB.
Org DB size us 350 GB.
we want to keep the attachments as is.
What will be best approaches while migrating using Organization import approach?
According to me, best approach to save the Storage would be to move the Attachments to Azure Blob or Sharepoint.
Add a link to that file on storage location to the actual CRM record.
You are right, you will save a lot of time, if you do the Organization Import as your attachment data does not have to be migrated.
Any other approach will be a lot of time consuming, considering the size your DB file
If you're doing an organisation import, then I don't think the size of the attachment table will have much impact on the time it takes, as it won't need to process the data in any way. It would affect the time to copy or backup/restore the database, but that's not normally a large part of the overall upgrade time
To make the import fast we are thinking of below approach please guide us.
1. Restore the Org DB on sql server 2014.
2. Take a backup of Annotation table in a new custom DB.
3.Set the documentbody column of Annotation table to Null.
4.Shrink the Org DB to reclaim the attached files space.
5.Import the Org
6. Update the documentbody from Backup table
Is this approach right?
The approach will work but it is unsupported.
If it is onprem then simply import the org - 300 GB isn't that big that import wont handle. You can always involve support team in case you get error. But with direct CRM table manipulation even the support team wont be able to help since you went the unsupported way.
Business Applications communities