TIwang


hi out there
On our Windows 2003 servers w. sp1 and running MS SQL Server 2000 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




Re: Memtoleave and -g-switch

Ron D.


The units for -g are MB. The default is 256.

Is this a 32 or 64 bit system

How much memory is on the system

Are you running SQL Server with AWE enabled







Re: Memtoleave and -g-switch

WesleyB

Could you run the following query (when you are having this problem) and gives us the results.

Code Snippet

SELECT type, multi_pages_kb FROM sys.dm_os_memory_clerks WHERE multi_pages_kb > 0

ORDER BY multi_pages_kb DESC

WesleyB

Visit my SQL Server weblog @ http://dis4ea.blogspot.com






Re: Memtoleave and -g-switch

Ron D.

SQL 2000 does not have DMVs. There's no easy way to profile memory usage in SQL 2000. See http://msdn2.microsoft.com/en-US/library/aa175282(sql.80).aspx for more information

Thanks, Ron D.






Re: Memtoleave and -g-switch

WesleyB

Oops, I missed the 2000 part :-)