Maintenance Activiti Database

[fduartej]

What is the best strategy to maintenance activiti database?

Hi We are working with activiti for 1 year and now we have 50GB storage on the database and we want to maintenance this database in order to reduce the space used, we are checking some tables that we could reset this tables start with suffix ACT_HI, will it a good option to truncate this tables? or what would be the best option please if there is a topic about it share me the link in order to review this strategy.

Regards
Fred

[sathish1]

Thinking retention policy will be based on organization needs. But one thing to keep in mind from, if there is a need to run reports based on the historic data, then it is better to push it to s dataware-house set-up before cleaning up the history information. Will follow the this thread if there are other recommendations.

Cheers.

[fduartej]

I know it, but if we want to clean all historical data just should resest ACT_HI or if I clean it affect other component on activiti?

[martin_grofcik]

Hi,

ACT_HI tables are used in reports and in activiti-crystalball simulation/debugger.
If you do not need reports and simulations you can archive them.

(test it first - it is just my guess)


Regards
Martin

[frederikherema1]

It's perfectly safe to delete/archive stuff from the ACT_HI_* tables, there are no foreign key constraints between history and runtime, nor between different history entities. Only make sure all entities belong to an ended process though (ACT_HI_PROCINST has an end-time).