db性能指标(国外英语资料).doc

db性能指标(国外英语资料) SQL Server Note: the following metrics are taken from the performance counter provided by SQL Server itself. The index name indicator describes the unit of index The Access Methods object in SQL Server contains a performance counter Full table scan/second Full Scans/SEC refers to the number of total table Scans per second. Full table scans can be basic table scans or full index scans. Because full table scans take a lot of time, the frequency of full table scans is too high to affect performance. If the value of the index is higher than 1 or 2, the query should be analyzed to determine whether full table scans are required and whether SQL queries can be optimized. Number of times/SEC. The performance counter that the Buffer Manager object contains in SQL Server Buffer Cache hit ratio (Buffer Cache) Hit Ratio %) refers to the percentage of pages found in a buffer cache that do not need to be read from the disk. This ratio is the ratio of the total number of hits to the cache. After a long time, the ratio changes little. Because reading data from a cache is much smaller than reading data from a disk, it is generally expected to be higher. The value of the target is 90% or higher. You can usually increase the value of this metric by increasing the amount of memory available for SQL Server. Increase memory until this metric is consistently above 90%, indicating that more than 90% of the data requests can be obtained from the data buffer. % Read pages/SEC Page Reads/SEC refers to the number of physical database Page Reads per second. This metric focuses on how often the database reads data from disk. Because physical I/O takes a lot of time, it should be possible to minimize physical I/O as much as possible to improve performance. The value of this metric should be as small as possible. You can reduce the value of this metric by using larger data caching, smarter indexing, more efficient queries, or changing database design. The number/SEC. Write pages/SEC