If you monitor too many counters, resource usage overhead is added to the monitoring process and affects the performance of the computer that is being monitored. Monitor only the counters in which you are interested. Therefore, either log the Performance Monitor data to another disk (or computer) so that it reduces the effect on the computer being monitored, or run Performance Monitor from a remote computer. Monitoring a computer on which Performance Monitor is running can affect computer performance slightly.

When you monitor SQL Server and the Microsoft Windows operating system to investigate performance-related issues, concentrate your initial efforts in three main areas: Save individual chart, alert, log, or report settings, or the entire workspace setup for reuse. View current-activity reports, or create reports from existing log files. Run a predefined application the first time or every time a counter value goes over or under a user-defined value.Ĭreate log files that contain data about various objects from different computers.Īppend to one file selected sections from other existing log files to form a long-term archive. View and change charts to reflect current activity, and show counter values that are updated at a frequency that the user defines.Įxport data from charts, logs, alert logs, and reports to spreadsheet or database applications for further manipulation and printing.Īdd system alerts that list an event in the alert log and can notify you by issuing a network alert. View data simultaneously from any number of computers. Performance Monitor allows you to obtain statistics on current SQL Server activity and performance. For example, monitoring the Windows disk input/output (I/O) counters and the SQL Server Buffer Manager counters at the same time can reveal the behavior of the entire system. Performance Monitor can be useful to monitor Windows operating system and SQL Server counters at the same time to determine any correlation between the performance of SQL Server and Windows. Each of these objects has an associated set of counters that measure device usage, queue lengths, delays, and other indicators of throughput and internal congestion. You can view SQL Server objects, performance counters, and the behavior of other objects, such as processors, memory, cache, threads, and processes.

If you are running Microsoft Windows server operating system, use the Performance Monitor graphical tool to measure the performance of SQL Server. Applies to: SQL Server (all supported versions) - Windows only

Windows monitor resources