| Rich Sienkiewicz 2002-10-05, 9:13 pm |
| SQL Server, by default, will eventually use all a
machine's memory and keep between 4 and 10 Meg free. On
systems that use MSDE, the "desktop" version of SQL
Server, this is of course unacceptable. But I can
configure the max server memory using SQL-DMO so no
problem, right?
On our systems I configure the "max server memory"
property of SQL Server to be 1/3 the total physical
memory. When I use Enterprise Manager and connect to any
of these MSDE machines, I do indeed see the max server
memory set to what I said. For example, on a NT system
with 192meg of memory, that server is set to use 66Meg.
On another NT box with 512meg, the server is set to use
89meg.
However, after you let these systems run you will see,
via the Task Manager that they are using far more than
that. On the 192meg machine that is set to use 66meg, the
task manager says its using 76meg of memory and 80meg of
VM memory. The other 512meg system, configured to use
89meg, shows 104meg of memory and another 104meg of VM
memory. On some systems, but not all, after a couple of
days, virutally all the memory will be used by SQL
Server.
So what gives? Does SQL Server ignore this setting? Do I
have to use the fixed size instead?
Thanks,
Rich
|