Rough Estimate on Storage needed in Dynamics 365 Customer Engagement

Dynamics 365 Customer Engagement

With effect from 1 April 2019, new Dynamics 365 agreements will use a new definition on storage – For details see Dynamics 365 Licensing Guide. Now storage is divided up into 3, Database, File Capacity, and log Capacity.

Common Data Service for Apps Database
Transactional database storage for entity definitions and record data.

Common Data Service for Apps File Capacity
Capacity to store attachments for notes or emails in D365 Customer Engagement apps and PowerApps. This can include Word documents, image files, PDF files, spreadsheets, videos, and other business files.

Common Data Service for Apps Log Capacity
Separate storage capacity for audit logs will track records and attribute data changes. This includes field value record updates, previous values, security role updates, data/time of access.

Additional Instances are free of charge… almost

Effective April 1, 2019, organizations that transact on the new platform capacity license no longer need to pay for additional production or non-production environments.

Create as many production or sandbox instances for Dev, TEST, and UAT as you like as long as you have at least 1 GB of CDS for Apps Database Capacity available. Storage capacity is shared between all instances.

Be aware that you still need to buy add-on Marketing and Portal instances.

In Dynamics 365 Customer engagement cloud version to see if there is leftover storage use the new Capacity view as an admin.storage-consumption-1

Migration from Dynamics CRM onprem… how much Cloud data do i need?

If you need a Rough estimate on Storage needed in Dynamics 365 Customer engagement online based on your Dynamics CRM onprem then use the following to calculate a rough estimate.

Screenshot (1)

File Capacity

In Dynamics CRM on-prem, Determine the size, including index, of the entity/table “Annotation” by fx using Microsoft SQL command to list table size: sp_spaceused ‘Tablename’. The Result would be the rough estimate on File Capacity needed in Dynamics 365 Customer Engagement.

Log Capacity

In Dynamics CRM on-prem, Determine the size of the table “Audit” by fx using Microsoft SQL command to list table size: sp_spaceused ‘Tablename’. The Result would be the rough estimate on Log Capacity needed in Dynamics 365 Customer Engagement. audit table is stored here: “Organization_name_MSCRM”.[dbo].[Audit]

Database Capacity

In Dynamics CRM on-prem determine the size of the Content Database “Organization_name_MSCRM” and subtract the size of the estimate on above File and Log capacity. The result would be the rough estimate on Database Capacity needed.

UAT, TEST, and Dev instance Capacity

Usually, you want to have a full copy of production as a UAT sandbox instance and if this is the case then multiply the rough storage estimate with 2.

Usually, you also have a Test sandbox instance and a couple of Dev sandbox instances,…None of those normally hold a lot of data and for a rough estimate add 2 GB pr sandbox instance to the needed Database Capacity

WebResourceBase is now in File instead of Database https://arundynamix.blogspot.com/2020/12/webresourcebase-is-now-in-file-instead.html?m=1

One thought on “Rough Estimate on Storage needed in Dynamics 365 Customer Engagement

  1. I love how you presented your ideas in this post. Your insights are thought-provoking and well-explained. I especially appreciated the examples you provided to illustrate your points. Read Blog-https://www.dynamicssquare.com.au/blog/dynamics-365-storage-cost/

Leave a Reply