> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/microsoft-sql-server.md).
# Microsoft SQL Server
### How to Configure Remote Monitoring of Microsoft SQL Server
1\. In the IT-Conductor main menu, navigate to **Dashboards > Administrator.**
2\. In the Administrator dashboard, locate the Microsoft SQL Servers panel and click the 
to start adding a system to be monitored.
3\. In the Create New Microsoft SQL Server wizard, fill out all the necessary information. Once completed, click to add the system.
> **Note** Please specify the MSSQL Server name in the DBA Connection Property field, use \:\ notation with the port typically set to 1433.
4\. A pop-up message will confirm that the Microsoft SQL has been added successfully. Click **OK** to dismiss and proceed to configure the Microsoft SQL user to be used for monitoring.
5\. Provide the account information in the wizard, then click to complete the configuration.
> **Note** Please take note of the [Microsoft SQL Monitoring](#it-conductor-microsoft-sql-server-monitoring-configuration-requirements) configuration requirements
6\. A pop-up message will confirm that the account has been created successfully. Click **OK** to complete the process.
7\. The newly added system will appear in the Microsoft SQL Servers panel
> **Note** It may take a few minutes to change the status to "In Progress," refresh the panel if needed. If there are issues with the configuration, such as wrong connection parameters or an invalid account etc. the status will stay "Ready", troubleshoot by displaying the log. Click  for the new record or click object icon and select Log from the menu popup.
8\. The SQL Server will show up in the service grid within 5-15 minutes
### IT-Conductor Microsoft SQL Server Monitoring Configuration Requirements
The account used to monitor the SQL Server instance should have the following permissions:
* Member of the "sysadmin" role
If you are unable to grant "sysadmin" permissions to the account, please grant the following permissions:
* Member of the "db\_datareader" role on the msdb system database
* Member of "SQLAgentReader" role on the msdb system database
* **VIEW ANY DEFINITION** server permission
* **ALTER TRACE** server permission (if you want to enable trace data)
* **VIEW SERVER STATE** and **VIEW DATABASE STATE** database permissions on all databases
* Member of the **db\_owner** role on the "tempdb" database
* **EXECUTE** on xp\_readerrorlog
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/start-here/systems-setup/microsoft-sql-server.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.