server| performance when you suspect that your computer hardware is the primary reason for the performance impact of SQL Server running, you can use the SQL Se
RVer Performance Monitor monitors the load of the appropriate hardware to confirm your guesses and find the system
Bottleneck. Some of the commonly used analysis objects and their parameters are described below.
Memory:page faults/sec
If the value is occasionally higher, it indicates that the thread was competing for memory. If it continues to be high, the memory may be a bottle
Neck.
Process:working Set
This parameter of SQL Server should be very close to the memory value assigned to SQL Server. In SQL Server Set
Set, if set working set size is placed to 0, Windows NT determines the SQL Server's
The size of the working set. If set working set size is placed to 1, the working set is forced to be SQL
The allocated memory size of the server. In general, it is best not to change the "set working set Size"
The default value.
Process:%processor time
If the value of this parameter persists over 95%, the bottleneck is the CPU. You may consider adding a processor or replacing a
A faster processor.
Processor:%privileged time
If the value of the parameter and the "physical Disk" parameter values are high, it indicates that I/O is problematic. May consider the replacement
Faster hard drive systems. Set up tempdb in RAM and reduce max async IO, Max Lazy W
Riter IO "and other measures will reduce this value.
Processor:%user time
Represents CPU-consuming database operations, such as sorting, executing aggregate functions, and so on. If the value is
High, you can consider the addition of index, as far as possible using simple table joins, horizontal split large tables and other methods to reduce the
Value.
Physical Disk:Avg.Disk Queue Length
This value should be no more than 1.5~2 times the number of disks. To improve performance, you can increase the disk.
Note: A RAID disk actually has more than one disk.
Sqlserver:cache Hit Ratio
The higher the value, the better. If you continue below 80%, you should consider adding more memory. Note that the parameter value is from the SQL Se
After the RVer is started, the count is cumulative, so after a period of time, the value will not reflect the system
The current value.
