Configuring and using PAE on SQS Server 2000 Enterprise Edition

We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
machine with 16 GB of memory. I am trying to use more than the default 2GB of
memory for SQL Server.
I have added the /PAE switch to the boot.ini file on the server, configured
SQL Server by issuing a
sp_configure 'show advanced options', 1
RECONFIGURE
and a
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 14336
RECONFIGURE
GO
However, it looks like SQL Server is till using less than 2GB of memory when
running. I have run the sp_configure check on it's own and noticed that the
config_value for AWE enabled is 1, but that the run_value is still 0.
Could that be the problem? What do I have to do to fix this?
I know I did restart the server after adding the settings (the setting for
'show advanced options' and 'max server memory' both show the same value for
config and run_value. It is just the AWE enable setting that has a
discrepancy.
Should I set the 'max server memory' to less than 14 GB if the server has
16GB available? How much does the OS need?
Thanks
FredHow to configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
Managing AWE Memor
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
AMB
"fredscuba" wrote:
> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configured
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory when
> running. I have run the sp_configure check on it's own and noticed that the
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value for
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred|||Alejandro,
I did go through the instructions that are shown on the pages you bookmarked
(see my original post).
My question is: why is SQL Server still using less than 2GB of memory even
after I have setup my boot.ini and enabled AWE and set the max server
memory?
Fred
"Alejandro Mesa" wrote:
> How to configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> Managing AWE Memory
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>
> AMB
>
> "fredscuba" wrote:
> > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > memory for SQL Server.
> >
> > I have added the /PAE switch to the boot.ini file on the server, configured
> > SQL Server by issuing a
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> >
> > and a
> >
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'max server memory', 14336
> > RECONFIGURE
> > GO
> >
> > However, it looks like SQL Server is till using less than 2GB of memory when
> > running. I have run the sp_configure check on it's own and noticed that the
> > config_value for AWE enabled is 1, but that the run_value is still 0.
> >
> > Could that be the problem? What do I have to do to fix this?
> >
> > I know I did restart the server after adding the settings (the setting for
> > 'show advanced options' and 'max server memory' both show the same value for
> > config and run_value. It is just the AWE enable setting that has a
> > discrepancy.
> >
> > Should I set the 'max server memory' to less than 14 GB if the server has
> > 16GB available? How much does the OS need?
> >
> > Thanks
> >
> > Fred|||What Edition of Windows 2003 Server?
AMB
"fredscuba" wrote:
> Alejandro,
> I did go through the instructions that are shown on the pages you bookmarked
> (see my original post).
> My question is: why is SQL Server still using less than 2GB of memory even
> after I have setup my boot.ini and enabled AWE and set the max server
> memory?
> Fred
>
> "Alejandro Mesa" wrote:
> > How to configure memory for more than 2 GB in SQL Server
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >
> > Managing AWE Memory
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >
> >
> > AMB
> >
> >
> > "fredscuba" wrote:
> >
> > > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > > memory for SQL Server.
> > >
> > > I have added the /PAE switch to the boot.ini file on the server, configured
> > > SQL Server by issuing a
> > >
> > > sp_configure 'show advanced options', 1
> > > RECONFIGURE
> > >
> > > and a
> > >
> > > sp_configure 'awe enabled', 1
> > > RECONFIGURE
> > > GO
> > > sp_configure 'max server memory', 14336
> > > RECONFIGURE
> > > GO
> > >
> > > However, it looks like SQL Server is till using less than 2GB of memory when
> > > running. I have run the sp_configure check on it's own and noticed that the
> > > config_value for AWE enabled is 1, but that the run_value is still 0.
> > >
> > > Could that be the problem? What do I have to do to fix this?
> > >
> > > I know I did restart the server after adding the settings (the setting for
> > > 'show advanced options' and 'max server memory' both show the same value for
> > > config and run_value. It is just the AWE enable setting that has a
> > > discrepancy.
> > >
> > > Should I set the 'max server memory' to less than 14 GB if the server has
> > > 16GB available? How much does the OS need?
> > >
> > > Thanks
> > >
> > > Fred|||Are you sure it is Enterprise Edition and not Std? What Edition is the OS?
What does @.@.VERSION or xp_MSVer show? After you get it going I would start
out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty and
there is a little room to spare for other apps.
--
Andrew J. Kelly SQL MVP
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> Alejandro,
> I did go through the instructions that are shown on the pages you
> bookmarked
> (see my original post).
> My question is: why is SQL Server still using less than 2GB of memory even
> after I have setup my boot.ini and enabled AWE and set the max server
> memory?
> Fred
>
> "Alejandro Mesa" wrote:
>> How to configure memory for more than 2 GB in SQL Server
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> Managing AWE Memory
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>>
>> AMB
>>
>> "fredscuba" wrote:
>> > We are running SQL Server 2000 Enterprise Edition on a Windows Server
>> > 2003
>> > machine with 16 GB of memory. I am trying to use more than the default
>> > 2GB of
>> > memory for SQL Server.
>> >
>> > I have added the /PAE switch to the boot.ini file on the server,
>> > configured
>> > SQL Server by issuing a
>> >
>> > sp_configure 'show advanced options', 1
>> > RECONFIGURE
>> >
>> > and a
>> >
>> > sp_configure 'awe enabled', 1
>> > RECONFIGURE
>> > GO
>> > sp_configure 'max server memory', 14336
>> > RECONFIGURE
>> > GO
>> >
>> > However, it looks like SQL Server is till using less than 2GB of memory
>> > when
>> > running. I have run the sp_configure check on it's own and noticed that
>> > the
>> > config_value for AWE enabled is 1, but that the run_value is still 0.
>> >
>> > Could that be the problem? What do I have to do to fix this?
>> >
>> > I know I did restart the server after adding the settings (the setting
>> > for
>> > 'show advanced options' and 'max server memory' both show the same
>> > value for
>> > config and run_value. It is just the AWE enable setting that has a
>> > discrepancy.
>> >
>> > Should I set the 'max server memory' to less than 14 GB if the server
>> > has
>> > 16GB available? How much does the OS need?
>> >
>> > Thanks
>> >
>> > Fred|||Andrew & Alejandro,
I am running Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
Edition.
I think the problem is that the config_value for 'AWE enabled' is 1, but
that the run_value is still 0.
Why would that be? What do I have to do to fix this?
I am fairly sure that I restarted the server after changing the AWE setting,
but I can do it again after hours (it is a production server).
Is there any reason why the 'AWE enabled' setting would stay at a run_value
of 0, even after I try to set it with:
sp_configure 'awe enabled', 1
RECONFIGURE
Fred
"Andrew J. Kelly" wrote:
> Are you sure it is Enterprise Edition and not Std? What Edition is the OS?
> What does @.@.VERSION or xp_MSVer show? After you get it going I would start
> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty and
> there is a little room to spare for other apps.
> --
> Andrew J. Kelly SQL MVP
>
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> > Alejandro,
> >
> > I did go through the instructions that are shown on the pages you
> > bookmarked
> > (see my original post).
> >
> > My question is: why is SQL Server still using less than 2GB of memory even
> > after I have setup my boot.ini and enabled AWE and set the max server
> > memory?
> >
> > Fred
> >
> >
> > "Alejandro Mesa" wrote:
> >
> >> How to configure memory for more than 2 GB in SQL Server
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >>
> >> Managing AWE Memory
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >>
> >>
> >> AMB
> >>
> >>
> >> "fredscuba" wrote:
> >>
> >> > We are running SQL Server 2000 Enterprise Edition on a Windows Server
> >> > 2003
> >> > machine with 16 GB of memory. I am trying to use more than the default
> >> > 2GB of
> >> > memory for SQL Server.
> >> >
> >> > I have added the /PAE switch to the boot.ini file on the server,
> >> > configured
> >> > SQL Server by issuing a
> >> >
> >> > sp_configure 'show advanced options', 1
> >> > RECONFIGURE
> >> >
> >> > and a
> >> >
> >> > sp_configure 'awe enabled', 1
> >> > RECONFIGURE
> >> > GO
> >> > sp_configure 'max server memory', 14336
> >> > RECONFIGURE
> >> > GO
> >> >
> >> > However, it looks like SQL Server is till using less than 2GB of memory
> >> > when
> >> > running. I have run the sp_configure check on it's own and noticed that
> >> > the
> >> > config_value for AWE enabled is 1, but that the run_value is still 0.
> >> >
> >> > Could that be the problem? What do I have to do to fix this?
> >> >
> >> > I know I did restart the server after adding the settings (the setting
> >> > for
> >> > 'show advanced options' and 'max server memory' both show the same
> >> > value for
> >> > config and run_value. It is just the AWE enable setting that has a
> >> > discrepancy.
> >> >
> >> > Should I set the 'max server memory' to less than 14 GB if the server
> >> > has
> >> > 16GB available? How much does the OS need?
> >> >
> >> > Thanks
> >> >
> >> > Fred
>
>|||The most obvious reason would be that you didn't actually restart SQL
Server. I would try that and see if it fixes it.
--
Andrew J. Kelly SQL MVP
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
> Andrew & Alejandro,
> I am running Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
> Edition.
> I think the problem is that the config_value for 'AWE enabled' is 1, but
> that the run_value is still 0.
> Why would that be? What do I have to do to fix this?
> I am fairly sure that I restarted the server after changing the AWE
> setting,
> but I can do it again after hours (it is a production server).
> Is there any reason why the 'AWE enabled' setting would stay at a
> run_value
> of 0, even after I try to set it with:
> sp_configure 'awe enabled', 1
> RECONFIGURE
>
> Fred
>
> "Andrew J. Kelly" wrote:
>> Are you sure it is Enterprise Edition and not Std? What Edition is the
>> OS?
>> What does @.@.VERSION or xp_MSVer show? After you get it going I would
>> start
>> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
>> and
>> there is a little room to spare for other apps.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
>> > Alejandro,
>> >
>> > I did go through the instructions that are shown on the pages you
>> > bookmarked
>> > (see my original post).
>> >
>> > My question is: why is SQL Server still using less than 2GB of memory
>> > even
>> > after I have setup my boot.ini and enabled AWE and set the max server
>> > memory?
>> >
>> > Fred
>> >
>> >
>> > "Alejandro Mesa" wrote:
>> >
>> >> How to configure memory for more than 2 GB in SQL Server
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> >>
>> >> Managing AWE Memory
>> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>> >>
>> >>
>> >> AMB
>> >>
>> >>
>> >> "fredscuba" wrote:
>> >>
>> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
>> >> > Server
>> >> > 2003
>> >> > machine with 16 GB of memory. I am trying to use more than the
>> >> > default
>> >> > 2GB of
>> >> > memory for SQL Server.
>> >> >
>> >> > I have added the /PAE switch to the boot.ini file on the server,
>> >> > configured
>> >> > SQL Server by issuing a
>> >> >
>> >> > sp_configure 'show advanced options', 1
>> >> > RECONFIGURE
>> >> >
>> >> > and a
>> >> >
>> >> > sp_configure 'awe enabled', 1
>> >> > RECONFIGURE
>> >> > GO
>> >> > sp_configure 'max server memory', 14336
>> >> > RECONFIGURE
>> >> > GO
>> >> >
>> >> > However, it looks like SQL Server is till using less than 2GB of
>> >> > memory
>> >> > when
>> >> > running. I have run the sp_configure check on it's own and noticed
>> >> > that
>> >> > the
>> >> > config_value for AWE enabled is 1, but that the run_value is still
>> >> > 0.
>> >> >
>> >> > Could that be the problem? What do I have to do to fix this?
>> >> >
>> >> > I know I did restart the server after adding the settings (the
>> >> > setting
>> >> > for
>> >> > 'show advanced options' and 'max server memory' both show the same
>> >> > value for
>> >> > config and run_value. It is just the AWE enable setting that has a
>> >> > discrepancy.
>> >> >
>> >> > Should I set the 'max server memory' to less than 14 GB if the
>> >> > server
>> >> > has
>> >> > 16GB available? How much does the OS need?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Fred
>>|||Hi,
Apologies if this has already been checked, but have you looked in the SQL
Server log for an entry of 'Address Windowing Extensions enabled' to clarify
if AWE is enabled or not?
--
Regards
Robert
"fredscuba" wrote:
> Andrew & Alejandro,
> I am running Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
> Edition.
> I think the problem is that the config_value for 'AWE enabled' is 1, but
> that the run_value is still 0.
> Why would that be? What do I have to do to fix this?
> I am fairly sure that I restarted the server after changing the AWE setting,
> but I can do it again after hours (it is a production server).
> Is there any reason why the 'AWE enabled' setting would stay at a run_value
> of 0, even after I try to set it with:
> sp_configure 'awe enabled', 1
> RECONFIGURE
>
> Fred
>
> "Andrew J. Kelly" wrote:
> > Are you sure it is Enterprise Edition and not Std? What Edition is the OS?
> > What does @.@.VERSION or xp_MSVer show? After you get it going I would start
> > out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty and
> > there is a little room to spare for other apps.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> > news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> > > Alejandro,
> > >
> > > I did go through the instructions that are shown on the pages you
> > > bookmarked
> > > (see my original post).
> > >
> > > My question is: why is SQL Server still using less than 2GB of memory even
> > > after I have setup my boot.ini and enabled AWE and set the max server
> > > memory?
> > >
> > > Fred
> > >
> > >
> > > "Alejandro Mesa" wrote:
> > >
> > >> How to configure memory for more than 2 GB in SQL Server
> > >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> > >>
> > >> Managing AWE Memory
> > >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> > >>
> > >>
> > >> AMB
> > >>
> > >>
> > >> "fredscuba" wrote:
> > >>
> > >> > We are running SQL Server 2000 Enterprise Edition on a Windows Server
> > >> > 2003
> > >> > machine with 16 GB of memory. I am trying to use more than the default
> > >> > 2GB of
> > >> > memory for SQL Server.
> > >> >
> > >> > I have added the /PAE switch to the boot.ini file on the server,
> > >> > configured
> > >> > SQL Server by issuing a
> > >> >
> > >> > sp_configure 'show advanced options', 1
> > >> > RECONFIGURE
> > >> >
> > >> > and a
> > >> >
> > >> > sp_configure 'awe enabled', 1
> > >> > RECONFIGURE
> > >> > GO
> > >> > sp_configure 'max server memory', 14336
> > >> > RECONFIGURE
> > >> > GO
> > >> >
> > >> > However, it looks like SQL Server is till using less than 2GB of memory
> > >> > when
> > >> > running. I have run the sp_configure check on it's own and noticed that
> > >> > the
> > >> > config_value for AWE enabled is 1, but that the run_value is still 0.
> > >> >
> > >> > Could that be the problem? What do I have to do to fix this?
> > >> >
> > >> > I know I did restart the server after adding the settings (the setting
> > >> > for
> > >> > 'show advanced options' and 'max server memory' both show the same
> > >> > value for
> > >> > config and run_value. It is just the AWE enable setting that has a
> > >> > discrepancy.
> > >> >
> > >> > Should I set the 'max server memory' to less than 14 GB if the server
> > >> > has
> > >> > 16GB available? How much does the OS need?
> > >> >
> > >> > Thanks
> > >> >
> > >> > Fred
> >
> >
> >|||And check to make sure the account sql server is running under has Lock
Pages In Memory rights.
--
Andrew J. Kelly SQL MVP
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
> The most obvious reason would be that you didn't actually restart SQL
> Server. I would try that and see if it fixes it.
> --
> Andrew J. Kelly SQL MVP
>
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
>> Andrew & Alejandro,
>> I am running Server 2003 Enterprise Edition and SQL Server 2000
>> Enterprise
>> Edition.
>> I think the problem is that the config_value for 'AWE enabled' is 1, but
>> that the run_value is still 0.
>> Why would that be? What do I have to do to fix this?
>> I am fairly sure that I restarted the server after changing the AWE
>> setting,
>> but I can do it again after hours (it is a production server).
>> Is there any reason why the 'AWE enabled' setting would stay at a
>> run_value
>> of 0, even after I try to set it with:
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>>
>> Fred
>>
>> "Andrew J. Kelly" wrote:
>> Are you sure it is Enterprise Edition and not Std? What Edition is the
>> OS?
>> What does @.@.VERSION or xp_MSVer show? After you get it going I would
>> start
>> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
>> and
>> there is a little room to spare for other apps.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
>> > Alejandro,
>> >
>> > I did go through the instructions that are shown on the pages you
>> > bookmarked
>> > (see my original post).
>> >
>> > My question is: why is SQL Server still using less than 2GB of memory
>> > even
>> > after I have setup my boot.ini and enabled AWE and set the max server
>> > memory?
>> >
>> > Fred
>> >
>> >
>> > "Alejandro Mesa" wrote:
>> >
>> >> How to configure memory for more than 2 GB in SQL Server
>> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> >>
>> >> Managing AWE Memory
>> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>> >>
>> >>
>> >> AMB
>> >>
>> >>
>> >> "fredscuba" wrote:
>> >>
>> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
>> >> > Server
>> >> > 2003
>> >> > machine with 16 GB of memory. I am trying to use more than the
>> >> > default
>> >> > 2GB of
>> >> > memory for SQL Server.
>> >> >
>> >> > I have added the /PAE switch to the boot.ini file on the server,
>> >> > configured
>> >> > SQL Server by issuing a
>> >> >
>> >> > sp_configure 'show advanced options', 1
>> >> > RECONFIGURE
>> >> >
>> >> > and a
>> >> >
>> >> > sp_configure 'awe enabled', 1
>> >> > RECONFIGURE
>> >> > GO
>> >> > sp_configure 'max server memory', 14336
>> >> > RECONFIGURE
>> >> > GO
>> >> >
>> >> > However, it looks like SQL Server is till using less than 2GB of
>> >> > memory
>> >> > when
>> >> > running. I have run the sp_configure check on it's own and noticed
>> >> > that
>> >> > the
>> >> > config_value for AWE enabled is 1, but that the run_value is still
>> >> > 0.
>> >> >
>> >> > Could that be the problem? What do I have to do to fix this?
>> >> >
>> >> > I know I did restart the server after adding the settings (the
>> >> > setting
>> >> > for
>> >> > 'show advanced options' and 'max server memory' both show the same
>> >> > value for
>> >> > config and run_value. It is just the AWE enable setting that has a
>> >> > discrepancy.
>> >> >
>> >> > Should I set the 'max server memory' to less than 14 GB if the
>> >> > server
>> >> > has
>> >> > 16GB available? How much does the OS need?
>> >> >
>> >> > Thanks
>> >> >
>> >> > Fred
>>
>|||Hi
Before you set AWE you need to set "Lock Pages In Memory" first.
How to set the "Lock Pages In Memory", Please see URL
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servp_2vqh.asp
By default SQL Seerver 2000 in Windows 2003 is disable.
Goog luck
Bogi Wu
"fredscuba" wrote:
> We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> machine with 16 GB of memory. I am trying to use more than the default 2GB of
> memory for SQL Server.
> I have added the /PAE switch to the boot.ini file on the server, configured
> SQL Server by issuing a
> sp_configure 'show advanced options', 1
> RECONFIGURE
> and a
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 14336
> RECONFIGURE
> GO
> However, it looks like SQL Server is till using less than 2GB of memory when
> running. I have run the sp_configure check on it's own and noticed that the
> config_value for AWE enabled is 1, but that the run_value is still 0.
> Could that be the problem? What do I have to do to fix this?
> I know I did restart the server after adding the settings (the setting for
> 'show advanced options' and 'max server memory' both show the same value for
> config and run_value. It is just the AWE enable setting that has a
> discrepancy.
> Should I set the 'max server memory' to less than 14 GB if the server has
> 16GB available? How much does the OS need?
> Thanks
> Fred|||OK, I did reboot the server and afterwards I could verify that the run_value
for 'AWE enabled' is now 1.
The 'min server memory' is set to 1024 (1 GB) and the 'max server memory'
is set to 10240 (10GB). The server has 16GB of memory, but I will be sharing
that with the OS and with a SAS application, so I thought that 10GB for SQL
Server is a good number to start with.
*HOWEVER* when I check the memory utilization on the server through the Task
Manager, it now shows that the process sqlservr.exe is only using 141,164 K
of memory - only about 138 MB!!
Why would this be? Could this be correct? The server is being used pretty
heavily right now - it is not a transaction heavy load, more a batch type
load with millions of records being updated in a batch.
My impression was that if AWE is enabled and PAE is used, that the memory
allocation is not dynamic anymore, but static, according to what you specify
in the max server memory setting.
Why would it then show such a low memory utilization by SQL Server? (It used
to hover around 1.7 GB before I enabled PAE and AWE).
Fred
"Andrew J. Kelly" wrote:
> And check to make sure the account sql server is running under has Lock
> Pages In Memory rights.
> --
> Andrew J. Kelly SQL MVP
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
> > The most obvious reason would be that you didn't actually restart SQL
> > Server. I would try that and see if it fixes it.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> > news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
> >> Andrew & Alejandro,
> >>
> >> I am running Server 2003 Enterprise Edition and SQL Server 2000
> >> Enterprise
> >> Edition.
> >>
> >> I think the problem is that the config_value for 'AWE enabled' is 1, but
> >> that the run_value is still 0.
> >>
> >> Why would that be? What do I have to do to fix this?
> >>
> >> I am fairly sure that I restarted the server after changing the AWE
> >> setting,
> >> but I can do it again after hours (it is a production server).
> >>
> >> Is there any reason why the 'AWE enabled' setting would stay at a
> >> run_value
> >> of 0, even after I try to set it with:
> >>
> >> sp_configure 'awe enabled', 1
> >> RECONFIGURE
> >>
> >>
> >> Fred
> >>
> >>
> >> "Andrew J. Kelly" wrote:
> >>
> >> Are you sure it is Enterprise Edition and not Std? What Edition is the
> >> OS?
> >> What does @.@.VERSION or xp_MSVer show? After you get it going I would
> >> start
> >> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
> >> and
> >> there is a little room to spare for other apps.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> >> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> >> > Alejandro,
> >> >
> >> > I did go through the instructions that are shown on the pages you
> >> > bookmarked
> >> > (see my original post).
> >> >
> >> > My question is: why is SQL Server still using less than 2GB of memory
> >> > even
> >> > after I have setup my boot.ini and enabled AWE and set the max server
> >> > memory?
> >> >
> >> > Fred
> >> >
> >> >
> >> > "Alejandro Mesa" wrote:
> >> >
> >> >> How to configure memory for more than 2 GB in SQL Server
> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >> >>
> >> >> Managing AWE Memory
> >> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >> >>
> >> >>
> >> >> AMB
> >> >>
> >> >>
> >> >> "fredscuba" wrote:
> >> >>
> >> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
> >> >> > Server
> >> >> > 2003
> >> >> > machine with 16 GB of memory. I am trying to use more than the
> >> >> > default
> >> >> > 2GB of
> >> >> > memory for SQL Server.
> >> >> >
> >> >> > I have added the /PAE switch to the boot.ini file on the server,
> >> >> > configured
> >> >> > SQL Server by issuing a
> >> >> >
> >> >> > sp_configure 'show advanced options', 1
> >> >> > RECONFIGURE
> >> >> >
> >> >> > and a
> >> >> >
> >> >> > sp_configure 'awe enabled', 1
> >> >> > RECONFIGURE
> >> >> > GO
> >> >> > sp_configure 'max server memory', 14336
> >> >> > RECONFIGURE
> >> >> > GO
> >> >> >
> >> >> > However, it looks like SQL Server is till using less than 2GB of
> >> >> > memory
> >> >> > when
> >> >> > running. I have run the sp_configure check on it's own and noticed
> >> >> > that
> >> >> > the
> >> >> > config_value for AWE enabled is 1, but that the run_value is still
> >> >> > 0.
> >> >> >
> >> >> > Could that be the problem? What do I have to do to fix this?
> >> >> >
> >> >> > I know I did restart the server after adding the settings (the
> >> >> > setting
> >> >> > for
> >> >> > 'show advanced options' and 'max server memory' both show the same
> >> >> > value for
> >> >> > config and run_value. It is just the AWE enable setting that has a
> >> >> > discrepancy.
> >> >> >
> >> >> > Should I set the 'max server memory' to less than 14 GB if the
> >> >> > server
> >> >> > has
> >> >> > 16GB available? How much does the OS need?
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >> > Fred
> >>
> >>
> >>
> >
> >
>
>|||Hi,
I followed the link you provided, but there is a note saying that "This
functionality is available only if you are running the Microsoft® Windows®
2000 operating system".
Can I or should I do it if I am running on Windows Server 2003?
Fred
"BogiWu" wrote:
> Hi
> Before you set AWE you need to set "Lock Pages In Memory" first.
> How to set the "Lock Pages In Memory", Please see URL
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servp_2vqh.asp
> By default SQL Seerver 2000 in Windows 2003 is disable.
> Goog luck
> Bogi Wu
> "fredscuba" wrote:
> > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > memory for SQL Server.
> >
> > I have added the /PAE switch to the boot.ini file on the server, configured
> > SQL Server by issuing a
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> >
> > and a
> >
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'max server memory', 14336
> > RECONFIGURE
> > GO
> >
> > However, it looks like SQL Server is till using less than 2GB of memory when
> > running. I have run the sp_configure check on it's own and noticed that the
> > config_value for AWE enabled is 1, but that the run_value is still 0.
> >
> > Could that be the problem? What do I have to do to fix this?
> >
> > I know I did restart the server after adding the settings (the setting for
> > 'show advanced options' and 'max server memory' both show the same value for
> > config and run_value. It is just the AWE enable setting that has a
> > discrepancy.
> >
> > Should I set the 'max server memory' to less than 14 GB if the server has
> > 16GB available? How much does the OS need?
> >
> > Thanks
> >
> > Fred|||Never mind - the account running SQL Server already has the ability to lock
pages in memory.
My problem now is that SQL Server does not seem to be using all of the
memory I set aside for it under the max server memory setting. (see my other
post from today)
Fred
"fredscuba" wrote:
> Hi,
> I followed the link you provided, but there is a note saying that "This
> functionality is available only if you are running the Microsoft® Windows®
> 2000 operating system".
> Can I or should I do it if I am running on Windows Server 2003?
>
> Fred
> "BogiWu" wrote:
> > Hi
> > Before you set AWE you need to set "Lock Pages In Memory" first.
> > How to set the "Lock Pages In Memory", Please see URL
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/howtosql/ht_servp_2vqh.asp
> > By default SQL Seerver 2000 in Windows 2003 is disable.
> >
> > Goog luck
> >
> > Bogi Wu
> > "fredscuba" wrote:
> >
> > > We are running SQL Server 2000 Enterprise Edition on a Windows Server 2003
> > > machine with 16 GB of memory. I am trying to use more than the default 2GB of
> > > memory for SQL Server.
> > >
> > > I have added the /PAE switch to the boot.ini file on the server, configured
> > > SQL Server by issuing a
> > >
> > > sp_configure 'show advanced options', 1
> > > RECONFIGURE
> > >
> > > and a
> > >
> > > sp_configure 'awe enabled', 1
> > > RECONFIGURE
> > > GO
> > > sp_configure 'max server memory', 14336
> > > RECONFIGURE
> > > GO
> > >
> > > However, it looks like SQL Server is till using less than 2GB of memory when
> > > running. I have run the sp_configure check on it's own and noticed that the
> > > config_value for AWE enabled is 1, but that the run_value is still 0.
> > >
> > > Could that be the problem? What do I have to do to fix this?
> > >
> > > I know I did restart the server after adding the settings (the setting for
> > > 'show advanced options' and 'max server memory' both show the same value for
> > > config and run_value. It is just the AWE enable setting that has a
> > > discrepancy.
> > >
> > > Should I set the 'max server memory' to less than 14 GB if the server has
> > > 16GB available? How much does the OS need?
> > >
> > > Thanks
> > >
> > > Fred|||Task Manager isn't PAE aware. Use Perf Mon.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:3AB99BA7-408F-4B05-B44B-DA2D78FE0053@.microsoft.com...
> OK, I did reboot the server and afterwards I could verify that the run_value
> for 'AWE enabled' is now 1.
> The 'min server memory' is set to 1024 (1 GB) and the 'max server memory'
> is set to 10240 (10GB). The server has 16GB of memory, but I will be sharing
> that with the OS and with a SAS application, so I thought that 10GB for SQL
> Server is a good number to start with.
> *HOWEVER* when I check the memory utilization on the server through the Task
> Manager, it now shows that the process sqlservr.exe is only using 141,164 K
> of memory - only about 138 MB!!
> Why would this be? Could this be correct? The server is being used pretty
> heavily right now - it is not a transaction heavy load, more a batch type
> load with millions of records being updated in a batch.
> My impression was that if AWE is enabled and PAE is used, that the memory
> allocation is not dynamic anymore, but static, according to what you specify
> in the max server memory setting.
> Why would it then show such a low memory utilization by SQL Server? (It used
> to hover around 1.7 GB before I enabled PAE and AWE).
>
> Fred
> "Andrew J. Kelly" wrote:
>> And check to make sure the account sql server is running under has Lock
>> Pages In Memory rights.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
>> > The most obvious reason would be that you didn't actually restart SQL
>> > Server. I would try that and see if it fixes it.
>> >
>> > --
>> > Andrew J. Kelly SQL MVP
>> >
>> >
>> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> > news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
>> >> Andrew & Alejandro,
>> >>
>> >> I am running Server 2003 Enterprise Edition and SQL Server 2000
>> >> Enterprise
>> >> Edition.
>> >>
>> >> I think the problem is that the config_value for 'AWE enabled' is 1, but
>> >> that the run_value is still 0.
>> >>
>> >> Why would that be? What do I have to do to fix this?
>> >>
>> >> I am fairly sure that I restarted the server after changing the AWE
>> >> setting,
>> >> but I can do it again after hours (it is a production server).
>> >>
>> >> Is there any reason why the 'AWE enabled' setting would stay at a
>> >> run_value
>> >> of 0, even after I try to set it with:
>> >>
>> >> sp_configure 'awe enabled', 1
>> >> RECONFIGURE
>> >>
>> >>
>> >> Fred
>> >>
>> >>
>> >> "Andrew J. Kelly" wrote:
>> >>
>> >> Are you sure it is Enterprise Edition and not Std? What Edition is the
>> >> OS?
>> >> What does @.@.VERSION or xp_MSVer show? After you get it going I would
>> >> start
>> >> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
>> >> and
>> >> there is a little room to spare for other apps.
>> >>
>> >> --
>> >> Andrew J. Kelly SQL MVP
>> >>
>> >>
>> >> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
>> >> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
>> >> > Alejandro,
>> >> >
>> >> > I did go through the instructions that are shown on the pages you
>> >> > bookmarked
>> >> > (see my original post).
>> >> >
>> >> > My question is: why is SQL Server still using less than 2GB of memory
>> >> > even
>> >> > after I have setup my boot.ini and enabled AWE and set the max server
>> >> > memory?
>> >> >
>> >> > Fred
>> >> >
>> >> >
>> >> > "Alejandro Mesa" wrote:
>> >> >
>> >> >> How to configure memory for more than 2 GB in SQL Server
>> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
>> >> >>
>> >> >> Managing AWE Memory
>> >> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
>> >> >>
>> >> >>
>> >> >> AMB
>> >> >>
>> >> >>
>> >> >> "fredscuba" wrote:
>> >> >>
>> >> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
>> >> >> > Server
>> >> >> > 2003
>> >> >> > machine with 16 GB of memory. I am trying to use more than the
>> >> >> > default
>> >> >> > 2GB of
>> >> >> > memory for SQL Server.
>> >> >> >
>> >> >> > I have added the /PAE switch to the boot.ini file on the server,
>> >> >> > configured
>> >> >> > SQL Server by issuing a
>> >> >> >
>> >> >> > sp_configure 'show advanced options', 1
>> >> >> > RECONFIGURE
>> >> >> >
>> >> >> > and a
>> >> >> >
>> >> >> > sp_configure 'awe enabled', 1
>> >> >> > RECONFIGURE
>> >> >> > GO
>> >> >> > sp_configure 'max server memory', 14336
>> >> >> > RECONFIGURE
>> >> >> > GO
>> >> >> >
>> >> >> > However, it looks like SQL Server is till using less than 2GB of
>> >> >> > memory
>> >> >> > when
>> >> >> > running. I have run the sp_configure check on it's own and noticed
>> >> >> > that
>> >> >> > the
>> >> >> > config_value for AWE enabled is 1, but that the run_value is still
>> >> >> > 0.
>> >> >> >
>> >> >> > Could that be the problem? What do I have to do to fix this?
>> >> >> >
>> >> >> > I know I did restart the server after adding the settings (the
>> >> >> > setting
>> >> >> > for
>> >> >> > 'show advanced options' and 'max server memory' both show the same
>> >> >> > value for
>> >> >> > config and run_value. It is just the AWE enable setting that has a
>> >> >> > discrepancy.
>> >> >> >
>> >> >> > Should I set the 'max server memory' to less than 14 GB if the
>> >> >> > server
>> >> >> > has
>> >> >> > 16GB available? How much does the OS need?
>> >> >> >
>> >> >> > Thanks
>> >> >> >
>> >> >> > Fred
>> >>
>> >>
>> >>
>> >
>> >
>>|||Thanks!
Perf Mon shows a static number for the memory assigned to SQL Server and it
matches what I set the max server memory setting to.
Fred
"Tibor Karaszi" wrote:
> Task Manager isn't PAE aware. Use Perf Mon.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:3AB99BA7-408F-4B05-B44B-DA2D78FE0053@.microsoft.com...
> > OK, I did reboot the server and afterwards I could verify that the run_value
> > for 'AWE enabled' is now 1.
> >
> > The 'min server memory' is set to 1024 (1 GB) and the 'max server memory'
> > is set to 10240 (10GB). The server has 16GB of memory, but I will be sharing
> > that with the OS and with a SAS application, so I thought that 10GB for SQL
> > Server is a good number to start with.
> >
> > *HOWEVER* when I check the memory utilization on the server through the Task
> > Manager, it now shows that the process sqlservr.exe is only using 141,164 K
> > of memory - only about 138 MB!!
> >
> > Why would this be? Could this be correct? The server is being used pretty
> > heavily right now - it is not a transaction heavy load, more a batch type
> > load with millions of records being updated in a batch.
> >
> > My impression was that if AWE is enabled and PAE is used, that the memory
> > allocation is not dynamic anymore, but static, according to what you specify
> > in the max server memory setting.
> >
> > Why would it then show such a low memory utilization by SQL Server? (It used
> > to hover around 1.7 GB before I enabled PAE and AWE).
> >
> >
> > Fred
> >
> > "Andrew J. Kelly" wrote:
> >
> >> And check to make sure the account sql server is running under has Lock
> >> Pages In Memory rights.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> >> news:u2cLo5lhFHA.576@.TK2MSFTNGP15.phx.gbl...
> >> > The most obvious reason would be that you didn't actually restart SQL
> >> > Server. I would try that and see if it fixes it.
> >> >
> >> > --
> >> > Andrew J. Kelly SQL MVP
> >> >
> >> >
> >> > "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> >> > news:27D53CE0-A064-4B3A-83CA-25293115FA99@.microsoft.com...
> >> >> Andrew & Alejandro,
> >> >>
> >> >> I am running Server 2003 Enterprise Edition and SQL Server 2000
> >> >> Enterprise
> >> >> Edition.
> >> >>
> >> >> I think the problem is that the config_value for 'AWE enabled' is 1, but
> >> >> that the run_value is still 0.
> >> >>
> >> >> Why would that be? What do I have to do to fix this?
> >> >>
> >> >> I am fairly sure that I restarted the server after changing the AWE
> >> >> setting,
> >> >> but I can do it again after hours (it is a production server).
> >> >>
> >> >> Is there any reason why the 'AWE enabled' setting would stay at a
> >> >> run_value
> >> >> of 0, even after I try to set it with:
> >> >>
> >> >> sp_configure 'awe enabled', 1
> >> >> RECONFIGURE
> >> >>
> >> >>
> >> >> Fred
> >> >>
> >> >>
> >> >> "Andrew J. Kelly" wrote:
> >> >>
> >> >> Are you sure it is Enterprise Edition and not Std? What Edition is the
> >> >> OS?
> >> >> What does @.@.VERSION or xp_MSVer show? After you get it going I would
> >> >> start
> >> >> out with 15 or 15.5GB instead of 16 just to make sure the OS has plenty
> >> >> and
> >> >> there is a little room to spare for other apps.
> >> >>
> >> >> --
> >> >> Andrew J. Kelly SQL MVP
> >> >>
> >> >>
> >> >> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> >> >> news:6007E2E5-304A-4C53-9A29-E061F3E439BB@.microsoft.com...
> >> >> > Alejandro,
> >> >> >
> >> >> > I did go through the instructions that are shown on the pages you
> >> >> > bookmarked
> >> >> > (see my original post).
> >> >> >
> >> >> > My question is: why is SQL Server still using less than 2GB of memory
> >> >> > even
> >> >> > after I have setup my boot.ini and enabled AWE and set the max server
> >> >> > memory?
> >> >> >
> >> >> > Fred
> >> >> >
> >> >> >
> >> >> > "Alejandro Mesa" wrote:
> >> >> >
> >> >> >> How to configure memory for more than 2 GB in SQL Server
> >> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
> >> >> >>
> >> >> >> Managing AWE Memory
> >> >> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1fnd.asp
> >> >> >>
> >> >> >>
> >> >> >> AMB
> >> >> >>
> >> >> >>
> >> >> >> "fredscuba" wrote:
> >> >> >>
> >> >> >> > We are running SQL Server 2000 Enterprise Edition on a Windows
> >> >> >> > Server
> >> >> >> > 2003
> >> >> >> > machine with 16 GB of memory. I am trying to use more than the
> >> >> >> > default
> >> >> >> > 2GB of
> >> >> >> > memory for SQL Server.
> >> >> >> >
> >> >> >> > I have added the /PAE switch to the boot.ini file on the server,
> >> >> >> > configured
> >> >> >> > SQL Server by issuing a
> >> >> >> >
> >> >> >> > sp_configure 'show advanced options', 1
> >> >> >> > RECONFIGURE
> >> >> >> >
> >> >> >> > and a
> >> >> >> >
> >> >> >> > sp_configure 'awe enabled', 1
> >> >> >> > RECONFIGURE
> >> >> >> > GO
> >> >> >> > sp_configure 'max server memory', 14336
> >> >> >> > RECONFIGURE
> >> >> >> > GO
> >> >> >> >
> >> >> >> > However, it looks like SQL Server is till using less than 2GB of
> >> >> >> > memory
> >> >> >> > when
> >> >> >> > running. I have run the sp_configure check on it's own and noticed
> >> >> >> > that
> >> >> >> > the
> >> >> >> > config_value for AWE enabled is 1, but that the run_value is still
> >> >> >> > 0.
> >> >> >> >
> >> >> >> > Could that be the problem? What do I have to do to fix this?
> >> >> >> >
> >> >> >> > I know I did restart the server after adding the settings (the
> >> >> >> > setting
> >> >> >> > for
> >> >> >> > 'show advanced options' and 'max server memory' both show the same
> >> >> >> > value for
> >> >> >> > config and run_value. It is just the AWE enable setting that has a
> >> >> >> > discrepancy.
> >> >> >> >
> >> >> >> > Should I set the 'max server memory' to less than 14 GB if the
> >> >> >> > server
> >> >> >> > has
> >> >> >> > 16GB available? How much does the OS need?
> >> >> >> >
> >> >> >> > Thanks
> >> >> >> >
> >> >> >> > Fred
> >> >>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>