Working on a project we need to first stabilize and then upgrade.
We have a 32bit Enterprise edition SQL Server 2005 installed on a 64 bit Windows 2008 standard Server.
The server has 64GB RAM installed, however in taskmgr there are only 32GB available. I believe this is a Standard Windows Server limitation, just want to confirm.
On other side, we have checked the SQL Server memory counters on perfmon, and the value we get for target and total memory is about 3.500.000, so I guess SQL server is using about 3,5GB??
I want to ask about the configurations we need to make in order to make SQL Server use as much memory as possible, hopefully 28 GB, leaving 4GB for OS, as we have no other services in this machine.
This is what I'm planning so far, but as it's a production environment, I would ideally try to nail it on one attempt, coz don't want to stop the services many times:
The service account is Local System, but I cant see the "Using locked pages for buffer pool" in the SQL Server logs. Do I need to swtich to another user account to take advantage of the "lock pages in memory" policy? What I can see in the SQL Server log is this: "Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required."
The Max server memory property is set to 10240; I think after enabled lock pages in memory, I will need to increse this to 28000
As this is 64 bit OS, no need to enable AWE. However, in the SQL server log, I can see this message: "Set AWE Enabled to 1 in the configuration parameters to allow use of more memory."
Anything else I need to take into consideration in order to enable more memory for SQL Server??