Diagnose SQL Server Performance Problems

Rapidly discover and fix performance problems

Stop Searching and Start Fixing

Your mission-critical applications depend on data. When that data is not available, the applications and processes slow down or stop working altogether. When that happens, you're on the hot seat to diagnose the problem, find the root cause, fix it, and get the system running smoothly again.

The ability to quickly diagnose problems requires visibility into your entire stack. Without the right information, you could spend hours working on an issue and still not fix the problem.


Troubleshooting SQL Server Performance Problems

The first step in effective troubleshooting is to separate the urgent from the non-urgent problems. Then, you need to determine the nature of the problem, which could involve:

  • Resource Contention
  • Storage Performance
  • Virtualization Issues
  • Network Latency
  • Memory Pressure
  • Bad Code
  • Deadlocks
  • Blocking
  • Inefficient Query Plans

Expert Tips for Diagnosing SQL Server Performance


Top 5 Most Common SQL Server Performance Problems

Get the Tips

Troubleshooting SQL Server CPU Performance Issues

Get the Tips

Beware of These Knee-Jerk Wait Stats

Get the Tips

Analyzing I/O Performance Bottlenecks for SQL Server

Get the Tips

The Two Phases of Troubleshooting SQL Server Performance Issues

Sometimes, a performance issue is straightforward and easy to fix. Other times, the root cause is buried deep, and it takes some investigative work to discover the problem.

In these cases, troubleshooting is broken into two phases:

Phase 1: Gather All the Facts

With SentryOne, you will have all the information you need to diagnose the problem, including historical data. In some cases, you’ll know what action to take based on the first event you see in the Health Overview. Other situations will require more analysis, but you won’t need to leave the SentryOne client to look for more information.

Without SentryOne, gathering data can take hours, not to mention the time you'll need to diagnose the problem. Worse, you might discover that you still can’t explain the problem because you don’t have a historical view of the data.

Phase 2: Analyze the Problem

Once you have all the information required to identify the root cause, you can solve the problem, then optimize your system to prevent the problem from recurring.

Analysis can be straightforward and quick, if you have all the information required. But making a diagnosis without all the facts is a gamble—for your career and your company's ability to operate—that you don't want to take.