In addition, to monitor memory, we can use the following counters:
This counter indicates the number of pages that either were retrieved from disk due to hard page faults or written to disk to free space in the working set due to page faults. A high rate for the Pages/sec counter could indicate excessive paging.The average Pages/sec value should be below 50.
Memory: Page Faults/sec
This counter indicates the rate of Page Faults for all processes including system processes. A low but non-zero rate of paging to disk (and hence page faults) is typical, even if the computer has plenty of available memory. The normal values are 10 to 15, but even 1,000 page faults per second can be normal in specific environments.
Memory: Available bytes
This counter indicates how many bytes of memory are currently available for use by processes. Low values for the Available Bytes counter can indicate an overall shortage of operating system memory. If the memory Available bytes value is constantly lower than 100 MB, it indicates that there is insufficient memory on the server, or that there is an application that is not releasing memory.
SQL Server: Memory Manager: Total Server Memory (KB)
This counter indicates the amount of the operating system's memory the SQL Server memory manager currently has committed to SQL Server. If the Total Server Memory (KB) value is consistently high, it means that SQL Server is constantly using a lot of memory and that the server is under memory pressure.
SQL Server: Memory Manager: Target Server Memory (KB)
This counter indicates an ideal amount of memory SQL Server could consume, based on recent workload. When the Total Server Memory and Target Server Memory values are close, there’s no memory pressure on the server.
SQL Server: Buffer Manager: Buffer Cache Hit Ratio
This counter is specific to SQL Server. A ratio of 90 or higher is desirable. A value greater than 90 indicates that more than 90 percent of all requests for data were satisfied from the data cache in memory without having to read from disk.
SQL Server: Buffer Manager: Page life expectancy
This counter measures amount of time in seconds that the oldest page stays in the buffer pool. For systems that use a NUMA architecture, this is the average across the all NUMA nodes. A higher, growing value is best. A sudden dip indicates a significant churn of data in and out of the buffer pool, indicating the workload could not fully benefit from data already in memory.
Please refer to SQL Server memory performance metrics and Monitor memory usage which might help.
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.