We are trying to resolve an issue with capacity related to the Activity Pointer Base table - below is a recap:
Our Activity Pointer Base table size is disproportionate to the the activity tables that roll up to it. Row comparisons are equal but he size is off - the Activity Pointer Base is significantly larger than the rollup tables.
Have engaged Microsoft support who's only recommendation is to delete emails to reduce the activity pointer base table size.
Here is a summary of the database table size information as of January
Has anyone else ran into this problem? The only advice from Microsoft is to delete Emails, but then we lose historical information. And deleting would not solve the disproportionate size issue.
Waiting for final word from Microsoft - several steps were taken on their end to troubleshoot - they acknowledge that there is a discrepancy in the size of the tables, but have stated the table is performing as expected that there are not issues with the indexes or sync jobs between APB and individual activity tables.
Have a look at www.d365-shrinky.com. Addresses the description issue with embedded images, no loss of data just a reduction in size.
Have a look at www.d365-shrinky.com. Specifically addresses the description field where there are embedded images (not separate attachments). Free to download and will tell you if you can save space this way.
info@d365-shrinky.com
@celiohenrique - we implemented https://www.mscrm-addons.com/Products/AttachmentExtractor. Microsoft solution was to delete activities which is not an option for us.
Hi @loriatracy Did you find what was causing this error in storage? I have the exact same problem and wondered if/how Microsoft resolved this. Thank You.
Interesting point - I'm not entirely sure. I would have thought so, but that's not a given. Not currently running it in my current workplace so I can't check...
I'm assuming if the email Description content is extracted (removed) from dataverse and stored in blob storage, then the Description column in the ActivityPointerBase Table will also be empty?
MSCRM-addons is a good and relatively cheap solution. In addition to extracting attachments to Sharepoint, you can set the Attachment Extractor function to extract the content (Description field) to Blob, and stream it back in to Dynamics (so users see no difference). Very useful...
Hi,
At a previous implementation we used: https://www.mscrm-addons.com/Products/AttachmentExtractor
Primarily it reduces costs by putting attachments into SharePoint, however I believe it also does something with the description field.
Hi! I have this same issue.
How to apply this solution with sharepoint or blob suggested by @ChrisPiasecki ?
Thanks!
@ChrisPiasecki Any recommendations on archiving - and can these still be accessible from the CRM record?
stampcoin
17
mmbr1606
15
Super User 2025 Season 1
ankit_singhal
11
Super User 2025 Season 1