> 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-hosting-the-db-on-sql-cluste.md). # Database hosting [Command Centre Databases (SQL)](broken://pages/cCfAltV0RyZ60G9YuhuO) › Hosting the DB on SQL Clustered or Remote server ## This page answers * Can the Command Centre databases be hosted on a separate SQL server? * Should you use a standalone or clustered SQL server? * How does Command Centre find databases on a remote server? The Command Centre databases can be hosted on a separate SQL server, either standalone or clustered, as the customer chooses. For the full install procedure against a remote SQL server, see [Databases - Setting up Command Centre with remote SQL](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-setting-up-command-centre-wi.md). *** ## Standalone vs clustered Gallagher recommends **standalone with dedicated resources**, sized to the throughput of the system. This means not placing the Command Centre server or the SQL server on a system with dynamic resources that change as demand increases (as is common in virtual systems). > **Note:** If the SQL is in a cluster environment, latency must be at a minimum, **preferably less than 5ms**. > **Note:** Command Centre relies heavily on a solid connection to the SQL database. High latency can significantly impair Command Centre's performance or even make it unusable. *** ## Locating the databases (registry) Moving the Gallagher databases to a remote system requires Command Centre to know where to find them. This is set in the Gallagher Registry. ![Gallagher Registry entries for the database server machine location](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ce59a3c396bee9919b5249167074ab37773ba734%2FSECHUB-CCS-SQL-CLUSTERED-registry-db-location.jpg?alt=media) These are the entries to alter so Command Centre can connect to the relocated databases. > **Important:** Command Centre does not support renaming the Gallagher database names. By default the Gallagher databases are at `C:\Program Files (x86)\Gallagher\Command Centre\Data` on the server. > **Remember:** The Command Centre services must be stopped when moving the databases. *** 🔗 **Related** * [Databases - Setting up Command Centre with remote SQL](/knowledge-hub/products/cc-software/configure/databases-an-overview-of-command-centr/databases-setting-up-command-centre-wi.md). The full install procedure against a remote SQL server. --- # 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-hosting-the-db-on-sql-cluste.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.