> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/install-central-manager-multi-store/set-up-the-head-office/installation-cm-connect-to-central-db.md).

# Connect to SQL Server and the Central database and force install tables

This topic describes how to connect to SQL Server and the Central database in Central Administrator, and how to update the tables in the Central database using the Force Install Tables function.

{% hint style="success" %}
You can run Force Install Tables as an executable in **Command Prompt** or **PowerShell**. This allows you to update or repair the Central database without opening Central Administrator or Central Manager. Refer to [**Run Force Install Tables as an executable**](https://docs.rmhpos.com/installation/other-procedures/force-install-tables-executable.md) for more information.
{% endhint %}

1. Open **Central Administrator**. The shortcut should be available on your desktop.
2. Click **Connect**.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-1744118a81962de6b9895d01e012361c5a91de1b%2Fcentral-administrator.png?alt=media" alt=""></div>

3. In the **Server** field, select the host name of the computer where you installed SQL server and the name of the SQL Server instance.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-f4bd2a966db041aee0298c39e5f30d5f4343acf7%2Fcentral-administrator-connect-filled.png?alt=media" alt=""></div>

4. Under **Connection information**, select **Use SQL Server Authentication**.
5. Enter the **User name** and **Password** for the system account.
6. From **Database**, select the Central database.
7. Click **Connect**. You will notice that the functions in the Database menu are now accessible.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-d9989699948674af8a843c5e4a71af8ca9002ed7%2Fcentral-administator-database-menu.png?alt=media" alt=""></div>

8. In the **Database** menu, click **Force Install Tables**.

{% hint style="info" %}
Starting with release 3.11.14, the Force Install Tables function no longer creates the SYNCGUID column in the RMH or third-party app tables. The Prepare Database function will create the SYNCGUID column in the RMH table, but it will no longer create it in third party app tables.
{% endhint %}

9. Click **Yes** to continue.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-2ac289c3b3d6ee670e2ed934529194fb25e9934a%2Fcentral-administrator-force-install-tables.png?alt=media" alt=""></div>

10. Wait while **Central Administrator** executes the SQL scripts to create RMH custom tables in the Central database. This may take a few minutes.
11. Click **OK** to close the confirmation dialog.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-9c0e3f65880cda54f8c77c6e48bac1d1170154e7%2Fcentral-administrator-force-install-tables-confirm.png?alt=media" alt=""></div>


---

# 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.rmhpos.com/installation/install-central-manager-multi-store/set-up-the-head-office/installation-cm-connect-to-central-db.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.
