I don't think there is much documenting this. There is some
limited info in the SQL 7 SP2 Readme from when this option
was first documented:
http://support.microsoft.com/kb/254555 On SQL Server 2000 the MemToLeave area is set at 256 MB. The
value is in mbytes. Generally, the default setting is fine.
If you are getting memory errors related to MemToLeave, you
would want to look at your Linked Servers/OLE DB, extended
stored procedures, calls to sp_OA procedures, etc. If you
have leaks or something fragmenting MemToLeave then
increasing the size is just going to postpone the errors a
bit but not solve the problem.
-Sue
On Wed, 6 Jun 2007 02:48:01 -0700, TIwang
[quoted text, click to view] <TIwang@discussions.microsoft.com> wrote:
>hi out there
>On our Windows 2003 Servers w. sp1 running MS SQL Server2000 w. sp4 we see
>from time to time that we get this error "cannot allocate 64k
>continous memory" or "SQL Server could not spawn process_loginread thread"
>which could be caused by nothing left in the "Memtoleave" pool - I have now
>search for advice on how to determine the values for the -g-switch - but
>without much success - and if I just go for the "try&error" concept my
>sql-server just allocates less and less ??? - ehh - in which units are the
>parameters for the -g option specified - bytes, kilobytes, mbytes - 4k block
>???? Any suggestions for measuring the actual running value of this pool -
>memtoleave ??
>
>best regards /ti
