> 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/databases-an-overview-of-command-centr/databases-structure.md).

# Database structure

### Which two databases does Command Centre maintain, and what does each hold?

Gallagher Command Centre maintains two databases:

| Database      | Contains                                                                          |
| ------------- | --------------------------------------------------------------------------------- |
| `CCFTCentral` | Site configuration: doors, cardholders, schedules, and all other FT item entities |
| `CCFTEvent`   | All alarms and events generated by the system                                     |

### Where do the database files live by default?

By default both live on the Command Centre server here:

```
C:\Program Files (x86)\Gallagher\Command Centre\Data
```

Each database has a data file and a corresponding SQL transaction log file:

* `CCFTCentral.mdf`: the configuration database
* `CCFTCentral_log.ldf`: its SQL log file
* `CCFTEvents.mdf`: the events database
* `CCFTEvents_log.ldf`: its SQL log file

> **Important:** Command Centre does not support renaming the Gallagher database names.

![Command Centre database structure schema diagram showing the tables and relationships within CCFTCentral and CCFTEvent](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6015ef511c59d396ed8cca6501bc914f5bc06825%2FSECHUB-CCS-SQL-STRUCTURE-schema-diagram.png?alt=media)

***

🔗 **Related**

* [Databases - An Overview of Command Centre and SQL](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr.md). SQL instances, service accounts, and remote SQL.
* [Databases - Sizes and Examples](/knowledge-hub/products/cc-software/reference/databases-sizes-and-examples.md). How large each database grows.


---

# 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/databases-an-overview-of-command-centr/databases-structure.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.