> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/10.5/instance-administration/housekeeping.md).

# Housekeeping

Default settings for the SonarQube Server 10.5 database cleaner.

{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 10.5 documentation. For a list of all 10.5 pages, see the [SonarQube Server 10.5 page index](https://3691828591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feu7dHWcqP9Cr3eUAzwWg%2Fuploads%2FjUvEoDEUUE0rAURT5wZJ%2Fsonarqube-server-10.5-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 10.5 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}

When you run a new analysis of your project or its branches or pull requests (PRs), some data that was previously available is cleaned out of the database. For example, the source code of the previous analysis, measures at directory and file levels, and so on are automatically removed at the end of a new analysis. Additionally, some old analysis snapshots, PR analyses, and branches are also removed.

Why? While it’s useful to analyze a project frequently to see how its quality evolves, it is also useful to be able to see the trends over weeks, months, and years; when you look back in time, you don’t really need the same level of detail as you do for the project’s current state. To save space and improve overall performance, the Database Cleaner deletes some rows in the database. Here is the default configuration:

* Audit logs (available starting in [Enterprise Edition](https://www.sonarsource.com/plans-and-pricing/enterprise/)) are deleted monthly.
* For each project:
  * Only one snapshot per day is kept after 1 day. Snapshots marked by an event are not deleted.
  * Only one snapshot per week is kept after 1 month. Snapshots marked by an event are not deleted.
  * Only one snapshot per month is kept after 1 year. Snapshots marked by an event are not deleted.
  * Only snapshots with version events are kept after 2 years. Snapshots without events or with only other event types are deleted.
  * *All snapshots* older than 5 years are deleted, including snapshots marked by an event.
* All Closed issues more than 30 days old are deleted (this concerns only Fixed issues).
* History at package/directory level is removed.

These settings can be changed at **Administration** > **General** > **Housekeeping**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/10.5/instance-administration/housekeeping.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.