Wednesday, March 21, 2012

Force server use 3GB memory

Hi,
We have AWE enabled but SQL Server 2000 with SP3 only use
103 MB memory during peak-hour. So we try to force SQL use
3GB memory. Is the following statements' order all right?
sp_configure 'max server memory', 3072
reconfigure with override
go
exec sp_configure 'min server memory', 3072
reconfigure with override
go
exec sp_configure 'show advanced options', '1'
reconfigure with override
go
exec sp_configure 'set working set size', 1
reconfigure with override
go
then re-start SQL Server.
Thanks!
JennyHow are you monitoring the memory, Task manager doesn't understand AWE so it
reports incorrect figures. Perfmon counters will be accurate, use the Total
Server Memory (KB) counter. You don't need to set min memory or working
size, SQL will grab the memory upto max server memory at startup with AWE
enabled (thus is a good idea to set max server memory like you have
otherwise it only leaves 128MB for the OS). Having said all that, it might
be better using the /3GB switch rather than AWE assuming you have <12GB
total server memory if you only want 3 GB. I am assuming you are using
SQL2000 EE and win2kAS or wink3 EE.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jenny" <jyu@.iseoptions.com> wrote in message
news:017901c39ff2$3450fa10$a601280a@.phx.gbl...
Hi,
We have AWE enabled but SQL Server 2000 with SP3 only use
103 MB memory during peak-hour. So we try to force SQL use
3GB memory. Is the following statements' order all right?
sp_configure 'max server memory', 3072
reconfigure with override
go
exec sp_configure 'min server memory', 3072
reconfigure with override
go
exec sp_configure 'show advanced options', '1'
reconfigure with override
go
exec sp_configure 'set working set size', 1
reconfigure with override
go
then re-start SQL Server.
Thanks!
Jennysql

No comments:

Post a Comment