August 6, 2007 at 7:34 pm
I've got SQL Server 2000 sp3a which used to be a Standard Edition sitting on Windows 2000 Server Standard. I moved it to a new server on Windows 2003 Enterprise and then upgraded it to the Enterprise Edition. The server has 6GB of RAM. I've allocated 3.5GB as minimum server memory and 5GB as maximum server memory. It has AWE enabled and /PAE & /3GB switches in boot.ini. Total pages counter tells me that SQL server uses only 338344 pages, which is around 2643MB. This number does not change at all even when the server has drops in buffer cache ratio. It looks like it hits some obstacle and can not get any more memory. Another thing that looks suspicious is that task manager shows aprox 2816MB of memory taken by SQL server process, while for a server with AWE enabled it typically shows wrong very small amount of memory, and you typically can not tell how much memory SQL Server takes using task manager for such setup.
I think it may be due to the fact that in-place upgrade is not 100% valid in terms of making it fully Enterprise Edition.
Any ideas?
Thanks.
August 7, 2007 at 12:51 pm
well, since you are over the 2 gig max for standard, I'm betting that it does recognize that you have enterprise edition.
August 7, 2007 at 1:07 pm
It appears that only the /3GB is being used. Check the SQL Server errorlog for a message "Address Windowing Extension enabled". If missing, then AWE is not enabled.
Confirm that SQL Server has been configured to use AWE by running:
exec sp_configure 'awe enabled'
This should return 1
Also, with AWE, only the "max server memory" will be used, "min server memory" is ignored and SQL Server memory will be a fixed amount.
Finally, the SQL Server service account wil need the Window privilege "lock pages in memory" for AWE to work.
SQL = Scarcely Qualifies as a Language
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply