- 2 minutes to read
CleanUpTimerInterval - System Parameter
The CleanUpTimerInterval System Parameter sets the time, in milliseconds, between two cleanup runs of the Logging Service. Each cleanup run deletes logged data that is older than its retention setting; the retention rules themselves are described in the Logging Service Data Retention section.
At a Glance
| Property | Value |
|---|---|
| Key | CleanUpTimerInterval |
| Data type | integer (milliseconds) |
| Default | 3600000 (1 hour) |
| Read by | Logging Service |
| Takes effect | The Logging Service checks the value every 10 minutes; no restart needed |
| Status | ✅ Active |
How It Works
Each cleanup run of the Logging Service deletes, in the Log Databases:
- Processed Log Events, message bodies, and context properties older than their Message Type's Days to keep values. New Message Types get these values from DaysToKeepMessageEventsDefault, DaysToKeepMessageDataDefault, and DaysToKeepMessageContextDefault.
- Error events without data older than DaysToKeepErrorEventsWithoutData.
- Log Audit records older than DaysToKeepLogAudits.
- Unprocessed Log Events without a Message Type, and incomplete BizTalk message data, older than MissingEventsDays.
This parameter sets only how often the cleanup runs, not how long data is kept. Monitor Events are not part of this cleanup: the Monitoring Service purges them every hour, based on DaysToKeepMonitorEvents.
Choosing a Value
- Keep the default
3600000(1 hour) unless you have a reason to change it. - A longer interval lets expired data stay in the Log Database a little longer and makes each cleanup run delete more rows at once.
- A shorter interval spreads the deletes over more, smaller runs. Consider it when expired data piles up between runs on a busy system, and avoid very short intervals that keep the database busy with cleanup.