Analyse Size of Acumatica Database

Hi Everyone,

Sometimes, when you have big Acumatica database, you might want to know how much space does it taken by what table.

This script can help you:

The result of this script on my demo database is here:

Samples of heavy tables in Acumatica
You can see that I have highlighted some tables that contains a lot of data. Actually some of them does not contains important information.
Let me point you on some tables that you can archive and clear if you aware about space. This can be helpful if you use cloud hosting and the size of database is not cheep.
  • Logs Tables
    • LoginTrace – all login, logout, screen opening, session expired, customization published events
    • EMailSyncLog – all history of exchange synchronization
    • LogRecord – all history of exception logs
  • Performance Monitor Log –  et of tables that save trace of requests, sql querries, memory usage. This can be helpful for Acumatica support and performance issue investigation, but after that you can clear it.
    • SMPerformanceInfo
    • SMPerformanceInfoSQL
    • SMPerformanceInfoSQLText
    • SMPerformanceInfoStackTrace
    • SMPerformanceInfoTraceEvents
    • SMPerformanceInfoTraceMessages
    • SMPerformanceSettings
    • SMPerformanceValues
  • Historical Information
    • AUScheduleHistory – all history of scheduler execution
    • UPHistory – all history of application update
    • AUNotificationHistory – all history of notification operations.
  • AuditHistory – This is field level audit log. Some times it can be too big, if you use audit a lot. It may be useful to archive this table to file system and clear it in database.
  • UploadFileRevision – This table contains binary data of all files and images that have been uploaded and attached to different entities and screens. Usually this table is huge. Sometimes you can clear old files to save space. Also you store a copy of big database for testing purposes, you can clear this table.
  • SYData – Here you can find all prepared data for import/export scenarios. It can be easily cleared after completing all import/export operations.

Have a nice maintenance!

4 Replies to “Analyse Size of Acumatica Database”

  1. I have a question in my acumatica data size usage in user interface, the total size is about 36 000GB but in sql server database size is bigger, it’s up to 100GB. Could advice me what’s happen ?

    1. The rest of space probably can be occupied by snapshots. Please check that you have no snapshots and also click Optimize Database to clean any orphan data.

  2. Hi Sergey,

    I just noticed that my SMPerformanceInfoSQL table has 58.4 million records!

    Is it ok to truncate any of these tables assuming you do not need for diagnostics or history?

    1. Hi Jeremy, this table related to Request Profiler.
      Usually you should enable request profiler only when it is needed. If you enable and forget to disable it occasionally it may generate number of the records in the database and slow the system performance.
      There is a button in the interface at the request profiler screen to clear logs. I recommend you to use it.

Leave a Reply

Your email address will not be published. Required fields are marked *