May 2, 2005 at 12:12 am
Do I need to set "max server memory" to something > 2GB when using the /3GB (boot.ini) switch? Or will the default dynamic memory management recognize the switch and use more than the default 2GB application address space if needed?
Server is 2 processor, with 4GB of physical memory, running Windows 2000 Advanced Server, and SQL 2000 Enterprise edition. Other than an occasional remote login, SQL Server and Agent are the only things running on the box.
If I need to set "max server memory" to take advantage of the /3GB switch, what would be a good value? 2.7GB? Any reason to set "min server memory" or "working set size"?
Thanks...
May 3, 2005 at 9:34 am
Simply using the /3GB does not remove windows/sql's ability to manage memory. It simply moves 1GB from the kernel mode space over to user mode space so that instead of the OS having 2 GB and any "programs" having 2GB you limit the OS to 1 GB and the "programs" get 3 GB.
The only time you need to review the min/max server memory settings is when you have used /PAE in the boot.ini and have also enabled AWE in SQL. The user mode will still have 2 GB (or 1 if you used /3GB), and the OS will have either 1 or 2 GB depending. It's anything that has to do with physical pages or indexes (buffer cache-able objects) that uses AWE to map through the OS kernel memory to get to extended memory. The reason for the max server memory setting in this case is to prevent the mapped memory using AWE from suffocating the OS.
Mindy
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply