SQL Server性能监控工具

Install

Windows Authentication:

PerformanceMonitorInstaller.exe YourServerName

SQL Authentication:

PerformanceMonitorInstaller.exe YourServerName sa YourPassword

Entra ID (MFA) Authentication:

PerformanceMonitorInstaller.exe YourServerName --entra user@domain.com

Clean reinstall (drops existing database and all collected data):

PerformanceMonitorInstaller.exe YourServerName --reinstall
PerformanceMonitorInstaller.exe YourServerName sa YourPassword --reinstall

Custom data/log file locations (applied only when the database is first created):

PerformanceMonitorInstaller.exe YourServerName --data-path D:\SQLData --log-path E:\SQLLogs

Uninstall (removes database, Agent jobs, and XE sessions):

PerformanceMonitorInstaller.exe YourServerName --uninstall
PerformanceMonitorInstaller.exe YourServerName sa YourPassword --uninstall

The installer automatically tests the connection, checks the SQL Server version (2016+ required), executes SQL scripts, downloads community dependencies, creates SQL Agent jobs, and runs initial data collection. You can also install directly from the Dashboard's Add Server dialog.

Air-gapped environments? Place pre-downloaded community scripts (sp_WhoIsActive.sql, DarlingData.sql, Install-All-Scripts.sql) in a community/ directory next to the installer. The installer uses local files when present and falls back to GitHub downloads otherwise.

CLI Installer Options

Custom file locations: --data-path / --log-path set where SQL Server places the PerformanceMonitor data and log files. They take effect only when the database is first created — if the database already exists they are ignored. Either flag may be supplied independently; an omitted one falls back to the instance default (SERVERPROPERTY('InstanceDefaultDataPath') / InstanceDefaultLogPath). The directory is a path on the SQL Server host and must already exist, with the SQL Server service account holding write permission. Both --data-path D:\SQLData and --data-path=D:\SQLData forms are accepted; quote paths containing spaces. Not applicable to Azure SQL Managed Instance, which always uses its managed file layout.

Environment variable: Set PM_SQL_PASSWORD to avoid passing the password on the command line.

Post-Installation

1. Ensure SQL Server Agent is running — the collection job executes every minute
2. Verify installation:

SELECT * FROM PerformanceMonitor.config.current_version;

SELECT TOP (20) *
FROM PerformanceMonitor.config.collection_log
ORDER BY collection_time DESC;

1. Install the Dashboard. Download PerformanceMonitorDashboard-win-Setup.exe (requires .NET 10 Desktop Runtime). Setup.exe installs to %LocalAppData%\PerformanceMonitorDashboard, adds Start Menu and Desktop shortcuts, registers the app under Apps & Features, and wires up auto-update. Launch from the Start Menu, add your server, enter credentials, and data appears immediately.

What Gets Installed

• PerformanceMonitor database with collection tables and reporting views
• 33 collector stored procedures for gathering metrics (including SQL Agent job monitoring)
• Configurable collection — query text and execution plan capture can be disabled per-collector via config.collection_schedule (collect_query, collect_plan columns) for sensitive or high-volume environments
• Delta framework for calculating per-second rates from cumulative DMVs
• Community dependencies: sp_WhoIsActive, sp_HealthParser, sp_HumanEventsBlockViewer, sp_BlitzLock
• SQL Agent jobs: Collection (every 1 minute), Data Retention (daily at 2:00 AM), and Hung Job Monitor (collection job watchdog, every 5 minutes)
• Version tracking in config.installation_history

Setup

1. Enable the MCP server in Settings (checkbox + port, default 5151) - The port must be between 1024 and 65535. Ports 0–1023 are well-known privileged ports reserved by the operating system. - On save, the app checks whether the chosen port is already in use and warns you if there is a conflict. - On startup, the app verifies the port is available before starting the MCP server. 2. Register with Claude Code:

claude mcp add --transport http --scope user sql-monitor http://localhost:5151/

3. Open a new Claude Code session and ask questions like: - "What servers are being monitored?" - "What are the top wait types on my server?" - "Are there any blocking or deadlock issues?" - "Show me CPU utilization for the last 4 hours" - "What are the most expensive queries by CPU?"

Building from Source

All projects target .NET 10.0.

```

CLI Installer (self-contained)

dotnet publish Installer/PerformanceMonitorInstaller.csproj -c Release ```

---

Quick Start — Lite Edition

1. Download PerformanceMonitorLite-win-Setup.exe (requires .NET 10 Desktop Runtime)
2. Run the installer — it installs to %LocalAppData%\PerformanceMonitorLite, adds Start Menu and Desktop shortcuts, and registers the app under Apps & Features so it shows up in Windows search and can be uninstalled normally. Auto-update is wired in.
3. Launch from the Start Menu or Desktop shortcut.
4. Click + Add Server, enter connection details, test, save.
5. Double-click the server in the sidebar to connect.

Data starts flowing within 1–5 minutes. That's it. No installation on your server, no Agent jobs, no sysadmin required.

Upgrading from zip? Click Import Settings then Import Data in the sidebar and point both at your old Lite folder. Settings imports server connections, alert thresholds, SMTP config, and schedules. Data imports historical DuckDB + Parquet archives. Auto-update users (installed via Setup.exe) get updates automatically — no manual import needed.

Always On AG? Enable ReadOnlyIntent in the connection settings to route Lite's monitoring queries to a readable secondary, keeping the primary clear. Enable MultiSubnetFailover for multi-subnet failover scenarios.

Quick Start — Full Edition

More Screenshots

Lite Configuration

When a second Windows user on the same machine launches Lite, they see the shared servers.json immediately. SQL Auth and Entra MFA passwords are scoped to each user's own Credential Manager, so they'll be prompted once per server; Windows Auth works without any prompt.

---

AWS RDS Parameter Group Configuration

sp_configure is not available on AWS RDS for SQL Server. Features that depend on server-level configuration must be set through AWS RDS Parameter Groups instead.

Blocked process threshold — Enables blocked-process-report collection (the richer XE-sourced blocking detail). Without it the blocked-process-report XE will not fire on RDS, but blocking is still captured by the always-on dmv_blocking_snapshot collector, so the blocking grid and block-chain viewer stay populated regardless. Set the threshold for the fuller report-sourced detail.

1. Open the AWS RDS Console and navigate to Parameter groups 2. Create a new parameter group (or modify the one attached to your instance): - Family: sqlserver-ee-16.0 (or your edition/version) - Type: DB Parameter Group 3. Search for blocked process threshold (s) and set it to 5 (seconds) 4. Apply the parameter group to your RDS instance (may require a reboot if the parameter is static) 5. Verify it took effect:

   SELECT
       c.name,
       c.value_in_use
   FROM sys.configurations AS c
   WHERE c.name = N'blocked process threshold (s)';
   

Deadlocks — No parameter group configuration is required. The SQL Server deadlock monitor runs automatically on all platforms, and the xml_deadlock_report Extended Event fires without any threshold setting.

Azure SQL Database — The blocked process threshold is fixed at 20 seconds and cannot be changed. The blocked_process_report event fires automatically when blocking exceeds this duration.

---

MCP Server (LLM Integration)

Both editions include an embedded Model Context Protocol server that exposes monitoring data to LLM clients like Claude Code and Cursor.

Third-Party Components

Edition Comparison

---

Troubleshooting