Data Insight User Guides
Housekeeping – End-to-End Step-by-Step User Guide
This locked guide explains how to use the DDR Housekeeping utility to clean old DDR logs, temporary processing records, export records, run records, and database entries generated during DDR operations. It helps keep the DDR central console controlled, improves long-term system performance, reduces unnecessary database growth, and supports clean governance across refresh and replication cycles.
Purpose of the Housekeeping Utility
DDR Housekeeping is used to remove old and unnecessary technical data created during DDR execution. Every Data Refresh, Object Refresh, System Refresh, simulation, export, import, or background execution can generate technical records such as logs, run details, temporary processing entries, and database control records.
Over time, these records can build up and make the DDR central console harder to manage. Housekeeping gives administrators a controlled way to clean completed or obsolete records while keeping important audit and troubleshooting information available where required.
Key point: Housekeeping should be treated as an operational control process. It should be used to remove data that is no longer required, not to remove evidence that may still be needed for audit, issue investigation, customer reporting, or support review.
Access Utilities from the DDR Central Console
From the DDR Central Console, select Utilities from the left-hand navigation menu. Utilities is where shared DDR control functions are maintained, including Pattern, Business Objects, Exclusion, Number Range, and Housekeeping.
The Housekeeping function is located under Utilities because it is a central administrative task. It supports all DDR execution processes by helping administrators clean up old logs and database records after refresh activities have completed and are no longer required for operational tracking.
Open the Housekeeping Tab
Once the Utilities area is open, select Housekeeping from the top navigation bar. The Housekeeping screen provides selection fields that allow the user to identify which technical records should be reviewed or cleaned.
The user can select the relevant Connection, Export ID, and Run ID. These values help narrow the cleanup scope and reduce the risk of deleting records that still need to be retained.
What Housekeeping Cleans
Housekeeping is designed to clean technical records that are generated as part of DDR processing. The exact records depend on the DDR process, execution mode, and system configuration, but the purpose is to remove unnecessary technical data after it has served its operational purpose.
| Housekeeping Area | What It Means | Why It Matters |
|---|---|---|
| Execution logs | Messages and status records created during DDR runs. | Keeps old log history under control and avoids unnecessary clutter. |
| Export records | Technical records linked to export IDs generated during refresh activity. | Helps clean completed export activity once it is no longer needed. |
| Run records | Run-level details created for individual DDR execution instances. | Allows cleanup at a controlled run level rather than removing everything blindly. |
| Temporary processing data | Intermediate technical records used during processing. | Reduces database volume created by completed or obsolete processing steps. |
| Database control entries | Internal DDR database entries used for tracking and execution control. | Supports long-term DDR performance and operational stability. |
Why Housekeeping Is Important
Without regular housekeeping, the DDR central system can accumulate large volumes of historical execution data. This may make monitoring harder, increase database usage, and make it more difficult for support teams to identify the most relevant recent activity.
Cleaning old technical records reduces unnecessary database load and helps keep DDR screens responsive.
Old logs and obsolete run records can make it harder to find the correct execution history during support review.
Housekeeping helps enforce a clear retention approach for DDR logs and technical records.
Important Housekeeping Controls
Housekeeping should be performed carefully because DDR logs and run records may be required for troubleshooting, audit evidence, customer reporting, or post-refresh validation. The user should confirm that records are no longer required before cleaning them.
Important: Do not clean logs or run records that are linked to an open issue, failed refresh, customer validation activity, audit request, or support investigation.
- Confirm the correct connection before performing housekeeping.
- Check the export ID and run ID to avoid cleaning the wrong execution data.
- Retain records for failed or partially completed runs until support review is complete.
- Agree a retention period for DDR logs based on customer governance requirements.
- Perform housekeeping during controlled support windows where required.
- Document housekeeping activity where internal change control requires evidence.
Recommended Housekeeping Approach
Housekeeping should be carried out as part of regular DDR operational administration. A controlled approach ensures the system remains clean without losing important information.
- Review recent DDR runs and confirm which records are still required.
- Identify completed, successful, or obsolete runs that can be cleaned.
- Select the correct connection, export ID, and run ID.
- Confirm that no active support issue depends on the selected records.
- Run housekeeping only for the approved scope.
- Validate that current monitoring and reporting remain available after cleanup.
Recommendation: Define a standard retention period, for example keeping recent execution logs for operational support and cleaning older records once they are no longer required.
Summary
DDR Housekeeping provides a controlled method for cleaning old logs, temporary processing records, export records, run records, and database entries generated during DDR operations. It improves system performance, reduces unnecessary data buildup, keeps the central console manageable, and supports cleaner refresh governance.
The standard process is to access Utilities, select Housekeeping, choose the correct connection, export ID, and run ID, and then proceed only when the records are confirmed as safe to clean.