Resource Monitor and Performance Monitor - Microsoft SQL Server 2012 Performance Tuning - page 79

How it works...
The usage of Resource Monitor was straightforward in this recipe. Resource Monitor
basically provides resource usage information for CPU, memory, disk I/O, and network.
The main screen of Resource Monitor divides this resource usage information into the
following five tabs:
F Overview: This tab gives you an overview of usage statistics for all four main server
resources—CPU, memory, disk, and network—in their separate sections and in
real-time graphs as well. The top section on the screen also displays the list of all
processes that are currently in action. If you identify a problematic process that
could be causing performance issues, you can kill that process from here.
F CPU: This tab provides the CPU usage information, in percentage, and details for
each process that we saw on the Overview tab. From here, for any given process, we
can identify its associated services, handles, and modules. On the right-hand side, we
have a real-time graphical usage view of all the available CPUs. If you find that CPU
usage is very high, you can look at the list of processes, to identify the process that
is using more CPU by examining the CPU column.
F Memory: This tab provides memory usage information. From here, you can tell how
much memory has been installed, how much has been used, and how much memory
is free. It also displays the same list of processes, from where you can identify which
processes consume how much memory and which processes consume most of the
memory resources.
The best and most helpful feature of Resource Monitor is that you can select
particular process(es) by checking the corresponding checkbox(es) from the list
of processes, to monitor the hardware resource usage information for only that
particular process(es).
Notice that in this recipe we have selected the sqlservr.exe process, to monitor the
resource usage information for SQL Server service only.
F Disk: This tab provides usage information for the disk I/O activity of various
processes. By looking at the Read (B/Sec) and Write (B/Sec) columns, you can
identify disk I/O activity for a given process. It also displays the list of files upon
which the disk I/O activity (read/write operation) is performed for the processes.
The real-time graphical view of disk usage information is also displayed on the
right-hand side of the window.
In our example, to cause some disk I/O activity, we executed a query on the Sales.
SalesOrderDetail table in the AdventureWorks2012 database. Note the entry
for AdventureWorks2008R2_Data.mdf in Disk Activity. This file is the physical data
file for the AdventureWorks2012 database. Also, look at the Read (B/sec) column
for this file and examine the number of bytes that have been read from this file when
we executed the query.