Identify Bottlenecks


Applies To: SQL Server 2016

Simultaneous access to shared resources causes bottlenecks. In general, bottlenecks are present in every software system and are inevitable. However, excessive demands on shared resources cause poor response time and must be identified and tuned.

Causes of bottlenecks include:

  • Insufficient resources, requiring additional or upgraded components.

  • Resources of the same type among which workloads are not distributed evenly; for example, one disk is being monopolized.

  • Malfunctioning resources.

  • Incorrectly configured resources.

Excessive durations for various events are indicators of bottlenecks that can be tuned.

For example:

  • Some other component may prevent the load from reaching this component thereby increasing the time to complete the load.

  • Client requests may take longer due to network congestion.

Following are five key areas to monitor when tracking server performance to identify bottlenecks.

Possible bottleneck areaEffects on the server
Memory usageInsufficient memory allocated or available to Microsoft SQL Server degrades performance. Data must be read from the disk rather than directly from the data cache. Microsoft Windows operating systems perform excessive paging by swapping data to and from the disk as the pages are needed.
CPU utilizationA chronically high CPU utilization rate may indicate that Transact-SQL queries need to be tuned or that a CPU upgrade is needed.
Disk input/output (I/O)Transact-SQL queries can be tuned to reduce unnecessary I/O; for example, by employing indexes.
User connectionsToo many users may be accessing the server simultaneously causing performance degradation.
Blocking locksIncorrectly designed applications can cause locks and hamper concurrency, thus causing longer response times and lower transaction throughput rates.

Monitor CPU Usage
Monitor Disk Usage
Monitor Memory Usage
SQL Server, General Statistics Object
SQL Server, Locks Object

Community Additions