web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Purging data due to la...
Microsoft Dynamics AX (Archived)

Purging data due to large AX database Size

(0) ShareShare
ReportReport
Posted on by Community Member

Hello ,

We have around 5 TB size of our AX (AX 2012 R3 CU12). Can you please give your suggestions for purging data so we can reduce our AX database size.

  We have examined that some of tables takes too much of data (i.e. sales Table /Sales Line - 2TB around) so we thinking to purge data for these tables.

  looking for your best suggestions on this issue.

Thanks.

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    Community Member on at

    Can anyone would suggest me please on this??

  • Verified answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at

    AX has a bunch of functionality available under the Periodic > Clean-up section of each module for purging. If your reports and data warehouse are written correctly to use posted history tables instead of pointing directly to SalesTable/SalesLine, you have functionality to delete already invoiced sales orders.

    Such cleanups can take extensive amount of time and cause locking in the DB, so it should be exercised with caution. Make sure you test everything first.

    Also the IDMF tool can help with purging data that you do not have to legally keep for extended period of time, or just archive it by moving out of the AX database.

    docs.microsoft.com/.../microsoft-idmf

    Also having just 2 TB in salestabe/line suggests that you have added a lot of extra fields on those tables, or use containers/memo fields bloating your database, which are not exactly best practice. It is best to move out those to newly created custom tables with a RecId-based relation.

    Removing not used indexes on the table can also do considerable amount of space savings. Those could be identified with DynamicsPerf or SQL Server DMVs easily.

    Finally you could consider applying compression for the data and indexes on a table-by-table case. We just did that on our SalesLine for indexes where it had >75% read <25% write operations with a space saving of at least 25%, and disk space occupied went down from 350+ GB to 70.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans