30.06.2013 Views

Performance Tuning with SQL Server Dynamic Management Views

Performance Tuning with SQL Server Dynamic Management Views

Performance Tuning with SQL Server Dynamic Management Views

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

305<br />

Chapter 7: OS and Hardware Interaction<br />

This DMV also provides additional columns to get information about the memory<br />

assigned to the system cache and the kernel if, for some reason, you need to determine<br />

these individual values.<br />

Process memory use<br />

Also, for <strong>SQL</strong> <strong>Server</strong> 2008, there is another DMV pertaining to memory, sys.dm_os_<br />

process_memory, which returns a single row summarizing memory usage from the<br />

point of view of the <strong>SQL</strong> <strong>Server</strong> process. This DMV has the following columns (and more),<br />

all of which give you the current status of memory on the server:<br />

• physical_memory_in_use_kb – all physical memory in use on the server by the<br />

<strong>SQL</strong> <strong>Server</strong> processes, in kilobytes<br />

• virtual_address_space_committed_kb – amount of virtual address space<br />

committed to the <strong>SQL</strong> <strong>Server</strong> process<br />

• virtual_address_space_available_kb – amount of virtual address space that is<br />

committed but not currently in use<br />

• page_fault_count – number of times data needed was not found in process<br />

memory, causing a physical read to disk<br />

• process_physical_memory_low – when the <strong>SQL</strong> <strong>Server</strong> process is needing more<br />

RAM than is physically available, this value is set to 1<br />

• process_virtual_memory_low – when the <strong>SQL</strong> <strong>Server</strong> process is needing more<br />

virtual RAM than is currently available, this value is set to 1.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!