You’re offline. This is a read only version of the page.
Announcements
5
Hi!
So, I am on a project with a client where we have been tasked to reduce the size of their huge test environment. We have identified and utilized a large part of the standard out of the box features that Microsoft provide, as to clean up and archive/delete data.
However, we are still not a satisfying level in terms of DB size.
I have been spending hours and hours reading through blog posts, google search, learn pages and more, to find best practice in terms of reducing DB size further. We have also deleted via SQL in the backend, but that has caused some functional issues, so we have been sort of going away from that..
So... What are some really good practices for this? Surely it must be an increasing problem, as costumers use up more and more of their DB size.
Picture below of some of the top sized tables that we are focusing on.
Any advice, link, use-case, etc., would be highly helpful! :-)
Br,
Oscar Felfel
Hi Oscar,
Preferrable, I would suggest waiting for the preview and check how Microsoft ensures consistency. For a current inventory transaction archival options (copy to another table), Microsoft replaces a large number of records with a summary record.
Thanks for your quick reply.
We have also provided those upcoming features to the client, as something to look into on the other side of the summer.
But if we are looking at other tables, e.g., SourceDocumentLine and Costumer Tables (CustTrans, CustInvoiceTrans, etc.) how can we proceed in removing records in those?
Is it "simply" just that you have to develop scripts and then hope that they do not hinder functionality?
Hi Oscar,
Microsoft announced upcoming features for archiving GL and inventory transactions. A preview will be available in several months' time.
#1
André Arnaud de Cal...
294,033
Super User 2025 Season 1
#2
Martin Dráb
232,854
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
