The Activity Summary window gives a quick access to the activity of a SQLServer instance.
Percentage of CPU used by SQLServer
Total Total amount of dynamic memory (in kilobytes) that the server is using currently. Connection Total amount of dynamic memory the server is using for maintaining connections. Sort, Hash, Index Total amount of memory currently granted to executing processes such as hash, sort, bulk copy, and index creation operations. Optimizer Total amount of dynamic memory the server is using for query optimization. Lock Total amount of dynamic memory the server is using for locks. Free Total number of free memory.
Number of user connections. Because each user connection consumes some memory, configuring overly high numbers of user connections could affect throughput. Set user connections to the maximum expected number of concurrent users.
Logins and Logouts per second
Logins Total number of logins started per second. Logouts Total number of logout operations started per second.
Cache hit ratios
Buffer cache Percentage of pages found in the buffer cache without having to read from disk. The ratio is the total number of cache hits divided by the total number of cache lookups since an instance of SQL Server was started. After a long period of time, the ratio moves very little. Because reading from the cache is much less expensive than reading from disk, you want this ratio to be high. Generally, you can increase the buffer cache hit ratio by increasing the amount of memory available to SQL Server. Procedure cache Ratio between cache hits and lookups.
Locks per second
Number of new locks and lock conversions per second requested from the lock manager.
Latches/Locks Waits per second
Latches Number of latch requests that could not be granted immediately. Locks Number of lock requests per second that required the caller to wait.
IO (per second)
Physical reads Number of physical database page reads that are issued per second. This statistic displays the total number of physical page reads across all databases. Because physical I/O is expensive, you may be able to minimize the cost, either by using a larger data cache, intelligent indexes, and more efficient queries, or by changing the database design. Physical writes Number of physical database page writes issued. Logical reads Number of requests to find a page in the buffer pool.
Copyright © AgileLoad. All rights reserved.