Retention, archiving and purging in Protheus
Plans data lifecycle before removing records.
Overview
Retention determines availability needs, archiving preserves access outside active operations, and purging removes data under an approved policy. D_E_L_E_T_ logical deletion is neither physical purging nor guaranteed anonymization. Inventory tables, relationships, volume, owners and integration dependencies, agree criteria with business owners, and confirm module-supported maintenance. This guide sets no legal retention periods and supplies no generic DELETE. On SQL Server backups differ from queryable archives: test restore and reconciliation before maintenance. (Sources: refs. 1–2.)
Commented example
#Include "Protheus.ch"
User Function Ed622()
// Fictional inventory; neither purges nor defines a retention period.
Local aPlan := {{"ZZ1","OWNER","CRITERION_PENDING"}}
ConOut(Len(aPlan))
Return NilOne planning item, without database access. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
- Validate restore, relationships, before/after totals and query continuity before running an approved procedure.
- Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.