Run multiple times, and run periodically if you suspect you are under memory pressure WHERE LIKE N'%Memory Manager%' - Handles named instancesДЄND counter_name = N'Memory Grants Pending' OPTION (RECOMPILE) (47) - Memory Grants Pending value for current instance (Query 47) (Memory Grants Pending) Available physical memory is running low This indicates that you are not under external memory pressure You want to see 'Available physical memory is high' for System Memory State System_memory_state_desc AS ДЇROM sys.dm_os_sys_memory WITH (NOLOCK) OPTION (RECOMPILE) Total_page_file_kb/1024 AS ,ДЄvailable_page_file_kb/1024 AS , SELECT total_physical_memory_kb/1024 AS ,ДЄvailable_physical_memory_kb/1024 AS , (Query 14) - Good basic information about OS memory amounts and state (Query 14) (System Memory) Watch the trend over time, not the absolute value PLE is a good measurement of internal memory pressure WHERE LIKE N'%Buffer Node%' - Handles named instancesДЄND counter_name = N'Page life expectancy' OPTION (RECOMPILE) SELECT AS, RTRIM() AS, instance_name, cntr_value AS ДЇROM sys.dm_os_performance_counters WITH (NOLOCK) See comment - Page Life Expectancy (PLE) value for each NUMA node in current instance (Query 46) (PLE by NUMA Node) SQL Server 2017 Diagnostic Information Queries: 'I am trying to determine if memory pressure is an issue to some of my problem.' To read more about why task manager should not be used see Fun with Locked Pages, AWE, Task Manager, and the Working SetвЂ¦

Total_Memory_usedBy_SQLServer_MB- Gives total memory(RAM+Page file) used by SQL Server in MB Phy_Memory_usedby_Sqlserver_MB- Gives total Physical memory used by SQL Server in MB (virtual_address_space_committed_kb/1024 )Total_Memory_UsedBySQLServer_MB, (locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB, (physical_memory_in_use_kb/1024)Phy_Memory_usedby_Sqlserver_MB, To know how much physical memory SQL Server is using please use below query select Don`t panic if some tool is showing low CPU utilization and task manager is showing high memory this may be just normal.

It is quite normal for SQL Server to utilize memory allocated to it which often seems like it is using high memory but this is quite normal. This is because normally task manager tracks Process Private bytes which is pageable memory and allocated via VirtualAlloc() function but with Service account having LPIM chunk of memory allocation is done by AWE API which is NON pageable so task manager does not tracks it and this can lead to incorrect value. I would start by saying Task Manager is not a correct place to gauge SQL Server memory consumption, it will not tell you correct value when SQL Server service account has Locked Pages in Memory(LPIM) privilege. Can someone direct to a good/proper explanation.

Ewqlso physical memory issue fix