> 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-attaching-blank-ones-to-8-20.md).

# Steps for blank database attachment

Attach compatible blank databases and regenerate the thumbprint when required.

#### Can you reuse blank databases from an earlier version's install media?

If you have install media from a previous Command Centre version, you can attach blank databases from that version, provided it is a **valid upgrade path**. For 8.20, you can use blank databases from 7.80 or above install media.

#### When do you need to regenerate the thumbprint?

* If you are replacing `CCFTCentral` (or both databases), you still need to **regenerate the thumbprint by applying the recovery code**.
* If you are replacing `CCFTEvent` only, there is **no** need to regenerate the thumbprint.

***

🔗 **Related**

* [Databases - Creating blank ones using scripts (8.20 and above)](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-creating-blank-ones-using-sc.md). Creating blank databases from scratch, and the thumbprint procedure.
* [Databases - Detaching and Reattaching](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-detaching-and-reattaching.md). Attaching databases to the instance.


---

# 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-attaching-blank-ones-to-8-20.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.