Skip to main content
SQL Planner

Analytics & Diagnosing

Diagnosing High CPU and Memory Consumption

Troubleshoot server slowdowns with SQL Planner — dashboard overview, process-level CPU/memory metrics, time-based analysis and a practical remediation workflow.

Updated

Understanding and troubleshooting resource consumption is a critical skill for DBAs and IT professionals. This guide walks through a real-world scenario where a server experiences performance degradation due to excessive CPU or memory usage during specific time periods. When management, developers or customers report that “something is slowing down on the server,” investigation starts with systematic analysis using SQL Planner’s monitoring tools.

The Server Monitoring Dashboard

Centralized visibility

SQL Planner’s server monitoring feature provides a comprehensive dashboard that aggregates performance metrics across all monitored servers. This centralized view helps you quickly identify which servers are experiencing issues without manually checking each system.

Real-time alerts

The dashboard displays critical alerts and status indicators that immediately draw attention to problematic servers. When a server goes offline or experiences resource exhaustion, visual cues make the issue hard to miss during routine monitoring.

The monitoring interface presents a clear overview of your server infrastructure. In an example scenario, three servers appear in the dashboard — a domain controller, a general-purpose server and a third that remains powered down — showing how the system can track servers regardless of operational state.

Individual server health dashboard

Identifying the problem server

  • Critical status detection — the dashboard immediately flags servers with offline status or resource exhaustion.
  • Drill-down capability — click any server to investigate detailed performance metrics and historical data.
  • Time range selection — choose specific windows (24 hours, custom ranges) to focus your investigation.

Upon opening Server Overview, the system may immediately reveal a server with a critical offline status. That visual alert is the starting point. The main focus then becomes identifying which process consumed the highest CPU during the reported degradation period.

Individual server health — alerts, disk usage and CPU / memory / network / disk IO trends.

Analyzing process-level resource consumption

Below the high-level resource graphs, the monitoring dashboard provides analytical reports that break down resource consumption by individual processes.

Service outages and process-level CPU / memory / network analysis for the selected server.
MetricDescription
Average CPU UsageMean CPU consumption over the selected period — helps identify processes that consistently tax the processor.
Maximum CPU UsagePeak CPU moments — exposes processes that cause sudden spikes and temporary slowdowns.
Memory ConsumptionRAM usage patterns — identifies processes that allocate excessive memory or leak over time.
Network TransferData transfer volumes — highlights processes that generate heavy network traffic.

Investigating high-CPU processes

Viewing process details

When you identify a process consuming excessive CPU, click “View Details” to open an expanded analysis interface. This view breaks consumption down at finer granularity — typically minute-by-minute throughout the selected period.

Graphical representation

Visual graphs display CPU and memory trends over time, making it easy to spot patterns and correlate consumption with reported slowdowns. Spikes in the CPU graph that align with user-reported times create a clear correlation between process activity and performance degradation.

Understanding memory consumption patterns

  • Dedicated memory allocation — SQL Server processes typically maintain constant memory usage as they allocate dedicated resources for performance.
  • Stable baseline patterns — expected memory consumption shows consistent levels with minimal fluctuation.
  • Abnormal memory growth — memory leaks or inefficient processes show steadily increasing usage that can exhaust available RAM.

Time-based analysis for root cause detection

Analyzing resource consumption at specific date and minute levels is invaluable for root cause detection.

  • 23:08 – initial spike: process detected at 12% average CPU with maximum reaching 12%, memory at 5% overall.
  • Correlation window: match CPU spikes with user-reported slowdown times to confirm causation.
  • Pattern recognition: identify recurring patterns across multiple days to determine if the issue is periodic (scheduled task) or random.

Process-wise resource consumption insights

  • Comprehensive visibility — view all running processes with CPU, memory and network metrics in one interface.
  • Historical comparison — compare current consumption against historical baselines to spot abnormal behavior.
  • Impact assessment — understand how individual processes affect overall server performance and user experience.

For example, discovering that a backup utility — rather than SQL Server itself — causes CPU spikes means you can adjust backup schedules instead of reconfiguring SQL Server.

Practical applications in daily operations

Troubleshooting workflow

  1. 1

    Receive the complaint

    A user reports server slowdowns.

  2. 2

    Open the dashboard

    Access the monitoring dashboard and identify the affected server.

  3. 3

    Examine process metrics

    Review process-level metrics for the time period in question.

  4. 4

    Find top consumers

    Identify the highest-consuming processes using sorting and filtering.

  5. 5

    Drill into details

    Analyze minute-by-minute usage patterns.

  6. 6

    Correlate timing

    Match findings with user-reported issue times.

  7. 7

    Document and remediate

    Record the root cause and implement remediation.

Proactive monitoring benefits

  • Detect resource issues before users experience problems.
  • Establish performance baselines for comparison.
  • Identify trends that indicate future capacity requirements.
  • Validate the effectiveness of performance optimizations.

Key takeaways and best practices

  1. Start with the dashboard overview — identify which servers show critical status or resource exhaustion.
  2. Use time-based analysis — correlate user-reported slowdown times with minute-level metrics.
  3. Examine both CPU and memory — issues can stem from either or both.
  4. Understand normal patterns — recognize that SQL Server’s dedicated memory allocation can be expected behavior.
  5. Document findings — record root cause analyses and remediation steps to build institutional knowledge.

Windows Server Alerting

Configure thresholds and notifications for host-level issues.

Windows Server Monitoring

Product overview for CPU, memory, services and event logs.