Memory -again

Hi
I am starting a new thread so that is easy to follow.
We have 6GB of memory on Windows 2003 Enterprise Edition SQL 2000 Enterprise
Edition.
We have used /PAE switch and /3GB switch in boot.ini
We have run following commands on SQL server so that SQL server can use 5GB
of memory
exec sp_configure 'awe enabled', 1
reconfigure
go
exec sp_configure "max server memory" 5120
reconfigure
go
We have rebooted the box several times.
Problem
When we run sp_configure, we get the following values
Name min max config_value run_value
max server memory (MB) 4 2147483647 5120 5120
but when we look properties in Enterprise manager
we see that “Use a fixed memory size(MB)” is set to 3583 MB.
How do we get it to use more memory and is it correct that it is marked as
“Use a fixed memory size(MB)” and not “Dynamically configure SQL serve
r
memory”
Regards,
AmarHi Amar
The user account that the SQL Server service is running under needs to have
"Lock pages in memory" permissions (this is what AWE does).
Have you checked this?
Regards,
Greg Linwood
SQL Server MVP
"Amar" <Amar@.discussions.microsoft.com> wrote in message
news:A287F3C6-3D2F-46C6-8CC6-D8D84B1F9160@.microsoft.com...
> Hi
> I am starting a new thread so that is easy to follow.
> We have 6GB of memory on Windows 2003 Enterprise Edition SQL 2000
> Enterprise
> Edition.
> We have used /PAE switch and /3GB switch in boot.ini
> We have run following commands on SQL server so that SQL server can use
> 5GB
> of memory
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> exec sp_configure "max server memory" 5120
> reconfigure
> go
>
> We have rebooted the box several times.
> Problem
> When we run sp_configure, we get the following values
> Name min max config_value run_value
> max server memory (MB) 4 2147483647 5120 5120
>
> but when we look properties in Enterprise manager
> we see that "Use a fixed memory size(MB)" is set to 3583 MB.
> How do we get it to use more memory and is it correct that it is marked as
> "Use a fixed memory size(MB)" and not "Dynamically configure SQL server
> memory"
>
> Regards,
> Amar
>|||Have you tried setting awe enabled "on"
exec sp_configure 'awe enabled', 1
go
reconfigure with override
You might want to consider setting min and max server memory to whatever
value you want SQL Server to use.
Keith
"Amar" <Amar@.discussions.microsoft.com> wrote in message
news:A287F3C6-3D2F-46C6-8CC6-D8D84B1F9160@.microsoft.com...
> Hi
> I am starting a new thread so that is easy to follow.
> We have 6GB of memory on Windows 2003 Enterprise Edition SQL 2000
> Enterprise
> Edition.
> We have used /PAE switch and /3GB switch in boot.ini
> We have run following commands on SQL server so that SQL server can use
> 5GB
> of memory
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> exec sp_configure "max server memory" 5120
> reconfigure
> go
>
> We have rebooted the box several times.
> Problem
> When we run sp_configure, we get the following values
> Name min max config_value run_value
> max server memory (MB) 4 2147483647 5120 5120
>
> but when we look properties in Enterprise manager
> we see that "Use a fixed memory size(MB)" is set to 3583 MB.
> How do we get it to use more memory and is it correct that it is marked as
> "Use a fixed memory size(MB)" and not "Dynamically configure SQL server
> memory"
>
> Regards,
> Amar
>|||To enable the Lock Page in Memory option
1.. On the Start menu, click Run, and then in the Open box, type
gpedit.msc.
2.. On the Group Policy console, expand Computer Configuration, and then
expand Windows Settings.
3.. Expand Security Settings, and then expand Local Policies.
4.. Select the Users Rights Assignment check box.
The policies will be displayed in the details pane.
5.. In the details pane, double-click Lock pages in memory.
6.. In the Local Security Policy Setting dialog box, click Add.
7.. In the Select Users or Groups dialog box, add an account with
privileges to run sqlservr.exe.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Greg Linwood" wrote:

> Hi Amar
> The user account that the SQL Server service is running under needs to hav
e
> "Lock pages in memory" permissions (this is what AWE does).
> Have you checked this?
> Regards,
> Greg Linwood
> SQL Server MVP
> "Amar" <Amar@.discussions.microsoft.com> wrote in message
> news:A287F3C6-3D2F-46C6-8CC6-D8D84B1F9160@.microsoft.com...
>
>|||7.. In the Select Users or Groups dialog box, add an account with
privileges to run sqlservr.exe.
This is slightly mis-leading, depending on how you interpret it..
You don't select an account "with privileges to run sqlservr.exe" - you
select the user user account that the sql server service is configured to
log on as (I'm sure this is what you meant though).
Regards,
Greg Linwood
SQL Server MVP
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:C6C91370-14A0-4C99-87F7-8C842B6C2E0F@.microsoft.com...[vbcol=seagreen]
> To enable the Lock Page in Memory option
> 1.. On the Start menu, click Run, and then in the Open box, type
> gpedit.msc.
> 2.. On the Group Policy console, expand Computer Configuration, and then
> expand Windows Settings.
> 3.. Expand Security Settings, and then expand Local Policies.
> 4.. Select the Users Rights Assignment check box.
> The policies will be displayed in the details pane.
> 5.. In the details pane, double-click Lock pages in memory.
> 6.. In the Local Security Policy Setting dialog box, click Add.
> 7.. In the Select Users or Groups dialog box, add an account with
> privileges to run sqlservr.exe.
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Greg Linwood" wrote:
>