-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only small storage gained - Dynamics 365 (Online) #22
Comments
Hi there, In general, you should expect to save about 1.3 times the amount of data moved to your storage account, because the data stored in the CRM database is base64 encoded. From the screenshot, it seems to imply that you have 26Gb of data in your blob storage account (but I can also see that there are other things going into your storage account). The graph on the right seems to be the data throughput, so I can't quite tell exactly how much data you have in your attachment and annotationbase containers. Can you check (probably with the StorageExplorer) what the actual size is of only those two containers? I guessing Dynamics has some kind of optimization jobs that run automatically to compact databases, you might just want to check that too. Let me know please, it's an interesting observation. Cheers. |
So, I see what you're saying. You would have expected the yellow graph to drop down to almost 0 at about the same time as the red one, which I agree with. Looking at what we have and what you should see, the attachments table should be tiny storage wise.
From the graphs, it looks like it took about 10 days after migration for the annotations size to drop, is that correct? |
After implementing the solution version 4. I had verified that the migration tool run completely by check that the "body" have been updated to "IA==". The storage size used does goes down referring to Dynamics Capacity Report but only by a small amount. We have only recovered about 17 GB out of 46 GB of storage.
I would have expected more storage space to be recovered seeing all attachments should be in Azure. Is this normal?
The text was updated successfully, but these errors were encountered: