Article ID: 279113 - View products that this article applies to.
This article was previously published under Q279113
This article has been archived. It is offered "as is" and will no longer be updated.
Understanding the virtual memory layout of a SQL Server 7.0 or SQL Server 2000 process space can help to understand memory leaks and virtual fragmentation that occur on the server. The xp_DumpVM extended stored procedure in the Xpvmlog component provides a way to dump the virtual memory layout of the SQL Server process.
The following file is available for download from the Microsoft Download Center:
Xpvmlog.exeThe Xpvmlog.exe self-extracting executable contains the following files:
Collapse this tableExpand this table
The Readme.txt file describes how to install the extended stored procedure on SQL Server 7.0 or SQL Server 2000. The name of the extended stored procedure is xp_DumpVM. If you pass no arguments, the virtual memory dump (which is a text file) is dumped into the C:\Vmlog_*.log file. The file name will contain the date and time. You can specify a folder and a prefix for the log file. For example, the following command:
xp_DumpVM 'c:\logs\vmlog'would generate a Vmlog_datetime.log file in the C:\Logs folder where datetime is the actual date and time.
A sample of some of the output is shown below. The output lists each VM region (address, type of memory, and size) and the blocks within each region.
For more information about Windows Virtual Memory and the output above, see "Advanced Windows Third Edition", by Jeffrey Richter, ISBN 1-57231-548-2.