> 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/instance-administration/system-functions/housekeeping.md). # Housekeeping Default settings for SonarQube Server’s database cleaner. This page is for SonarQube Server 2026.5. When you run a new analysis of your project, 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 Fixed issues and dependency risks that are more than 30 days old are deleted. * History at package/directory level is removed. These settings can be changed at **Administration** > **Configuration** > **General settings** > **Housekeeping**. Even though Housekeeping removes data from the database, you will still need to reclaim free space if your database is not configured to do this as part of normal maintenance. ## Dashboards This setting controls how long dashboard history is kept. You can change it at **Administration** > **Configuration** > **General settings** > **Housekeeping** > **Dashboards**. This retention period applies only to dashboard history. It does not change how long analysis data is kept. Data collection is enabled by default, with a default retention period of **365 days**, which is also the recommended value. The other options are **180 days**, **90 days**, or a **Custom** value. If you don’t want to retain any dashboard history, select **Custom** and set the retention period to 0 days. Data older than the retention period is automatically deleted. --- # 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/instance-administration/system-functions/housekeeping.md?ask=&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.