November 25, 2007 at 3:39 pm
try to use the -g flag in sql startup to increase the MemToLeave area (make it to ~512MB) if you still encounter the error.Let us know if this helps.
my 2 cents.
Simon Liew
Microsoft Certified Master: SQL Server 2008
November 26, 2007 at 10:47 pm
Initially we thought of doing that but the server owner has not shown interest to continue with that...but is there a way to identify whether the mem-to-leave is fragmented or not...kindly let me know so that i could help u with 2 cents 😉
November 27, 2007 at 3:03 am
you can try to use vmstat.exe to view contiguous block of memory in MemToLeave area. Quest also has a stored proc xp_memory_size to check max contiguous memory. This comes with LiteSpeed.
I googled around and found vmstat.exe is available in one of the M$ lab at
so far, not sure how much this may help in your debugging. but keep looking for any extended stored proc running on the same server as sql, and whether any COM objects that may use this memory region. unfortunately, sql doesnt have any clue what's in the MemToLeave area.
Simon
Simon Liew
Microsoft Certified Master: SQL Server 2008
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply