A Customer Wants to Increase the Storage Capacity by 25gb

Latest Customer Engagement Licensing Change Could Lead to Dynamics 365 Storage Cost Increase

With the latest Dynamics 365 licensing changes (see Dynamics 365 Licensing Guide – April, 2020), there’s i change that small-scale business owners and IT administrators should be aware of. If y’all’re running Microsoft Dynamics 365 Customer Engagement (CRM), then yous need to be aware that the data storage model is changing, and could potentially lead to a Dynamics 365 Storage Cost Increment.

Where to Look to Place Biggest Data Storage Offenders

The first place to look to see if you may be impacted is the Power Platform Admin Middle. Just navigate to https://admin.powerplatform.microsoft.com and wait at the summarized storage capacity usage. Notation that the storage capacity summary shows how much data storage is used past all the environments in the tenant. The storage capacity is broken down past Database, Log, and File blazon. Database is your actual data, Log is your audit logs, and File is file attachments.

Until this alter, a lot of third-political party add together-ins were geared towards reducing the corporeality of space used by file attachments in your CRM system. It is hardly necessary to worry near files saved in your CRM system now, because you’ll have 20 GB for the tenant to outset, and an boosted 2GB for each full-licensed user. So, if you have fifteen users, you’ll have 50GB of file storage — more than than enough for most user environments.

Nevertheless the

Database


Storage
metric is more likely to be over the available chapters. You get 10GB for the tenant, and an incremental 0.25GB for each total-licensed user. Every bit shown on the chapters summary image above, you can see that 10GB + 15 users x 0.25GB = xiii.75GB. And you tin see that we’re using eleven.07 out of xiii.75GB. Once more annotation, this is the summary page and measures across all your environments (e.yard., your Production plus your Exam environments). The screenshot below shows the breakdown past environment (or organization).

Affect of Dynamics 365 Storage Costs Increase

Here we tin first to get an idea of the bear upon of the Dynamics 365 Storage Costs Increase, if you accept a few years of information, and a full-copy test environs, you may exist over your allotted capacity for the CDS Database Capacity metric. Under the previous licensing, you could purchase boosted chapters for $5 / GB per month. Now it’s $40 / GB per month.

Dynamics 365 Storage Costs Increase Mitigation

There are ii places to look to see what could be major factors impacting your CDS database usage. First, await to see if you take multiple environments with equivalent database sizes. If you take a test or demo surround of equal size to production, chances are you lot tin pare that down. Rarely does the test environment need to have all the historical data that the production environment has.

In our case, above, you tin can come across that we have four.66GB in prod, 3.i GB in the demo environment, and one.13GB in our Examination environment. If you don’t need a test, demo, or preparation environs, then these environments tin can exist deleted to free upwards capacity. If you practise need them, you still have options.

What Tables are Using the Most Storage Capacity?

From the screenshot, below, you tin can run across the tiptop ten tables that are using up database capacity. Every bit indicated in the graphic, in that location are a few tables that you lot may non be able to do anything about. If y’all have managed solutions that you’ve imported, and are still using, you won’t be able to delete data from, or reduce the size of those tables. (Though, if you don’t need those solutions in your examination surroundings, you can delete them from there.)

A proficient place to start is to download all the tables data, showing which tables are using the most data – from biggest to smallest. The table names listed are what are chosen schema names or logical names, every bit opposed to the friendly display name of the table. You can get more data about the specific tables via either the Metadata Browser or the Metadata Documentation Generator using the XrmToolBox.

Backup Essential Information to Long-Term Storage, then Delete Older Information

Once you identify the tables taking up the most space, yous can get to piece of work reducing the information size. If the information is non-essential, y’all tin run bulk delete jobs now, and schedule recurring majority delete jobs to periodically delete the information to keep information technology in check. Another strategy would be to delete merely the older information. For example, customer back up cases could be deleted if they’re older than one year old. Perhaps there are certain types of customer support calls that can be deleted, merely y’all definitely want an archive in case y’all ever need to refer back to them. In this case, nosotros can “save-off” a copy of your CRM data to an Azure SQL Database. Then you tin configure the database with a long-term memory backup policy (LTR) to automatically retain the database backups in separate Azure Hulk storage containers for up to 10 years for the Azure SQL Database.

Unexpectedly Large Web Resources Table

Nosotros had a recent case with a client, where they have a Dynamics 365 Customer Engagement Plan license, and had all the major apps installed; like Sales, Customer Service, Project Service Automation, and Field Service. We noticed that the database size increased dramatically overnight, and this was considering of the Spider web Resources table, which is where the size of the solutions files would prove in the database. After a telephone call with Microsoft, we were advised that there was a “technical glitch” — that happened around Baronial, 2020 — where the database web resources tabular array increased unexpectedly in size. Nosotros were told that all these four apps (sales, customer service, project service, and field service) should merely take up approximately i.5-to-two.0 GB in the spider web resources database table. Since we inquired most this issue on behalf our customer, we were told that they (Microsoft) would look to have the web resources database table shrunk dorsum down to the expected size.

Note, in the screenshot below, that this is showing the data storage issue for but 1 “org” — meaning that if you have the same problem in 2 organizations, you volition have twice the unexpectedly oversized Web Resource table data storage problem.