nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

archive & purge procedures

mdaviot

Hi,

Are there any recommendations to keep the database healthy in a production environment ? For instance, a list of tables (or better, scripts) which should be archived and purged on a regular basis to keep performance optimal ?

Thanks and regards
Michel

Find more posts tagged with

Comments

jbarrez

Activiti keeps its runtime tables minimal, to keep things fast.

All the stuff in the history tables could be archived. There are no foreign keys from history to runtime.
But it of course depends on your usage of the history: are you querying and displaying history info anywhere? If so, it might not be as easy to remove the history.

Of course, if you don't need the history, you could also turn it off completely.

mdaviot

OK, seems consistent with what we understood so far !

leggebroten

WARNING!!!
At least in 5.16.1 purging the history tables will eliminate ALL data in the activiti-explorer's "Administration" page.

While I expected that the "Completed process instances" would be empty I was stunned to see that "Running process instances" were also nuked.

jbarrez

Yes, that screen uses the history tables for all its queries. The purge query you use should not delete rows that dont have an end time yet.