Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

MS SQL Server Integration

Microsoft SQL Server (MS SQL) is a powerful relational database management system developed by Microsoft. It supports a wide range of transaction processing, business intelligence, and analytics applications.

Monitoring MS SQL Server is essential to maintain high performance, availability, and data integrity. Xitoring provides an advanced monitoring solution for MS SQL Server, offering real-time visibility into essential performance metrics like query times, resource consumption, and active sessions.

Getting Access to MySQL Data

For gathering information and statistics from MySQL, you need to give Xitogent access to your database. As we do not recommend you give Xitogent your database root access, we are going to walk you through creating a user with the necessary privileges for Xitogent.

Supported platforms

The following guide is working on Linux and Windows servers but some details could be quite different based on the OS version.

Xitoring is currently supporting MS SQL Server 2012 and leter while the size_on_disk_bytes stat is only available in versions 2022 and later.

Create a user for Xitogent

First, execute the following command to create a login on your SQL server and set a password:

CREATE LOGIN xitoring WITH PASSWORD = '<PASSWORD>';

Then create a user for xitoring login:

CREATE USER xitoring FOR LOGIN xitoring;

Set the correct privileges

To enable the collection of metrics, Xitogent requires some privileges:

GRANT CONNECT ANY DATABASE to xitoring;
GRANT VIEW SERVER STATE to xitoring;
GRANT VIEW ANY DEFINITION to xitoring;
GRANT SELECT to xitoring;

Enable MS SQL Server Integration

There are no special requirements or software dependencies to enable this integration.

  1. To begin, run xitogent integrate and choose SQL Server from the list.

  2. Provide the IP address, port, username, and password for your MS SQL Server instance.

  3. Xitogent will test the connection and automatically complete the setup. Within moments, you'll start seeing real-time graphs and data on your Server page.

Setup Triggers for MS SQL Server Integration

With Xitoring, users can create Triggers for MS SQL Server to detect issues and respond quickly. Triggers can be set up based on a wide variety of parameters such as:

BufferCacheHitRatio
BatchRequestsPerSec
SqlCompilationsPerSec
TransactionsPerSec
UserConnections
LockTimeoutsPerSec
DeadlocksPerSec
LatchWaitsPerSec
PageLookupsPerSec
PageReadsPerSec
PageWritesPerSec
InsertsPerSec
UpdatesPerSec
DeletesPerSec
SelectsPerSec
TotalPerSec
MemoryUsage
+ many more
Last Updated: 4/17/25, 1:37 PM
Prev
Redis Integration
Next
Supervisor Integration