I am running SQL Server 2000 EE (with SP3a) on Windows 2000 Advanced Server with the /PAE /3GB OS boot parameters. My server has 8GB of physical memory. I can confirm that the OS can definitely see all 8GB and the SQL log file reports "Address Windowing Extensions enabled." As can be seen in the config below, the following SQL Server memory configuration options are currently set: name minimum maximum config_value run_value ----------------------------------- ----------- ----------- ------------ ----------- max server memory (MB) 4 2147483647 4096 4096 min server memory (MB) 0 2147483647 4096 4096 set working set size 0 1 1 1 The value is reasonable, 4GB, half the physical memory available, the min and max are the same and the set size option is 1. According to BOL, the configuration above should work fine. However, I consistently get the following SQL log file warning on each reboot. initdata: Warning: Could not set working set size to 0 KB. 0 KB? Surely that cant be right? I know some members will simply advise to set the working set size option to 0, but that then defeats the purpose of having a set size option, so it's not an acceptable solution. In addition, I recently read this article from Intel: http://www.intel.com/cd/ids/developer/asmo-na/eng/189869.htm?page=4 It states there that the combination of the /PAE and /3GB OS boot parameters.. "App gets 3GB and benefits from full 8GB memory." Is SQL Server considered to be an application in the normal sense? If an application "gets 3GB" then how can it "benefit from the full 8GB"? It sounds like a contradiction. Surely an application can only benefit from what it gets? Also; if SQL Server only "gets 3GB", and I have a working set size of 4GB, could this be generating the log warning? Any insights on the above would be appreciated.