Does the integration support SQL Server on Linux?

Yes. While MSSQL is traditionally on Windows, Xitogent supports SQL Server on both Windows and Linux environments.

Will this integration affect SQL Server performance?

No. Xitogent uses lightweight DMV queries (Dynamic Management Views) which have negligible impact on SQL Server performance.

Can I monitor multiple instances?

Yes. Xitogent can monitor multiple SQL Server instances (named instances) on the same server.

Can I monitor Azure SQL Database?

The agent-based integration monitors self-hosted SQL Server. For Azure SQL Database, use Xitoring's uptime monitoring for endpoint health.

What SQL Server versions are supported?

Xitoring supports SQL Server 2016 and later, including SQL Server 2022 and Express editions.

How often are metrics collected?

Metrics are collected at 1-minute intervals by default. This can be adjusted through the Xitoring dashboard or CLI.

Databases

MSSQL Monitoring

Monitor Microsoft SQL Server query performance, wait statistics, buffer cache, and transaction log health in real time with zero configuration.

Start Free Trial View Docs

Why monitor MSSQL?

Microsoft SQL Server powers enterprise applications, data warehouses, and business intelligence platforms worldwide. Monitoring MSSQL is essential to optimize query execution plans, track wait statistics, manage buffer cache efficiency, and detect deadlocks. Xitoring's MSSQL integration provides comprehensive visibility into your SQL Server instances.

Auto-discovery via Xitogent — no manual configuration required

Real-time query performance and batch request metrics

Buffer cache hit ratio and page life expectancy

Wait statistics and deadlock detection

Transaction log usage and growth tracking

Index usage and missing index recommendations

Supports Windows Server environments natively

1-minute metric collection intervals

Metrics

What we monitor

Batch Requests/sec

Number of SQL batch requests received per second.

Buffer Cache Hit Ratio

Percentage of page reads satisfied from buffer pool vs physical disk reads.

Page Life Expectancy

Average time (seconds) a page stays in the buffer pool — lower values indicate memory pressure.

Wait Statistics

Top wait types and durations indicating resource bottlenecks.

Deadlocks/sec

Number of lock requests that resulted in deadlocks.

Transaction Log Usage

Percentage of transaction log space used per database.

User Connections

Number of active user connections to the SQL Server instance.

Compilations/sec

Number of SQL compilations and recompilations per second.

Lock Waits/sec

Number of lock requests that required the caller to wait.

Index Fragmentation

Fragmentation level of indexes across databases.

CPU Usage

SQL Server process CPU utilization vs total system CPU.

Database Size

Data and log file sizes for each database.

Triggers & Alerts

Configurable alert triggers

Set up custom triggers in your dashboard to get notified the moment MSSQL metrics cross your defined thresholds.

MSSQL monitoring trigger configuration dashboard

Buffer Cache Hit Ratio

critical

Fires when cache hit ratio drops below threshold, indicating insufficient memory for workload.

Page Life Expectancy

warning

Triggers when PLE drops below threshold, meaning pages are being flushed too quickly from memory.

Deadlocks

critical

Alerts when deadlock rate exceeds threshold, indicating lock contention in application queries.

Transaction Log Usage

critical

Fires when transaction log usage exceeds threshold, risking write failures.

User Connections

warning

Triggers when connection count approaches limits, risking connection refused errors.

Wait Statistics

warning

Alerts when specific wait types spike, indicating resource bottlenecks (CPU, I/O, memory, locks).

Importance of MSSQL Monitoring

SQL Server runs mission-critical enterprise workloads — from ERP systems and financial databases to e-commerce platforms. Without monitoring, buffer pressure, deadlocks, and transaction log bloat can cause outages and data corruption.

Detect memory pressure through buffer cache and PLE metrics
Monitor wait statistics to identify the root cause of slowdowns
Track deadlocks to fix application-level locking issues
Ensure transaction log space for uninterrupted write operations
Optimize index usage to maintain query performance over time

MSSQL monitoring dashboard with query performance and buffer cache metrics

SQL Server deadlock detection and index usage analytics

Why Choose Xitoring

Xitoring delivers enterprise-grade SQL Server monitoring with zero-config setup. Our lightweight agent auto-discovers your MSSQL instances, starts collecting metrics in under 60 seconds, and integrates with your existing notification channels.

Native Windows Server support with easy installer
15+ global monitoring nodes for low-latency checks
Unified dashboard for servers, databases, and uptime
Flexible alerting via Slack, PagerDuty, Telegram & more
Historical data retention for capacity planning & audits

Xitoring MSSQL monitoring overview on Windows Server

Alert notification and escalation configuration

Before you start

Prerequisites for MSSQL

Make sure you've got these in place — most installs are a 60-second job once they are.

Microsoft SQL Server 2012 or later (2022+ for the size_on_disk_bytes metric)
A SQL login with CONNECT ANY DATABASE, VIEW SERVER STATE, VIEW ANY DEFINITION, and SELECT grants
TCP/IP enabled on the instance, with the port reachable from Xitogent

Setup Guide

Get started in minutes

Install Xitogent on your Windows server

Download and install the Xitogent agent on your Windows Server hosting SQL Server.

# Download from https://xitoring.com/xitogent
# Run the installer as Administrator

Configure SQL Server access

Create a dedicated login for monitoring with minimal privileges:

CREATE LOGIN xitoring WITH PASSWORD = 'your_password';
CREATE USER xitoring FOR LOGIN xitoring;
GRANT CONNECT ANY DATABASE TO xitoring;
GRANT VIEW SERVER STATE TO xitoring;
GRANT VIEW ANY DEFINITION TO xitoring;
GRANT SELECT TO xitoring;

Enable the MSSQL integration

Use the Xitoring dashboard or CLI to enable the MSSQL integration.

xitogent integrate

Configure alert thresholds (optional)

Set custom thresholds for buffer cache hit ratio, page life expectancy, or deadlock count to get notified when something needs attention.

Verify it's working

Run this command on the server to confirm Xitogent picked up the integration. Fresh metrics will start streaming to your dashboard within ~30 seconds.

sudo xitogent status

Compare

Considering alternatives?

See how Xitoring stacks up against the alternatives for MSSQL monitoring — flat pricing, deeper integrations, and one agent that covers your whole stack.