SQL Server Memory Tracking with Windows Task Manager
Kevin describes a possible problem scenario when monitoring SQL Server memory using Windows Task Manager.
August 28, 2008
Have you ever looked at the Windows Task Manager for a quick read on SQL Server 2005 memory consumption? You can get good information from the Windows Task Manager about SQL Server memory, but you have to know what to look for. When running with AWE memory enabled on a 32-bit system, you may see an unusually low amount of memory in the Windows Task Manager. If AWE is being used, you will probably get a much better idea of how much AWE memory is being consumed by checking page file usage. The page file usage value and the amount of AWE memory will correspond.You can then cross-check this value against sys.dm_os_sys_info.bpool_committed for the exact value.(Thanks to Geoff N. Hiten, the "SQL Craftsman", and Erland Sommarskog for the tip.
About the Author
You May Also Like