Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 2.99 KB

isolate-performance-problems.md

File metadata and controls

51 lines (36 loc) · 2.99 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords monikerRange
Isolate Performance Problems
Use SQL Server Profiler and System Monitor to monitor and troubleshoot Transact-SQL, application-related problems, hardware, and system-related problems.
MikeRayMSFT
mikeray
03/14/2017
sql
performance
conceptual
isolating performance problems [SQL Server]
monitoring performance [SQL Server], isolating problems
database monitoring [SQL Server], isolating problems
tuning databases [SQL Server], isolating problems
monitoring server performance [SQL Server], isolating problems
database performance [SQL Server], isolating problems
server performance [SQL Server], isolating problems
=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current

Isolate Performance Problems

[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance] It is often more effective to use several [!INCLUDEmsCoName] [!INCLUDEssNoVersion] or Microsoft Windows tools together to isolate database performance problems than to use one tool at a time. For example, the graphical Execution Plan feature, also called Showplan, helps you quickly recognize deadlocks in a single query. However, you can recognize some other performance problems more easily if you use the monitoring features of [!INCLUDEssNoVersion] and Windows together.

[!INCLUDEssSqlProfiler] can be used to monitor and troubleshoot Transact-SQL and application-related problems. System Monitor can be used to monitor hardware and other system-related problems.

You can monitor the following areas to troubleshoot problems:

  • [!INCLUDEssNoVersion] stored procedures or batches of [!INCLUDEtsql] statements submitted by user applications.

  • User activity, such as blocking locks or deadlocks.

  • Hardware activity, such as disk usage.

Problems can include:

  • Application development errors involving incorrectly written [!INCLUDEtsql] statements.

  • Hardware errors, such as disk- or network-related errors.

  • Excessive blocking due to an incorrectly designed database.

Tools for Common Performance Problems

Equally important is careful selection of the performance problem that you want each tool to monitor or tune. The tool and the utility depend on the type of performance problem you want to resolve.

The following topics describe a variety of monitoring and tuning tools and the problems they uncover.

Identify Bottlenecks

Monitor Memory Usage