Skip to main content
SQL Planner

Configuration

How to create SQL Server monitoring Job in SQL Planner

Create a job-based SQL Server monitoring or health analysis job — permissions, connection, alert thresholds, notifications and dashboards.

2 min readUpdated

1. Prerequisites and security requirements

Before initiating a monitoring job, ensure that the environment meets the necessary security standards.

  • Administrative privileges: to capture deep-level diagnostics, the account used by SQL Planner must have DBA (Database Administrator) or VIEW SERVER STATE privileges.
  • Access to DMVs: high-level permissions are required because the tool executes complex T-SQL and queries Dynamic Management Views (DMVs). These views provide vital metadata about server health, memory pressure and query execution plans that standard user accounts cannot access.

2. Initiating a new monitoring job

The monitoring process in SQL Planner is job-based, allowing you to customize tracking for different environments (Production, UAT or Development).

  1. 1

    Access the wizard

    Navigate to the primary navigation menu and select “Create Monitoring or Health Analysis Job.”

  2. 2

    Define the instance

    Enter the server name or IP address of the SQL Server instance you wish to monitor.

  3. 3

    Authentication

    Select your connection method (Windows Authentication or SQL Server Authentication) and provide the DBA-level credentials from the prerequisites.

3. Configuring advanced alert thresholds

One of the most critical steps in the setup is defining what constitutes a Critical or Warning state. SQL Planner monitors three core hardware pillars:

A. CPU usage

Set a percentage limit (for example, 80% for 5 minutes) to identify sustained spikes. High CPU usage often indicates poorly optimized queries, missing indexes or excessive compilation.

B. Disk drive monitoring

Database growth can be unpredictable. By setting disk thresholds, you receive an alert long before a drive reaches 100% capacity — which would otherwise cause the SQL Server service to halt.

C. RAM (memory) pressure

SQL Server is designed to use a significant amount of memory. Monitoring RAM helps you distinguish between normal internal memory pressure (where SQL Server manages its cache) and external memory pressure (where other applications are starving the database of resources).

50+ critical and warning level alerts are available and can be configured.

Alerts for SQL Server

Browse the full list of critical and warning alerts SQL Planner can raise.

4. Automation: notification & job identification

Once the thresholds are set, define how the system communicates issues to your team.

  • Job naming convention: use a clear, descriptive name (for example, PROD_FINANCE_DB_MONITOR) so that when an alert arrives, you immediately know which server is affected.
  • Email integration: enter the primary email address for notifications. In an enterprise environment, this is typically a distribution list for the DBA team or a ticketing system’s intake email.

Configure Email Alert

Link email notifications with SQL Planner alerts.

5. Post-configuration: dashboards and analysis

After saving the job, SQL Planner begins its data collection cycle. There are two primary ways to interact with this data:

The Server Monitoring Dashboard

This is your bird’s-eye view. It displays a real-time status of all configured servers. If a server goes offline or a threshold is breached, the status indicator changes color — allowing immediate visual recognition of issues.

Health Analysis Reports

For deep-dive investigations, navigate to the Analyze section. Unlike the dashboard, which shows “right now,” Analysis provides:

  • Historical trends: see if memory pressure occurs every Monday morning or during month-end processing.
  • Live performance snapshots: view active sessions, blocked queries and current resource consumption in a single, unified report.

Summary checklist for administrators

  • Verify DBA permissions for the monitoring account.
  • Define custom CPU, Disk and RAM thresholds based on server hardware.
  • Test the notification email to ensure alerts aren’t caught in spam filters.
  • Review the Analyze section after 24 hours to establish a performance baseline.

SQL Server Monitoring product page

See live monitoring, alerts and estate health in SQL Planner.