My Memory Usage– Performance Counters

Troubleshooting a SQL Server Memory issues by knowing how the memory is used.

1 SQL Server: Buffer Manager-Database Pages Number of database pages in the buffer pool, as opposed to other usages for memory such as free pages, procedure cache, etc.
2 SQL Server: Buffer Manager-Procedure Cache Pages Number of pages used to store compiled queries and objects.
3 SQL Server: Buffer Manager-Target Pages The ideal number of pages in the buffer pool according the maximum memory granted to SQL Server in sp_configure.
4 SQL Server: Buffer Manager-Free Pages Total number of pages available across all free lists. A value less than 640 (5MB) indicates physical memory pressure.
5 SQL Server: Buffer Manager-Stolen Pages/sec Tells how many pages were “stolen” from the buffer pool to satisfy other memory needs, such as plan cache and workspace memory. This number is a good metric to determine how much data is flowing into SQL Server caches and should remain proportionate to “Batch Requests/sec”. Also remember to look for where these stolen pages might be stolen from – optimizer memory, lock memory, and so forth.
6 SQLServer:MemoryManager-Total ServerMemory(KB) “Shows the amount of memory that SQL Server is currently using. This value should grow until its equal to Target Server Memory, as it populates its caches and loads pages into memory. When it has finished, SQL Server is said to be
in a “steady-state”. Until it is in steady-state, performance may be slow and IO may be higher”
7 SQLServer:Memory Manager-Target Server Memory(KB) Shows the amount of memory that SQL Server wants to use based on the configured Max Server Memory.
8 SQLServer:Memory Manager-Target Server Memory(KB) Shows the amount of memory that SQL Server wants to use based on the configured Max Server Memory.

Leave a Reply

Your email address will not be published. Required fields are marked *