> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-database-information.md).

# Archiving database information

Understand SQL Express database limits and recovery options when capacity is reached.

### What happes if a site does not archive?

A site that does not archive can experience:

* Alarm messages in the Alarms viewer (database-full warnings).
* The Events window in the Configuration Client no longer displaying events.

Both happen because the database has reached or exceeded its maximum size and SQL will no longer store data.

***

### SQL Express size limits

What is the maximum database size for each SQL Express version?

Command Centre installs the **Express** edition of SQL by default. The maximum database size for SQL Express varies by version:

| SQL Express version | Maximum database size |
| ------------------- | --------------------- |
| 2005                | 4 GB                  |
| 2008                | 4 GB                  |
| 2008 R2             | 10 GB                 |
| 2012                | 10 GB                 |
| 2016                | 10 GB                 |
| 2017                | 10 GB                 |
| 2019                | 10 GB                 |

For most sites this is enough for many years before space becomes an issue, but the limit will eventually be reached if archiving is not implemented. As the database approaches the limit, Command Centre raises alarms warning the administrator. Act on these as soon as possible.

***

### What options are available once the database is full?

Once the database is beyond the SQL Express limit, only two options remain:

1. **Upgrade to full SQL:** effectively unlimited space (bounded by hard drive and machine specs).
2. **Replace `CCFTCentral` with a blank one:** losing all past activity history.

If an old system has a 4 GB SQL limit, you could upgrade to SQL Express 2008 R2 or later, but most Command Centre systems now run SQL versions with the 10 GB limit.

> **Blank-database media:** up to version 8.20, the install media carries a blank set of databases you can restore from. From 8.20 onward, use scripts to create a blank database.

***

🔗 **Related**

* [Archiving - An Overview](/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-an-overview.md). Why every site should archive and the 90-day default.
* [Databases - Sizes and Examples](/knowledge-hub/products/cc-software/reference/databases-sizes-and-examples.md). Event sizing and how often to archive.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-database-information.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.