> 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/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-sql-s.md).

# SQL Server Profiler

[Command Centre - Connection Issues](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues.md) › SQL Server Profiler

Capture a **SQL Server Profiler** trace when Gallagher's developers need to investigate SQL traffic-related issues. The trace can be scoped to **Command Centre-specific** traffic or **SQL Server-wide** traffic, and is saved as a `.trc` file to return to Technical Support.

Only run this when requested by Gallagher developers or Technical Support. The trace is a diagnostic capture, not a routine task.

## Enabling the trace

1. Launch **SQL Server Profiler 18** on the machine where SQL Server is installed.
2. In the **File** menu, click **New Trace**.
3. On the **Connect to Server** dialogue, fill in the **Server Type**, **Server Name**, and **Authentication** fields, then click **Connect**.
4. On the **Trace Properties** page, populate the **Name** on the General tab. Leave all other values as default.
5. Click the **Event Selection** tab and check **'Show all events'** and **'Show all columns'**. Scroll down to the **Stored Procedure** section and check **SP:Completed** and **SP:Starting**.

   **To monitor Command Centre-specific traffic:** click **Column Filters**. On the **Edit Filters** dialogue, select **Database Name**, click **'Like'** in the box to the right, and type **`CCFTCentral`**. Click **OK**.

   **To monitor SQL Server-wide traffic:** skip the Column Filters step above.
6. Click **'Run'**.
7. Leave the trace running. Open **Command Centre** and **replicate** the issue.
8. Once the issue has been replicated, **stop** the trace and **save** the trace file via **File menu > Save** from SQL Server Profiler 18.
9. Send the generated file (in **`.trc`** format) to Technical Support.

![SQL Server Profiler trace setup](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-f15c881e87fc2b2aecf326e4d12613c823451d96%2FSECHUB-CCS-CONN-SQL-PROFILER-01.png?alt=media)

![SQL Server Profiler column filter](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-39e93fbd5484912b89c23389b6547ed1ad777509%2FSECHUB-CCS-CONN-SQL-PROFILER-02.png?alt=media)

***

🔗 **Related**

* [Command Centre Databases (SQL)](broken://pages/cCfAltV0RyZ60G9YuhuO). The CCFTCentral / CCFTEvent databases this trace targets.


---

# 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/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-sql-s.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.