Thread Details
  • State Not Answered
  • Replies 8 replies
  • Subscribers 354 subscribers
  • Views 931 views
  • Users 0 members are here
Forum Actions
Related

Clean audit tables?

Jeff Bickart

We have been using Sugar for more than 6 years. We have audit log records that go back to the start of our use of Sugar. The Archive Data tool does not have the ability to archive audit tables. What is the best practice to remove older data from these tables?

Parents
  • 0

    I raised a case with support and they trimmed the pmse_bpm table for us (sell, cloud, 14.0 back then, now 14.2).
    Everything older than a month.

    That seemed to have had a great effect in reducing the DB storage by  3.7GB...!

    I also noticed that when I view the Process List (/#pmse_Inbox/layout/casesList) it's lightning fast... previously I would open it, go and do something else for a bit, then come back to it. So this is a nice improvement too.

    This was in reply to my question/case:

    There is no way via the UI to delete data from a pmse_bpm table. This is on purpose as the data within those tables control moving processes in your instance and deleting something incorrectly can result in lots of problems. The size of your pmse_bpm_flow table is quite typical, but I'd be happy to trim it for you to reduce size if that's okay with you.

Reply
  • 0

    I raised a case with support and they trimmed the pmse_bpm table for us (sell, cloud, 14.0 back then, now 14.2).
    Everything older than a month.

    That seemed to have had a great effect in reducing the DB storage by  3.7GB...!

    I also noticed that when I view the Process List (/#pmse_Inbox/layout/casesList) it's lightning fast... previously I would open it, go and do something else for a bit, then come back to it. So this is a nice improvement too.

    This was in reply to my question/case:

    There is no way via the UI to delete data from a pmse_bpm table. This is on purpose as the data within those tables control moving processes in your instance and deleting something incorrectly can result in lots of problems. The size of your pmse_bpm_flow table is quite typical, but I'd be happy to trim it for you to reduce size if that's okay with you.

Children
  • 0 in reply to Luke Ridgway

    Hi  ,

    the problem with that kind of basic cleaning is that your BPM can't be defined to run only once. So if you delete the previous execution trace, it can be triggered again.

    Same for audit ; it could be great to keep the last change of a field instead of cleaning the full table ; furthermore, with GDPR / Data Privacy, the audit seems to be used to provide the last user that set the field.

    But of course, those tables (audit and pmse working tables) need to be cleaned for performance and DB sizing (even more on the cloud) and it would be great that this cleaning (as the core prune jobs) will be a part of the Sugar solution.

    Fred