sap-space-reclaimlisted

# Space Reclamation Assessment Two different jobs get confused here. **[sap-housekeeping](../sap-housekeeping/SKILL.md)** keeps a healthy system healthy — the standard reorganization jobs that should already be running. **This** skill is the *assessment and one-off reclamation project*: the system is already large, and someone needs a costed, evidence-backed list of what can go. > **Guardrail — measure, then propose, then delete.** > - **Never delete before sizing.** Every candidate gets a *current size* and an *estimated reclaim* (§2), > because effort is only justified by the number. > - **Deleting rows ≠ free disk.** On most databases the space stays inside the datafile/datavolume as > reusable space. **Reorganization is a separate, usually disruptive step** (§6). Say this out loud in > every estimate, or the reported "saving" is fiction. > - **Retention is a setting, not a delete.** Where a retention parameter exists, *fixing the setting* is > the durable win; a one-off deletion just restarts the clock (§3, §4). > - **Logs may be legally retained.** The Security Audit Log especially — archive and verify readability > *before* deletion, never delete immediately (§5). [G, SAL] > - **PRD: typed confirmation per object**, and prefer the standard job/report over ad-hoc SQL always. > Never `DELETE`/`TRUNCATE` an SAP table directly unless a Note explicitly says so for that table. Verification legend: **[V]** verified during authoring · **[G]** cited to an SAP Note