What''s running in MemToLeave????

  • Has anyone found a tool that will tell you what is currently running in the MemToLeave area?

    We are trying to track down the process's that are currently taking up memory in the MemToLeave area and not returning it back after completion.

     

  • This was removed by the editor as SPAM

  • Consists of a single contiguous region of addresses within the SQL Server process space that is set aside at startup. This area is static (the size cannot change) and is left unallocated by SQL Server for the use by components in the SQL Server process space, such as extended procedures, COM/OLE Automation objects, and linked servers. Memory allocations by SQL Server larger than 8 KB are also made from the MemToLeave area.

     

    From http://www.sqljunkies.com/Tutorial/0D4FF40A-695C-4327-A41B-F9F2FE2D58F6.scuk

  • DBCC MEMORYSTATUS is the only helpful thing I found for this.



    A.J.
    DBA with an attitude

  • SQL Server Dump can tell you what is loaded there.

    May not be easy

  • Here's the info we recieved from Microsoft:

    Based off the case that we had opened with MS, the best recommendation we have from PSS is to monitor MTL using "DBCC MEMORYSTATUS" as described in the article below :

     http://support.microsoft.com/kb/271624/en-us

     It's not very helpful, but it's the best we've got.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • I consulted with Microsoft. There is no "supported" way to monitor the usage of the MemToLeave area. They also backed up the fact that 1024mb is the absolute highest value it should ever be set to.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply