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

Gert Neetesonne CEGEKA Solution Architect

Gert Neetesonne

Joined: 3/6/2018

  • More standard cleanup or archiving jobs for standard tables

    Tue, 29 Oct 2024 06:47:58 GMT – Dynamics 365 Finance – New 

    Since the price model of Dynamics shifts to a capacity model, the storage cost of database tables becomes more and more important. Dynamics has quite some tables for which no cleanup functionality exists, but can grow large in size and thus become very expensive.

    Some of the tables are marked as internal in the application, so it is also impossible to create cleanup jobs yourselve.


    Examples of such tables are DIMENSIONDATAINTEGRITYLOG and DIMENSIONHASHMESSAGELOG.

    When you are using financial dimensions on a detailed level (in our case, per project) these tables can grow very large (50+ GB).


    • DIMENSIONDATAINTEGRITYLOG: The "DIMENSIONDATAINTEGRITYLOG" table serves as an integrity log, documenting changes and identifying issues. While it is not crucial for the regular operation of the system, it proves beneficial for troubleshooting. Truncating this table is optional. If you choose to do so, please note that it won't impact the system's immediate functionality. However, retaining the data can aid in resolving potential dimension-related problems in the future.
    • DIMENSIONHASHMESSAGELOG: The "DIMENSIONHASHMESSAGELOG" table is dedicated to storing hash calculations for each dimension set and combination. Similar to the integrity log, it is not essential for the system's day-to-day functionality. Truncating this table is at your discretion. Removing this data won't cause immediate issues but keeping it could expedite the resolution of dimension-related problems that may arise later.


    Although the data stored in the table is not crucial for the application, Microsoft does not want to cleanup the tables. We thus are requesting integration of this "troubleshooting data" in the long term data archival functionality or a cleanup option to remove older entries of this tables.


    There are more examples of this kind of tables in other areas of the application (MCRORDERLINE2PRICEHISTORYREF, ERFormatMappingRunJobTable,...)