Remove data from idempiere application which is greater than 10 years.

74 views
Skip to first unread message

Hansa Jha

unread,
Aug 1, 2025, 6:24:06 AMAug 1
to iDempiere
Hi,

To improve the performance od our idempiere application we would like to cut, archive, or purge old data (e.g., transactional data older than 10 years) in iDempiere.
How to do this in idempiere?
Any suggestions would be greatly helpful.

Thanks & Regards,
Hansa Jha

Heng Sin Low

unread,
Aug 1, 2025, 7:49:01 AMAug 1
to idem...@googlegroups.com

**************************************************************************************************

PLEASE READ: The information contained in this e-mail is confidential  and intended 
for the named  recipient(s)  only. If  you are not  an intended recipient of this  e-mail 
please  notify the sender immediately and delete your copy  from your  system. Our 
company accepts no liability for any damage sustained as a result of viruses in this 
e-mail or any attachment(s) to it.

**************************************************************************************************

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/idempiere/a149a95c-3291-43fd-b20e-17ac810840ddn%40googlegroups.com.

Yahya Kammukutty

unread,
Aug 23, 2025, 8:03:10 AMAug 23
to iDempiere
I think house keeping needs enhancement.  Please see a sample table size from one of my servers.
 schemaname |       table_name        | total_size | table_size | index_size | n_live_tup | n_dead_tup
------------+-------------------------+------------+------------+------------+------------+------------
 adempiere  | ad_changelog            | 73 GB      | 42 GB      | 31 GB      |  196890636 |      28135
 adempiere  | ad_issue                | 32 GB      | 26 GB      | 6280 MB    |   24919706 |          0
 adempiere  | fact_acct               | 17 GB      | 6978 MB    | 10179 MB   |   25611946 |       2048
 adempiere  | ad_session              | 6219 MB    | 4498 MB    | 1721 MB    |   14596410 |       3739
 adempiere  | m_storagereservationlog | 5956 MB    | 4046 MB    | 1910 MB    |   20030940 |         79
 pg_toast   | pg_toast_365979         | 3787 MB    | 3731 MB    | 56 MB      |    2388860 |          0
... All others are much less than these.... Total DB size only 175 GB

We cannot blindly delete these tables' data. May need way to identify what can be deleted and what not.

Has anyone handled this already? Please share your thoughts on this. 

My thoughts .... 
AD_ChangeLog -  Keep specific columns like Total, DocStatus, qty. Better to review dictionary for the columns to be logged at first place. 
AD_issue, Ad_session - Keep last 1 week...

thank you,
Yahya

Carlos Antonio Ruiz Gomez

unread,
Aug 23, 2025, 8:17:37 AMAug 23
to idem...@googlegroups.com
Yes, that's the intention of the SQL Where clause in the Housekeeping configuration:

You can check the 10 preconfigured examples in the database that delete the T_ tables preserving the last week - or last 2 days for T_Spool.

Regards,

Carlos Ruiz
Reply all
Reply to author
Forward
0 new messages