We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editions/64bit/sql64bitadvantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3 GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Server to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegr oups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editions/64bit/sql64bitadvantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
Showing posts with label awe. Show all posts
Showing posts with label awe. Show all posts
Sunday, March 11, 2012
AWE? / Windows 2003 R2 x64 / SQL Server 2000 x86 / 8GB RAM
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly learned that SQL 2000 x64 can only be installed on 64-bit Intel Itanium (IA64) servers, so were forced to install the 32bit x86 version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no longer need to set the /3GB and /PAE switches because all of the memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx AWE is a set of memory management extensions to the Microsoft Win32 API that allows applications to address memory beyond the 4GB limitation. Using AWE, applications can acquire physical memory as nonpaged memory, and then dynamically map views of the nonpaged memory to the 32-bit address space.32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3
GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Se
rver to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegroups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no longer need to set the /3GB and /PAE switches because all of the memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx AWE is a set of memory management extensions to the Microsoft Win32 API that allows applications to address memory beyond the 4GB limitation. Using AWE, applications can acquire physical memory as nonpaged memory, and then dynamically map views of the nonpaged memory to the 32-bit address space.32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3
GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Se
rver to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegroups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
AWE, SQL Server Enterprise, W2k STANDARD + 4GB RAM
Hi
Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to work (there seemed to be some doubt). I have reserved 3.5GB max server memory, and it has been allocated. The AWE counters in perfmon also seem to indicate it is functioning.
Does anyone have any experience with this configuration (good or bad)?
Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory doesn't appear to be of any use.
RegardsHi Stuart,
Not sure what you have done yet, but refers to the following article for
configuring AWE on SQL Server
HOW TO: Configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/defaul...kb;en-us;274750
On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
> Hi
> Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to
> work (there seemed to be some doubt). I have reserved 3.5GB max server
> memory, and it has been allocated. The AWE counters in perfmon also
> seem to indicate it is functioning.
> Does anyone have any experience with this configuration (good or bad)?
> Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory
> doesn't appear to be of any use.
> Regards
> Stuart|||Thanks - have read the MS articles (they often seem contradictory as
to whether AWE would work on W2k Server Standard)
However, even though AWE it does work on W2K server, there seems to be
some doubt as to whether there is any point in doing this, e.g.
http://www.sql-server-performance.com/awe_memory.asp says should leave
AWE off for my config.
To date, the config is looking quite good - enabling AWE has doubled
the available RAM to SQL and the Page Life Expectancy has gone up to
about 3 hours (up from a few seconds)
.
Regards
Stuart
Yih-Yoon Lee <yihyoon@.hotmail.com> wrote in message news:<1lywgm6zbxldi.sdsrs0dj91ss$.dlg@.4
0tude.net>...
> Hi Stuart,
> Not sure what you have done yet, but refers to the following article for
> configuring AWE on SQL Server
> HOW TO: Configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/defaul...kb;en-us;274750
> On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
>
Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to work (there seemed to be some doubt). I have reserved 3.5GB max server memory, and it has been allocated. The AWE counters in perfmon also seem to indicate it is functioning.
Does anyone have any experience with this configuration (good or bad)?
Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory doesn't appear to be of any use.
RegardsHi Stuart,
Not sure what you have done yet, but refers to the following article for
configuring AWE on SQL Server
HOW TO: Configure memory for more than 2 GB in SQL Server
http://support.microsoft.com/defaul...kb;en-us;274750
On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
> Hi
> Enabling AWE on SQL Enterprise Ed on a W2K STANDARD ed does appear to
> work (there seemed to be some doubt). I have reserved 3.5GB max server
> memory, and it has been allocated. The AWE counters in perfmon also
> seem to indicate it is functioning.
> Does anyone have any experience with this configuration (good or bad)?
> Also, any tips as to monitor memory usage - SQLServer/SQL Cache Memory
> doesn't appear to be of any use.
> Regards
> Stuart|||Thanks - have read the MS articles (they often seem contradictory as
to whether AWE would work on W2k Server Standard)
However, even though AWE it does work on W2K server, there seems to be
some doubt as to whether there is any point in doing this, e.g.
http://www.sql-server-performance.com/awe_memory.asp says should leave
AWE off for my config.
To date, the config is looking quite good - enabling AWE has doubled
the available RAM to SQL and the Page Life Expectancy has gone up to
about 3 hours (up from a few seconds)
.Regards
Stuart
Yih-Yoon Lee <yihyoon@.hotmail.com> wrote in message news:<1lywgm6zbxldi.sdsrs0dj91ss$.dlg@.4
0tude.net>...
> Hi Stuart,
> Not sure what you have done yet, but refers to the following article for
> configuring AWE on SQL Server
> HOW TO: Configure memory for more than 2 GB in SQL Server
> http://support.microsoft.com/defaul...kb;en-us;274750
> On 24 Mar 2004 08:04:17 -0800, Stuart wrote:
>
AWE, 3GB and SQL Boost
Please help. Just installed the SQL 2005 enterprise on 2003 standard server with /3GB switch.
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.
George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>
|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...[vbcol=seagreen]
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
[vbcol=seagreen]
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
|||Yes. To be honest, it is vague as some other Microsoft documents. Not sure
how to interpret the doc 100%.
So far, I understand that as long as I have no more than 4GB, I can dedicate
3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
Boot.ini. My understanding was not to use PAE or AWE.
"Chris Wood" wrote:
> George,
> Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
>
>
|||George,
You are indicating that 2 Gig is the ceiling on your machine. This will
always be the case if you have the Standard Edition as opposed to the
Enterprise Edition of SQL Server 2000. You didn't indicate you were running
2005 which does not have this limitation.
I made this mistake myself, adding 6 GIG to a Windows 2000 Advanced Server.
We still run at 2 GIG with the Standard Edition. We are using the boot.ini
switch to enable Windows 2000 Advanced to access above the 4 Gig mark which
is the limit on Windows 2000 without the switch. 2003 server has similar
requirements, but I think it starts at 16 gig so there should not be a
problem on the boot.ini for a 4 GIG machine. It is only the fact that you
may be using the Standard Edition.
Regards,
Jamie
"George" wrote:
[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
|||/3GB is a boot.ini setting. Not need to configure anything inside SQL Server
for this.
Linchi
"George" wrote:
[vbcol=seagreen]
> Thank you. I checked my prvious installations and you are right. I don't have
> it on.
> Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
> other switch in addition?
> If I put same valuses in both min and max memory, would that mean it is now
> FIXED MEMORY SIZE assigned vs dynamically when there is a range?
> SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
> sure you know of that just making a point)
> "Linchi Shea" wrote:
|||I have some empirical data on how much buffer pool mmeory a SQL instance
could consume with various settings of 3GB and AWE
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
Linchi
"George" wrote:
[vbcol=seagreen]
> Yes. To be honest, it is vague as some other Microsoft documents. Not sure
> how to interpret the doc 100%.
> So far, I understand that as long as I have no more than 4GB, I can dedicate
> 3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
> Boot.ini. My understanding was not to use PAE or AWE.
> "Chris Wood" wrote:
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.
George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>
|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...[vbcol=seagreen]
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
[vbcol=seagreen]
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
|||Yes. To be honest, it is vague as some other Microsoft documents. Not sure
how to interpret the doc 100%.
So far, I understand that as long as I have no more than 4GB, I can dedicate
3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
Boot.ini. My understanding was not to use PAE or AWE.
"Chris Wood" wrote:
> George,
> Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
>
>
|||George,
You are indicating that 2 Gig is the ceiling on your machine. This will
always be the case if you have the Standard Edition as opposed to the
Enterprise Edition of SQL Server 2000. You didn't indicate you were running
2005 which does not have this limitation.
I made this mistake myself, adding 6 GIG to a Windows 2000 Advanced Server.
We still run at 2 GIG with the Standard Edition. We are using the boot.ini
switch to enable Windows 2000 Advanced to access above the 4 Gig mark which
is the limit on Windows 2000 without the switch. 2003 server has similar
requirements, but I think it starts at 16 gig so there should not be a
problem on the boot.ini for a 4 GIG machine. It is only the fact that you
may be using the Standard Edition.
Regards,
Jamie
"George" wrote:
[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
|||/3GB is a boot.ini setting. Not need to configure anything inside SQL Server
for this.
Linchi
"George" wrote:
[vbcol=seagreen]
> Thank you. I checked my prvious installations and you are right. I don't have
> it on.
> Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
> other switch in addition?
> If I put same valuses in both min and max memory, would that mean it is now
> FIXED MEMORY SIZE assigned vs dynamically when there is a range?
> SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
> sure you know of that just making a point)
> "Linchi Shea" wrote:
|||I have some empirical data on how much buffer pool mmeory a SQL instance
could consume with various settings of 3GB and AWE
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
Linchi
"George" wrote:
[vbcol=seagreen]
> Yes. To be honest, it is vague as some other Microsoft documents. Not sure
> how to interpret the doc 100%.
> So far, I understand that as long as I have no more than 4GB, I can dedicate
> 3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
> Boot.ini. My understanding was not to use PAE or AWE.
> "Chris Wood" wrote:
AWE, 3GB and SQL Boost
Please help. Just installed the SQL 2005 enterprise on 2003 standard server with /3GB switch.
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>|||4GB on the server and 3GB to SQL
"Chris Wood" wrote:
> George,
> How much memory do you have on the server? How much do you want to give to
> SQL?
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > server
> > with /3GB switch.
> > Now, in SQL there is an AWE option. Do I need to check that off and where
> > do
> > I set the memory manualy and not dinamicly?
> > Also, do I boost SQL priority in processors?
> > Can you please help and give some other tunning pointers? I set couple of
> > boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> > processors and other fine tunning steps. Thanks in advance.
> >
>
>|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
>> George,
>> How much memory do you have on the server? How much do you want to give
>> to
>> SQL?
>> Chris
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
>> > server
>> > with /3GB switch.
>> > Now, in SQL there is an AWE option. Do I need to check that off and
>> > where
>> > do
>> > I set the memory manualy and not dinamicly?
>> > Also, do I boost SQL priority in processors?
>> > Can you please help and give some other tunning pointers? I set couple
>> > of
>> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
>> > on
>> > processors and other fine tunning steps. Thanks in advance.
>> >
>>|||Ok. So
1. Set the 3GB switch in Boot.ini (did this before SQL installation)
2. Run the sp_configure and set it to 2.5
Please confirm. Also, is that check for AWE in GUI same as the sp command
via QA?
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > 4GB on the server and 3GB to SQL
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> How much memory do you have on the server? How much do you want to give
> >> to
> >> SQL?
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> > server
> >> > with /3GB switch.
> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> > where
> >> > do
> >> > I set the memory manualy and not dinamicly?
> >> > Also, do I boost SQL priority in processors?
> >> > Can you please help and give some other tunning pointers? I set couple
> >> > of
> >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> >> > on
> >> > processors and other fine tunning steps. Thanks in advance.
> >> >
> >>
> >>
> >>
>
>|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
> > George,
> >
> > On server 2003 the switches should be set by the O/S. You will need to
> > configure AWE using sp_configure and then set max and min memory. I would
> > try with 2.5Gb first before you see if you can move up to 3Gb.
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > 4GB on the server and 3GB to SQL
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> How much memory do you have on the server? How much do you want to give
> > >> to
> > >> SQL?
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> > server
> > >> > with /3GB switch.
> > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> > where
> > >> > do
> > >> > I set the memory manualy and not dinamicly?
> > >> > Also, do I boost SQL priority in processors?
> > >> > Can you please help and give some other tunning pointers? I set couple
> > >> > of
> > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > >> > on
> > >> > processors and other fine tunning steps. Thanks in advance.
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||Thank you. I checked my prvious installations and you are right. I don't have
it on.
Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
other switch in addition?
If I put same valuses in both min and max memory, would that mean it is now
FIXED MEMORY SIZE assigned vs dynamically when there is a range?
SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
sure you know of that just making a point)
"Linchi Shea" wrote:
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Books
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operating
> system and network functions, resulting in problems shutting down SQL Server
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
> > Ok. So
> > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > 2. Run the sp_configure and set it to 2.5
> >
> > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > via QA?
> >
> > "Chris Wood" wrote:
> >
> > > George,
> > >
> > > On server 2003 the switches should be set by the O/S. You will need to
> > > configure AWE using sp_configure and then set max and min memory. I would
> > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > >
> > > Chris
> > >
> > > "George" <George@.discussions.microsoft.com> wrote in message
> > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > 4GB on the server and 3GB to SQL
> > > >
> > > > "Chris Wood" wrote:
> > > >
> > > >> George,
> > > >>
> > > >> How much memory do you have on the server? How much do you want to give
> > > >> to
> > > >> SQL?
> > > >>
> > > >> Chris
> > > >>
> > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > >> > server
> > > >> > with /3GB switch.
> > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > >> > where
> > > >> > do
> > > >> > I set the memory manualy and not dinamicly?
> > > >> > Also, do I boost SQL priority in processors?
> > > >> > Can you please help and give some other tunning pointers? I set couple
> > > >> > of
> > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > >> > on
> > > >> > processors and other fine tunning steps. Thanks in advance.
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Can anyone please confirm I should keep the 3GB in boot.ini and enable AWE in
SQL?
"Linchi Shea" wrote:
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Books
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operating
> system and network functions, resulting in problems shutting down SQL Server
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
> > Ok. So
> > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > 2. Run the sp_configure and set it to 2.5
> >
> > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > via QA?
> >
> > "Chris Wood" wrote:
> >
> > > George,
> > >
> > > On server 2003 the switches should be set by the O/S. You will need to
> > > configure AWE using sp_configure and then set max and min memory. I would
> > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > >
> > > Chris
> > >
> > > "George" <George@.discussions.microsoft.com> wrote in message
> > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > 4GB on the server and 3GB to SQL
> > > >
> > > > "Chris Wood" wrote:
> > > >
> > > >> George,
> > > >>
> > > >> How much memory do you have on the server? How much do you want to give
> > > >> to
> > > >> SQL?
> > > >>
> > > >> Chris
> > > >>
> > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > >> > server
> > > >> > with /3GB switch.
> > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > >> > where
> > > >> > do
> > > >> > I set the memory manualy and not dinamicly?
> > > >> > Also, do I boost SQL priority in processors?
> > > >> > Can you please help and give some other tunning pointers? I set couple
> > > >> > of
> > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > >> > on
> > > >> > processors and other fine tunning steps. Thanks in advance.
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Chris, thanks. I can not go higher than 2.1 GB. Please help.
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > 4GB on the server and 3GB to SQL
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> How much memory do you have on the server? How much do you want to give
> >> to
> >> SQL?
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> > server
> >> > with /3GB switch.
> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> > where
> >> > do
> >> > I set the memory manualy and not dinamicly?
> >> > Also, do I boost SQL priority in processors?
> >> > Can you please help and give some other tunning pointers? I set couple
> >> > of
> >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> >> > on
> >> > processors and other fine tunning steps. Thanks in advance.
> >> >
> >>
> >>
> >>
>
>|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
>> George,
>> On server 2003 the switches should be set by the O/S. You will need to
>> configure AWE using sp_configure and then set max and min memory. I would
>> try with 2.5Gb first before you see if you can move up to 3Gb.
>> Chris
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>> > 4GB on the server and 3GB to SQL
>> >
>> > "Chris Wood" wrote:
>> >
>> >> George,
>> >>
>> >> How much memory do you have on the server? How much do you want to
>> >> give
>> >> to
>> >> SQL?
>> >>
>> >> Chris
>> >>
>> >> "George" <George@.discussions.microsoft.com> wrote in message
>> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
>> >> > server
>> >> > with /3GB switch.
>> >> > Now, in SQL there is an AWE option. Do I need to check that off and
>> >> > where
>> >> > do
>> >> > I set the memory manualy and not dinamicly?
>> >> > Also, do I boost SQL priority in processors?
>> >> > Can you please help and give some other tunning pointers? I set
>> >> > couple
>> >> > of
>> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
>> >> > priority
>> >> > on
>> >> > processors and other fine tunning steps. Thanks in advance.
>> >> >
>> >>
>> >>
>> >>
>>|||Yes. To be honest, it is vague as some other Microsoft documents. Not sure
how to interpret the doc 100%.
So far, I understand that as long as I have no more than 4GB, I can dedicate
3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
Boot.ini. My understanding was not to use PAE or AWE.
"Chris Wood" wrote:
> George,
> Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> > Chris, thanks. I can not go higher than 2.1 GB. Please help.
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> On server 2003 the switches should be set by the O/S. You will need to
> >> configure AWE using sp_configure and then set max and min memory. I would
> >> try with 2.5Gb first before you see if you can move up to 3Gb.
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> >> > 4GB on the server and 3GB to SQL
> >> >
> >> > "Chris Wood" wrote:
> >> >
> >> >> George,
> >> >>
> >> >> How much memory do you have on the server? How much do you want to
> >> >> give
> >> >> to
> >> >> SQL?
> >> >>
> >> >> Chris
> >> >>
> >> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> >> > server
> >> >> > with /3GB switch.
> >> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> >> > where
> >> >> > do
> >> >> > I set the memory manualy and not dinamicly?
> >> >> > Also, do I boost SQL priority in processors?
> >> >> > Can you please help and give some other tunning pointers? I set
> >> >> > couple
> >> >> > of
> >> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
> >> >> > priority
> >> >> > on
> >> >> > processors and other fine tunning steps. Thanks in advance.
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||George,
You are indicating that 2 Gig is the ceiling on your machine. This will
always be the case if you have the Standard Edition as opposed to the
Enterprise Edition of SQL Server 2000. You didn't indicate you were running
2005 which does not have this limitation.
I made this mistake myself, adding 6 GIG to a Windows 2000 Advanced Server.
We still run at 2 GIG with the Standard Edition. We are using the boot.ini
switch to enable Windows 2000 Advanced to access above the 4 Gig mark which
is the limit on Windows 2000 without the switch. 2003 server has similar
requirements, but I think it starts at 16 gig so there should not be a
problem on the boot.ini for a 4 GIG machine. It is only the fact that you
may be using the Standard Edition.
--
Regards,
Jamie
"George" wrote:
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
> > George,
> >
> > On server 2003 the switches should be set by the O/S. You will need to
> > configure AWE using sp_configure and then set max and min memory. I would
> > try with 2.5Gb first before you see if you can move up to 3Gb.
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > 4GB on the server and 3GB to SQL
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> How much memory do you have on the server? How much do you want to give
> > >> to
> > >> SQL?
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> > server
> > >> > with /3GB switch.
> > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> > where
> > >> > do
> > >> > I set the memory manualy and not dinamicly?
> > >> > Also, do I boost SQL priority in processors?
> > >> > Can you please help and give some other tunning pointers? I set couple
> > >> > of
> > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > >> > on
> > >> > processors and other fine tunning steps. Thanks in advance.
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||/3GB is a boot.ini setting. Not need to configure anything inside SQL Server
for this.
Linchi
"George" wrote:
> Thank you. I checked my prvious installations and you are right. I don't have
> it on.
> Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
> other switch in addition?
> If I put same valuses in both min and max memory, would that mean it is now
> FIXED MEMORY SIZE assigned vs dynamically when there is a range?
> SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
> sure you know of that just making a point)
> "Linchi Shea" wrote:
> > Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> > same as executing the following T-SQL code:
> >
> > EXEC sys.sp_configure N'awe enabled', N'1'
> > RECONFIGURE WITH OVERRIDE
> >
> > BTW, you almost never should boost the SQL process priority. In fact, Books
> > Online comes with the following warning:
> >
> > "Raising the priority too high may drain resources from essential operating
> > system and network functions, resulting in problems shutting down SQL Server
> > or using other operating system tasks on the server."
> >
> > Linchi
> >
> > "George" wrote:
> >
> > > Ok. So
> > > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > > 2. Run the sp_configure and set it to 2.5
> > >
> > > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > > via QA?
> > >
> > > "Chris Wood" wrote:
> > >
> > > > George,
> > > >
> > > > On server 2003 the switches should be set by the O/S. You will need to
> > > > configure AWE using sp_configure and then set max and min memory. I would
> > > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > > >
> > > > Chris
> > > >
> > > > "George" <George@.discussions.microsoft.com> wrote in message
> > > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > > 4GB on the server and 3GB to SQL
> > > > >
> > > > > "Chris Wood" wrote:
> > > > >
> > > > >> George,
> > > > >>
> > > > >> How much memory do you have on the server? How much do you want to give
> > > > >> to
> > > > >> SQL?
> > > > >>
> > > > >> Chris
> > > > >>
> > > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > > >> > server
> > > > >> > with /3GB switch.
> > > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > > >> > where
> > > > >> > do
> > > > >> > I set the memory manualy and not dinamicly?
> > > > >> > Also, do I boost SQL priority in processors?
> > > > >> > Can you please help and give some other tunning pointers? I set couple
> > > > >> > of
> > > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > > >> > on
> > > > >> > processors and other fine tunning steps. Thanks in advance.
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >|||I have some empirical data on how much buffer pool mmeory a SQL instance
could consume with various settings of 3GB and AWE
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
Linchi
"George" wrote:
> Yes. To be honest, it is vague as some other Microsoft documents. Not sure
> how to interpret the doc 100%.
> So far, I understand that as long as I have no more than 4GB, I can dedicate
> 3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
> Boot.ini. My understanding was not to use PAE or AWE.
> "Chris Wood" wrote:
> > George,
> >
> > Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> > > Chris, thanks. I can not go higher than 2.1 GB. Please help.
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> On server 2003 the switches should be set by the O/S. You will need to
> > >> configure AWE using sp_configure and then set max and min memory. I would
> > >> try with 2.5Gb first before you see if you can move up to 3Gb.
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > >> > 4GB on the server and 3GB to SQL
> > >> >
> > >> > "Chris Wood" wrote:
> > >> >
> > >> >> George,
> > >> >>
> > >> >> How much memory do you have on the server? How much do you want to
> > >> >> give
> > >> >> to
> > >> >> SQL?
> > >> >>
> > >> >> Chris
> > >> >>
> > >> >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> >> > server
> > >> >> > with /3GB switch.
> > >> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> >> > where
> > >> >> > do
> > >> >> > I set the memory manualy and not dinamicly?
> > >> >> > Also, do I boost SQL priority in processors?
> > >> >> > Can you please help and give some other tunning pointers? I set
> > >> >> > couple
> > >> >> > of
> > >> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
> > >> >> > priority
> > >> >> > on
> > >> >> > processors and other fine tunning steps. Thanks in advance.
> > >> >> >
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> > >>
> >
> >
> >
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>|||4GB on the server and 3GB to SQL
"Chris Wood" wrote:
> George,
> How much memory do you have on the server? How much do you want to give to
> SQL?
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > server
> > with /3GB switch.
> > Now, in SQL there is an AWE option. Do I need to check that off and where
> > do
> > I set the memory manualy and not dinamicly?
> > Also, do I boost SQL priority in processors?
> > Can you please help and give some other tunning pointers? I set couple of
> > boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> > processors and other fine tunning steps. Thanks in advance.
> >
>
>|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
>> George,
>> How much memory do you have on the server? How much do you want to give
>> to
>> SQL?
>> Chris
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
>> > server
>> > with /3GB switch.
>> > Now, in SQL there is an AWE option. Do I need to check that off and
>> > where
>> > do
>> > I set the memory manualy and not dinamicly?
>> > Also, do I boost SQL priority in processors?
>> > Can you please help and give some other tunning pointers? I set couple
>> > of
>> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
>> > on
>> > processors and other fine tunning steps. Thanks in advance.
>> >
>>|||Ok. So
1. Set the 3GB switch in Boot.ini (did this before SQL installation)
2. Run the sp_configure and set it to 2.5
Please confirm. Also, is that check for AWE in GUI same as the sp command
via QA?
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > 4GB on the server and 3GB to SQL
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> How much memory do you have on the server? How much do you want to give
> >> to
> >> SQL?
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> > server
> >> > with /3GB switch.
> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> > where
> >> > do
> >> > I set the memory manualy and not dinamicly?
> >> > Also, do I boost SQL priority in processors?
> >> > Can you please help and give some other tunning pointers? I set couple
> >> > of
> >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> >> > on
> >> > processors and other fine tunning steps. Thanks in advance.
> >> >
> >>
> >>
> >>
>
>|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
> > George,
> >
> > On server 2003 the switches should be set by the O/S. You will need to
> > configure AWE using sp_configure and then set max and min memory. I would
> > try with 2.5Gb first before you see if you can move up to 3Gb.
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > 4GB on the server and 3GB to SQL
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> How much memory do you have on the server? How much do you want to give
> > >> to
> > >> SQL?
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> > server
> > >> > with /3GB switch.
> > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> > where
> > >> > do
> > >> > I set the memory manualy and not dinamicly?
> > >> > Also, do I boost SQL priority in processors?
> > >> > Can you please help and give some other tunning pointers? I set couple
> > >> > of
> > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > >> > on
> > >> > processors and other fine tunning steps. Thanks in advance.
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||Thank you. I checked my prvious installations and you are right. I don't have
it on.
Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
other switch in addition?
If I put same valuses in both min and max memory, would that mean it is now
FIXED MEMORY SIZE assigned vs dynamically when there is a range?
SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
sure you know of that just making a point)
"Linchi Shea" wrote:
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Books
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operating
> system and network functions, resulting in problems shutting down SQL Server
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
> > Ok. So
> > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > 2. Run the sp_configure and set it to 2.5
> >
> > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > via QA?
> >
> > "Chris Wood" wrote:
> >
> > > George,
> > >
> > > On server 2003 the switches should be set by the O/S. You will need to
> > > configure AWE using sp_configure and then set max and min memory. I would
> > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > >
> > > Chris
> > >
> > > "George" <George@.discussions.microsoft.com> wrote in message
> > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > 4GB on the server and 3GB to SQL
> > > >
> > > > "Chris Wood" wrote:
> > > >
> > > >> George,
> > > >>
> > > >> How much memory do you have on the server? How much do you want to give
> > > >> to
> > > >> SQL?
> > > >>
> > > >> Chris
> > > >>
> > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > >> > server
> > > >> > with /3GB switch.
> > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > >> > where
> > > >> > do
> > > >> > I set the memory manualy and not dinamicly?
> > > >> > Also, do I boost SQL priority in processors?
> > > >> > Can you please help and give some other tunning pointers? I set couple
> > > >> > of
> > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > >> > on
> > > >> > processors and other fine tunning steps. Thanks in advance.
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Can anyone please confirm I should keep the 3GB in boot.ini and enable AWE in
SQL?
"Linchi Shea" wrote:
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Books
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operating
> system and network functions, resulting in problems shutting down SQL Server
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
> > Ok. So
> > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > 2. Run the sp_configure and set it to 2.5
> >
> > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > via QA?
> >
> > "Chris Wood" wrote:
> >
> > > George,
> > >
> > > On server 2003 the switches should be set by the O/S. You will need to
> > > configure AWE using sp_configure and then set max and min memory. I would
> > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > >
> > > Chris
> > >
> > > "George" <George@.discussions.microsoft.com> wrote in message
> > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > 4GB on the server and 3GB to SQL
> > > >
> > > > "Chris Wood" wrote:
> > > >
> > > >> George,
> > > >>
> > > >> How much memory do you have on the server? How much do you want to give
> > > >> to
> > > >> SQL?
> > > >>
> > > >> Chris
> > > >>
> > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > >> > server
> > > >> > with /3GB switch.
> > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > >> > where
> > > >> > do
> > > >> > I set the memory manualy and not dinamicly?
> > > >> > Also, do I boost SQL priority in processors?
> > > >> > Can you please help and give some other tunning pointers? I set couple
> > > >> > of
> > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > >> > on
> > > >> > processors and other fine tunning steps. Thanks in advance.
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Chris, thanks. I can not go higher than 2.1 GB. Please help.
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > 4GB on the server and 3GB to SQL
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> How much memory do you have on the server? How much do you want to give
> >> to
> >> SQL?
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> > server
> >> > with /3GB switch.
> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> > where
> >> > do
> >> > I set the memory manualy and not dinamicly?
> >> > Also, do I boost SQL priority in processors?
> >> > Can you please help and give some other tunning pointers? I set couple
> >> > of
> >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> >> > on
> >> > processors and other fine tunning steps. Thanks in advance.
> >> >
> >>
> >>
> >>
>
>|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
>> George,
>> On server 2003 the switches should be set by the O/S. You will need to
>> configure AWE using sp_configure and then set max and min memory. I would
>> try with 2.5Gb first before you see if you can move up to 3Gb.
>> Chris
>> "George" <George@.discussions.microsoft.com> wrote in message
>> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>> > 4GB on the server and 3GB to SQL
>> >
>> > "Chris Wood" wrote:
>> >
>> >> George,
>> >>
>> >> How much memory do you have on the server? How much do you want to
>> >> give
>> >> to
>> >> SQL?
>> >>
>> >> Chris
>> >>
>> >> "George" <George@.discussions.microsoft.com> wrote in message
>> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
>> >> > server
>> >> > with /3GB switch.
>> >> > Now, in SQL there is an AWE option. Do I need to check that off and
>> >> > where
>> >> > do
>> >> > I set the memory manualy and not dinamicly?
>> >> > Also, do I boost SQL priority in processors?
>> >> > Can you please help and give some other tunning pointers? I set
>> >> > couple
>> >> > of
>> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
>> >> > priority
>> >> > on
>> >> > processors and other fine tunning steps. Thanks in advance.
>> >> >
>> >>
>> >>
>> >>
>>|||Yes. To be honest, it is vague as some other Microsoft documents. Not sure
how to interpret the doc 100%.
So far, I understand that as long as I have no more than 4GB, I can dedicate
3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
Boot.ini. My understanding was not to use PAE or AWE.
"Chris Wood" wrote:
> George,
> Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> > Chris, thanks. I can not go higher than 2.1 GB. Please help.
> >
> > "Chris Wood" wrote:
> >
> >> George,
> >>
> >> On server 2003 the switches should be set by the O/S. You will need to
> >> configure AWE using sp_configure and then set max and min memory. I would
> >> try with 2.5Gb first before you see if you can move up to 3Gb.
> >>
> >> Chris
> >>
> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> >> > 4GB on the server and 3GB to SQL
> >> >
> >> > "Chris Wood" wrote:
> >> >
> >> >> George,
> >> >>
> >> >> How much memory do you have on the server? How much do you want to
> >> >> give
> >> >> to
> >> >> SQL?
> >> >>
> >> >> Chris
> >> >>
> >> >> "George" <George@.discussions.microsoft.com> wrote in message
> >> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> >> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> >> >> > server
> >> >> > with /3GB switch.
> >> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> >> >> > where
> >> >> > do
> >> >> > I set the memory manualy and not dinamicly?
> >> >> > Also, do I boost SQL priority in processors?
> >> >> > Can you please help and give some other tunning pointers? I set
> >> >> > couple
> >> >> > of
> >> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
> >> >> > priority
> >> >> > on
> >> >> > processors and other fine tunning steps. Thanks in advance.
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||George,
You are indicating that 2 Gig is the ceiling on your machine. This will
always be the case if you have the Standard Edition as opposed to the
Enterprise Edition of SQL Server 2000. You didn't indicate you were running
2005 which does not have this limitation.
I made this mistake myself, adding 6 GIG to a Windows 2000 Advanced Server.
We still run at 2 GIG with the Standard Edition. We are using the boot.ini
switch to enable Windows 2000 Advanced to access above the 4 Gig mark which
is the limit on Windows 2000 without the switch. 2003 server has similar
requirements, but I think it starts at 16 gig so there should not be a
problem on the boot.ini for a 4 GIG machine. It is only the fact that you
may be using the Standard Edition.
--
Regards,
Jamie
"George" wrote:
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
> > George,
> >
> > On server 2003 the switches should be set by the O/S. You will need to
> > configure AWE using sp_configure and then set max and min memory. I would
> > try with 2.5Gb first before you see if you can move up to 3Gb.
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > 4GB on the server and 3GB to SQL
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> How much memory do you have on the server? How much do you want to give
> > >> to
> > >> SQL?
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> > server
> > >> > with /3GB switch.
> > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> > where
> > >> > do
> > >> > I set the memory manualy and not dinamicly?
> > >> > Also, do I boost SQL priority in processors?
> > >> > Can you please help and give some other tunning pointers? I set couple
> > >> > of
> > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > >> > on
> > >> > processors and other fine tunning steps. Thanks in advance.
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||/3GB is a boot.ini setting. Not need to configure anything inside SQL Server
for this.
Linchi
"George" wrote:
> Thank you. I checked my prvious installations and you are right. I don't have
> it on.
> Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
> other switch in addition?
> If I put same valuses in both min and max memory, would that mean it is now
> FIXED MEMORY SIZE assigned vs dynamically when there is a range?
> SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
> sure you know of that just making a point)
> "Linchi Shea" wrote:
> > Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
> > same as executing the following T-SQL code:
> >
> > EXEC sys.sp_configure N'awe enabled', N'1'
> > RECONFIGURE WITH OVERRIDE
> >
> > BTW, you almost never should boost the SQL process priority. In fact, Books
> > Online comes with the following warning:
> >
> > "Raising the priority too high may drain resources from essential operating
> > system and network functions, resulting in problems shutting down SQL Server
> > or using other operating system tasks on the server."
> >
> > Linchi
> >
> > "George" wrote:
> >
> > > Ok. So
> > > 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> > > 2. Run the sp_configure and set it to 2.5
> > >
> > > Please confirm. Also, is that check for AWE in GUI same as the sp command
> > > via QA?
> > >
> > > "Chris Wood" wrote:
> > >
> > > > George,
> > > >
> > > > On server 2003 the switches should be set by the O/S. You will need to
> > > > configure AWE using sp_configure and then set max and min memory. I would
> > > > try with 2.5Gb first before you see if you can move up to 3Gb.
> > > >
> > > > Chris
> > > >
> > > > "George" <George@.discussions.microsoft.com> wrote in message
> > > > news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > > > > 4GB on the server and 3GB to SQL
> > > > >
> > > > > "Chris Wood" wrote:
> > > > >
> > > > >> George,
> > > > >>
> > > > >> How much memory do you have on the server? How much do you want to give
> > > > >> to
> > > > >> SQL?
> > > > >>
> > > > >> Chris
> > > > >>
> > > > >> "George" <George@.discussions.microsoft.com> wrote in message
> > > > >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > > > >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > > > >> > server
> > > > >> > with /3GB switch.
> > > > >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > > > >> > where
> > > > >> > do
> > > > >> > I set the memory manualy and not dinamicly?
> > > > >> > Also, do I boost SQL priority in processors?
> > > > >> > Can you please help and give some other tunning pointers? I set couple
> > > > >> > of
> > > > >> > boxes with 2000 SQL and always used 3GB switch but forgot the priority
> > > > >> > on
> > > > >> > processors and other fine tunning steps. Thanks in advance.
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >|||I have some empirical data on how much buffer pool mmeory a SQL instance
could consume with various settings of 3GB and AWE
http://sqlblog.com/blogs/linchi_shea/archive/2007/01/11/awe-and-3gb-an-empirical-picture.aspx
Linchi
"George" wrote:
> Yes. To be honest, it is vague as some other Microsoft documents. Not sure
> how to interpret the doc 100%.
> So far, I understand that as long as I have no more than 4GB, I can dedicate
> 3 GB to SQL and 1GB to Windows and other apps by using only /3GB switch in
> Boot.ini. My understanding was not to use PAE or AWE.
> "Chris Wood" wrote:
> > George,
> >
> > Have you seen this:- http://support.microsoft.com/kb/283037/en-us
> >
> > Chris
> >
> > "George" <George@.discussions.microsoft.com> wrote in message
> > news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...
> > > Chris, thanks. I can not go higher than 2.1 GB. Please help.
> > >
> > > "Chris Wood" wrote:
> > >
> > >> George,
> > >>
> > >> On server 2003 the switches should be set by the O/S. You will need to
> > >> configure AWE using sp_configure and then set max and min memory. I would
> > >> try with 2.5Gb first before you see if you can move up to 3Gb.
> > >>
> > >> Chris
> > >>
> > >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
> > >> > 4GB on the server and 3GB to SQL
> > >> >
> > >> > "Chris Wood" wrote:
> > >> >
> > >> >> George,
> > >> >>
> > >> >> How much memory do you have on the server? How much do you want to
> > >> >> give
> > >> >> to
> > >> >> SQL?
> > >> >>
> > >> >> Chris
> > >> >>
> > >> >> "George" <George@.discussions.microsoft.com> wrote in message
> > >> >> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> > >> >> > Please help. Just installed the SQL 2005 enterprise on 2003 standard
> > >> >> > server
> > >> >> > with /3GB switch.
> > >> >> > Now, in SQL there is an AWE option. Do I need to check that off and
> > >> >> > where
> > >> >> > do
> > >> >> > I set the memory manualy and not dinamicly?
> > >> >> > Also, do I boost SQL priority in processors?
> > >> >> > Can you please help and give some other tunning pointers? I set
> > >> >> > couple
> > >> >> > of
> > >> >> > boxes with 2000 SQL and always used 3GB switch but forgot the
> > >> >> > priority
> > >> >> > on
> > >> >> > processors and other fine tunning steps. Thanks in advance.
> > >> >> >
> > >> >>
> > >> >>
> > >> >>
> > >>
> > >>
> > >>
> >
> >
> >
AWE, 3GB and SQL Boost
Please help. Just installed the SQL 2005 enterprise on 2003 standard server with /3GB switch.
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>|||4GB on the server and 3GB to SQL
"Chris Wood" wrote:
> George,
> How much memory do you have on the server? How much do you want to give to
> SQL?
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>
>|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...[vbcol=seagreen]
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
>|||Ok. So
1. Set the 3GB switch in Boot.ini (did this before SQL installation)
2. Run the sp_configure and set it to 2.5
Please confirm. Also, is that check for AWE in GUI same as the sp command
via QA?
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>
>|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
[vbcol=seagreen]
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
>|||Thank you. I checked my prvious installations and you are right. I don't hav
e
it on.
Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
other switch in addition?
If I put same valuses in both min and max memory, would that mean it is now
FIXED MEMORY SIZE assigned vs dynamically when there is a range?
SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
sure you know of that just making a point)
"Linchi Shea" wrote:
[vbcol=seagreen]
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is th
e
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Book
s
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operatin
g
> system and network functions, resulting in problems shutting down SQL Serv
er
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
>|||Can anyone please confirm I should keep the 3GB in boot.ini and enable AWE i
n
SQL?
"Linchi Shea" wrote:
[vbcol=seagreen]
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is th
e
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Book
s
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operatin
g
> system and network functions, resulting in problems shutting down SQL Serv
er
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
>|||Chris, thanks. I can not go higher than 2.1 GB. Please help.
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>
>|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
>
Now, in SQL there is an AWE option. Do I need to check that off and where do I set the memory manualy and not dinamicly?
Also, do I boost SQL priority in processors?
Can you please help and give some other tunning pointers? I set couple of boxes with 2000 SQL and always used 3GB switch but forgot the priority on processors and other fine tunning steps. Thanks in advance.George,
How much memory do you have on the server? How much do you want to give to
SQL?
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
> Please help. Just installed the SQL 2005 enterprise on 2003 standard
> server
> with /3GB switch.
> Now, in SQL there is an AWE option. Do I need to check that off and where
> do
> I set the memory manualy and not dinamicly?
> Also, do I boost SQL priority in processors?
> Can you please help and give some other tunning pointers? I set couple of
> boxes with 2000 SQL and always used 3GB switch but forgot the priority on
> processors and other fine tunning steps. Thanks in advance.
>|||4GB on the server and 3GB to SQL
"Chris Wood" wrote:
> George,
> How much memory do you have on the server? How much do you want to give to
> SQL?
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:4DA093A5-D72C-4276-A19A-385B81975C1F@.microsoft.com...
>
>|||George,
On server 2003 the switches should be set by the O/S. You will need to
configure AWE using sp_configure and then set max and min memory. I would
try with 2.5Gb first before you see if you can move up to 3Gb.
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...[vbcol=seagreen]
> 4GB on the server and 3GB to SQL
> "Chris Wood" wrote:
>|||Ok. So
1. Set the 3GB switch in Boot.ini (did this before SQL installation)
2. Run the sp_configure and set it to 2.5
Please confirm. Also, is that check for AWE in GUI same as the sp command
via QA?
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>
>|||Yes, checking and applying the 'Use AWE to allocate memory' checkbox is the
same as executing the following T-SQL code:
EXEC sys.sp_configure N'awe enabled', N'1'
RECONFIGURE WITH OVERRIDE
BTW, you almost never should boost the SQL process priority. In fact, Books
Online comes with the following warning:
"Raising the priority too high may drain resources from essential operating
system and network functions, resulting in problems shutting down SQL Server
or using other operating system tasks on the server."
Linchi
"George" wrote:
[vbcol=seagreen]
> Ok. So
> 1. Set the 3GB switch in Boot.ini (did this before SQL installation)
> 2. Run the sp_configure and set it to 2.5
> Please confirm. Also, is that check for AWE in GUI same as the sp command
> via QA?
> "Chris Wood" wrote:
>|||Thank you. I checked my prvious installations and you are right. I don't hav
e
it on.
Now, as far as 3GB goes, do I keep it in the boot.ini and do I need some
other switch in addition?
If I put same valuses in both min and max memory, would that mean it is now
FIXED MEMORY SIZE assigned vs dynamically when there is a range?
SQL 2000 had a slider and a check box to choose from fixed and dynamyc (I am
sure you know of that just making a point)
"Linchi Shea" wrote:
[vbcol=seagreen]
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is th
e
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Book
s
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operatin
g
> system and network functions, resulting in problems shutting down SQL Serv
er
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
>|||Can anyone please confirm I should keep the 3GB in boot.ini and enable AWE i
n
SQL?
"Linchi Shea" wrote:
[vbcol=seagreen]
> Yes, checking and applying the 'Use AWE to allocate memory' checkbox is th
e
> same as executing the following T-SQL code:
> EXEC sys.sp_configure N'awe enabled', N'1'
> RECONFIGURE WITH OVERRIDE
> BTW, you almost never should boost the SQL process priority. In fact, Book
s
> Online comes with the following warning:
> "Raising the priority too high may drain resources from essential operatin
g
> system and network functions, resulting in problems shutting down SQL Serv
er
> or using other operating system tasks on the server."
> Linchi
> "George" wrote:
>|||Chris, thanks. I can not go higher than 2.1 GB. Please help.
"Chris Wood" wrote:
> George,
> On server 2003 the switches should be set by the O/S. You will need to
> configure AWE using sp_configure and then set max and min memory. I would
> try with 2.5Gb first before you see if you can move up to 3Gb.
> Chris
> "George" <George@.discussions.microsoft.com> wrote in message
> news:26F43606-A322-484B-84B7-7B339139B3A0@.microsoft.com...
>
>|||George,
Have you seen this:- http://support.microsoft.com/kb/283037/en-us
Chris
"George" <George@.discussions.microsoft.com> wrote in message
news:F90DAA9C-1226-4E6F-9445-D4C3696A4556@.microsoft.com...[vbcol=seagreen]
> Chris, thanks. I can not go higher than 2.1 GB. Please help.
> "Chris Wood" wrote:
>
AWE, /3gb and /pae stuff
Hi all,
I'm running under Windows Server 2000 datacenter sp4 with sql server 2000 Sp4
on 16GB Ram.
I enabled the /PAE in the boot.ini file and also enabled the AWE and set the SLQ Server maximum memory to 6144.
Do I need to include the /3GB switch in the boot.ini file?
I'm a little bit confused with the article found on the site. http://support.microsoft.com/default.aspx/kb/274750
Here are the lines.
Use of the /PAE switch in the Boot.ini and the AWE enable option in SQL Server allows SQL Server 2000 to utilize more than 4 GB memory. Without the /PAE switch SQL Server can only utilize up to 3 GB of memory. or-Use of the /3GB switch in the Boot.ini file allows SQL Server 2000 to use up to 3 GB of available memory.Regards,
Larry
Hi Larry,
As you're running 16GB of RAM, you need to include the /PAE and /3GB switch in boot.ini.
Have a look at http://www.microsoft.com/whdc/system/platform/server/PAE/pae_os.mspx and http://www.sql-server-performance.com/awe_memory.asp
Cheers,
Rob
|||The /3GB switch allows SQL Server to use an additional 1GB for the database engine purposes -procedure caches, various internal caching needs, etc.
The PAE memory (above 2GB that is not accessed by the /3GB) is used ONLY for data caching.
You most likely want both.
|||But carefully watch your memory usage when you use 3GB, if misused it might cause system instability because of kernel memory starvation.
Check out the link here with more information about these subjects.
WesleyB
Visit my SQL Server weblog @. http://dis4ea.blogspot.com
AWE working?
Hi all,
This is a question related to AWE settings. I am on windows 2003 ent version with SQL Server 2005 std version. I have configured SQL Server to use AWE and min memery as 22G and max as 26G (I have 32G in total as physical memory). I do see the message in log as "Windows Address ... Enabled", but when I am using performance monitor to view total memory in kb for SQL Server, it never starts at 22G (usually at 1G). And I doubt why? The account I am running SQL Server is an admin account, so it can definitely locked down the pages in memory. Also, I do think AWE is working somehow, after several hours in running, the total memory will up to 8, 9 or 11G. So, apparently, it is over 2G per process limitation. I still want to know.
1. Is my AWE setting working?
2. If not, how to fix that?
3. How to confirm how many memory is actaully using by SQL Server?
Thanks,
NIng
(The comment below assumes 32 bit OS and 32 bit SQL Server.)
1. Since you see that SQL Server's memory usage grows up to 11GB, it is obvious that AWE is working. SQL Server only requests memory from the OS as it is needed -once allocated, it usually keeps it.
2. Nothing to do
3. Performance Monitor, as you are using, indicates SQL Server's memory usage. For more detailed memory usage analysis, you can look at the various SQL Server Memory counters in Performance Monitor, and you can use some the the system functions that will give you memory data. Look at the System Views. (Click on Database, Views, System Views.) Try:
SELECT * FROM sys.dm_os_performance_counter
Looking specifically at the SQL Server Memory Manager objects.
|||Are you sure this is by design?My performance is awful after I have upgraded. SQL Server 2000 used to locked the memory as it starts, so the production server (4 cpus and 32 G memory) was doing a lot better than my development server with (1cpu and 2G memory). However, after upgrade, the performance level of the production server is awful. For example, a query need 9 seconds on test server used to run only 2 seconds on live server. Now it needs 8 seconds ...
|||
After upgrading, it is NECESSARY to rebuild ALL the indexes, and update the statistics. If you have not done that, your performace will often be signicantly worse.
And even then, some queries will run faster on SQL 2005, and some (albeit few) will run slower. It may be necessary to 'revise' queries that are signicantly slower in order to use the new ways that SQL 2005 produces execution plans.
AWE vs PAE
guys,
what is the difference between AWE and PAE?PAE allows the OS to use more than 4GB of memory. AWE allows the
application to use more than 4GB.
Andrew J. Kelly SQL MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
> guys,
> what is the difference between AWE and PAE?|||for SQL server, shd i enable PAE or AWE? Can both be enabled at the same tim
e?
"Andrew J. Kelly" wrote:
> PAE allows the OS to use more than 4GB of memory. AWE allows the
> application to use more than 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
>
>|||AWE is a SQL Server setting (sp_configure) and PAE is an operating system se
tting (BOOT.INI). If you
want SQL Server to utilize > 4GB memory, you need both settings.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...[vbcol=seagreen]
> for SQL server, shd i enable PAE or AWE? Can both be enabled at the same t
ime?
> "Andrew J. Kelly" wrote:
>|||in that case...in a server with 5G of ram
should i put the /AWE /PAE swith in the same line in the boot.ini?
For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
how do i check it has 5G? Also, is there any significant on it? The
performance shd be better i suppose
Thank you
"Tibor Karaszi" wrote:
> AWE is a SQL Server setting (sp_configure) and PAE is an operating system
setting (BOOT.INI). If you
> want SQL Server to utilize > 4GB memory, you need both settings.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...
>
>|||boot.ini should have something like this:
multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
Enterprise" /fastdetect /pae /3gb
(The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
provide a little more to the apps, i.e. SQL Server.)
To check the amount of physical RAM the OS is seeing you can just check
the Performance tab in task manager.
To turn on AWE memory for SQL Server you use the sp_configure stored
proc (in Query Analyzer for example):
exec sp_configure 'awe enabled', 1
reconfigure
go
Then you have to restart the SQL instance as the AWE setting only takes
affect on server startup. Also, when SQL Server is using AWE memory, it
cannot use dynamic memory management. It *will not swap pages out of
memory *if another app requests memory and the OS doesn't have enough to
satisfy the request (unlike the SQL dynamic memory manager). So you
should specify a "max server memory" amount with sp_configure. For
example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
remaining 1GB to the OS & other apps, you would do this in QA:
exec sp_configure "max server memory", 5120
reconfigure
go
All this is documented in SQL BOL:
http://msdn.microsoft.com/library/d... />
g_3stg.asp
To see how much memory SQL Server is currently consuming you can open
the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
AWE & memory management.
HTH
*mike hodgson*
/ mallesons stephen jaques/
blog: http://sqlnerd.blogspot.com
rupart wrote:
[vbcol=seagreen]
>in that case...in a server with 5G of ram
>should i put the /AWE /PAE swith in the same line in the boot.ini?
>For the OS, i can see under system mgmt that 5G is enabled. How abt for sql
?
>how do i check it has 5G? Also, is there any significant on it? The
>performance shd be better i suppose
>Thank you
>"Tibor Karaszi" wrote:
>
>|||does /3g means the system will allocate 3g for system and the rest for
sql(that is after enabling thru AWE, rite?)?
yeah, good link...thank you
"Mike Hodgson" wrote:
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just check
> the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only takes
> affect on server startup. Also, when SQL Server is using AWE memory, it
> cannot use dynamic memory management. It *will not swap pages out of
> memory *if another app requests memory and the OS doesn't have enough to
> satisfy the request (unlike the SQL dynamic memory manager). So you
> should specify a "max server memory" amount with sp_configure. For
> example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
> remaining 1GB to the OS & other apps, you would do this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/d...>
fig_3stg.asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
> AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
>|||The other way around. 3 GB for the application and 1 GB for the system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:4944B057-1DC7-4638-BB88-9040FDCC9B9F@.microsoft.com...[vbcol=seagreen]
> does /3g means the system will allocate 3g for system and the rest for
> sql(that is after enabling thru AWE, rite?)?
> yeah, good link...thank you
> "Mike Hodgson" wrote:
>|||Oops - slight typo in my "max server memory" statement. To set a max
server memory of 4GB you would run:
exec sp_configure "max server memory", 4096
reconfigure
go
The 5120 figure I included in my previous post would try to set it at
5GB (not 4GB).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Mike Hodgson wrote:
[vbcol=seagreen]
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just
> check the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only
> takes affect on server startup. Also, when SQL Server is using AWE
> memory, it cannot use dynamic memory management. It *will not swap
> pages out of memory *if another app requests memory and the OS doesn't
> have enough to satisfy the request (unlike the SQL dynamic memory
> manager). So you should specify a "max server memory" amount with
> sp_configure. For example, on your 5GB box, if you wanted to allocate
> 4GB to SQL and the remaining 1GB to the OS & other apps, you would do
> this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/d...
fig_3stg..asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff
> on AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
what is the difference between AWE and PAE?PAE allows the OS to use more than 4GB of memory. AWE allows the
application to use more than 4GB.
Andrew J. Kelly SQL MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
> guys,
> what is the difference between AWE and PAE?|||for SQL server, shd i enable PAE or AWE? Can both be enabled at the same tim
e?
"Andrew J. Kelly" wrote:
> PAE allows the OS to use more than 4GB of memory. AWE allows the
> application to use more than 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
>
>|||AWE is a SQL Server setting (sp_configure) and PAE is an operating system se
tting (BOOT.INI). If you
want SQL Server to utilize > 4GB memory, you need both settings.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...[vbcol=seagreen]
> for SQL server, shd i enable PAE or AWE? Can both be enabled at the same t
ime?
> "Andrew J. Kelly" wrote:
>|||in that case...in a server with 5G of ram
should i put the /AWE /PAE swith in the same line in the boot.ini?
For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
how do i check it has 5G? Also, is there any significant on it? The
performance shd be better i suppose
Thank you
"Tibor Karaszi" wrote:
> AWE is a SQL Server setting (sp_configure) and PAE is an operating system
setting (BOOT.INI). If you
> want SQL Server to utilize > 4GB memory, you need both settings.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...
>
>|||boot.ini should have something like this:
multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
Enterprise" /fastdetect /pae /3gb
(The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
provide a little more to the apps, i.e. SQL Server.)
To check the amount of physical RAM the OS is seeing you can just check
the Performance tab in task manager.
To turn on AWE memory for SQL Server you use the sp_configure stored
proc (in Query Analyzer for example):
exec sp_configure 'awe enabled', 1
reconfigure
go
Then you have to restart the SQL instance as the AWE setting only takes
affect on server startup. Also, when SQL Server is using AWE memory, it
cannot use dynamic memory management. It *will not swap pages out of
memory *if another app requests memory and the OS doesn't have enough to
satisfy the request (unlike the SQL dynamic memory manager). So you
should specify a "max server memory" amount with sp_configure. For
example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
remaining 1GB to the OS & other apps, you would do this in QA:
exec sp_configure "max server memory", 5120
reconfigure
go
All this is documented in SQL BOL:
http://msdn.microsoft.com/library/d... />
g_3stg.asp
To see how much memory SQL Server is currently consuming you can open
the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
AWE & memory management.
HTH
*mike hodgson*
/ mallesons stephen jaques/
blog: http://sqlnerd.blogspot.com
rupart wrote:
[vbcol=seagreen]
>in that case...in a server with 5G of ram
>should i put the /AWE /PAE swith in the same line in the boot.ini?
>For the OS, i can see under system mgmt that 5G is enabled. How abt for sql
?
>how do i check it has 5G? Also, is there any significant on it? The
>performance shd be better i suppose
>Thank you
>"Tibor Karaszi" wrote:
>
>|||does /3g means the system will allocate 3g for system and the rest for
sql(that is after enabling thru AWE, rite?)?
yeah, good link...thank you
"Mike Hodgson" wrote:
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just check
> the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only takes
> affect on server startup. Also, when SQL Server is using AWE memory, it
> cannot use dynamic memory management. It *will not swap pages out of
> memory *if another app requests memory and the OS doesn't have enough to
> satisfy the request (unlike the SQL dynamic memory manager). So you
> should specify a "max server memory" amount with sp_configure. For
> example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
> remaining 1GB to the OS & other apps, you would do this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/d...>
fig_3stg.asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
> AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
>|||The other way around. 3 GB for the application and 1 GB for the system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:4944B057-1DC7-4638-BB88-9040FDCC9B9F@.microsoft.com...[vbcol=seagreen]
> does /3g means the system will allocate 3g for system and the rest for
> sql(that is after enabling thru AWE, rite?)?
> yeah, good link...thank you
> "Mike Hodgson" wrote:
>|||Oops - slight typo in my "max server memory" statement. To set a max
server memory of 4GB you would run:
exec sp_configure "max server memory", 4096
reconfigure
go
The 5120 figure I included in my previous post would try to set it at
5GB (not 4GB).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Mike Hodgson wrote:
[vbcol=seagreen]
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just
> check the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only
> takes affect on server startup. Also, when SQL Server is using AWE
> memory, it cannot use dynamic memory management. It *will not swap
> pages out of memory *if another app requests memory and the OS doesn't
> have enough to satisfy the request (unlike the SQL dynamic memory
> manager). So you should specify a "max server memory" amount with
> sp_configure. For example, on your 5GB box, if you wanted to allocate
> 4GB to SQL and the remaining 1GB to the OS & other apps, you would do
> this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/d...
fig_3stg..asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff
> on AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
AWE upper memory limit
Hi,
I have a question that I hope someone can help me with.
I am running SQL Server 2005 on a Windows 2003 Standard edition (x32). I have 6GB of memory in it but have realised that Windows can't use more than 4GB (I have enabled /PAE and /3GB in the boot.ini).
My question is:
Can SQL Server make use of the extra memory I have in the server? Otherwise I guess it is pointless having more than 4GB in there.
Thank you for your help!
Kind Regards
Stefan Ghose
Hello Stefan -
The way memory is used between 32-bit processors, the various Windows operating systems and SQL Server can be confusing. Because of 32-bit architectures and software design decisions, the first 2GB of RAM in a Windows 2000 or 2003 server is directly addressable by applications like SQL Server. That means that query plans, memory buffers and the like all go in this space. No changes are needed in any configurations, either at the OS or SQL Server level.
With the /3GB switch turned on in the BOOT.INI file, SQL Server increases this base limit to 3GB. This is great for SQL Server, but if you have other apps on your server, it can starve the OS, leaving only 1GB for all operations. Experts are divided on whether this is a good thing. I turn it on when the box is dedicated to SQL Server, and watch for errors in the event logs. If I see memory or I/O errors, or if the box becomes unstable in testing, I turn it off.
If you have 4GB in your server as you've indicated, that's all you need to do. Inside of SQL Server, I also recommend setting a floor and ceiling limit of 3GB, so it doesn't have to dynamically manage the RAM. That just saves a few ops, which is always a good thing. Again, I only do this if SQL Server is the only app on the box.
If you have over 4GB of RAM on the server, SQL Server needs a few things to use it. First, you have to enable the /PAE switch in the BOOT.INI file. Next, you need to set the SQL Server to use AWE memory. With these two things configured, the server will use the space above 4GB as a read-ahead buffer. It doesn't help much with query plans and those sorts of base memory operations, but it will speed up large queries.
Buck Woody
|||Thanks Buck!!
That was just what I was looking for... another thing... since I already have enabled AWE on my SQL server do I need to do anything with Max memory usage? Or can I just leave it at its default value?
Kind Regards
Stefan Ghose
|||The default is fine - you have it dynamic, I assume?AWE SQL Performance Problem
We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB R
AM. The setting seems to have made the difference in RAM usage, but we are e
xperiencing extremely high CPU utilization and overall the system does not s
eem to be any faster. If an
ything, it seems to have slowed down some. There are a lot of variables, but
I was wondering of anyone has had adverse effects with the AWE setting.From BOL.
<<
To enable AWE, set awe enabled to 1. SQL Server will reserve almost all
available memory, leaving 128 megabytes (MB) or less, unless a value has
been specified for max server memory.
What is your max memory setting? Leaving 128M for the OS probably isn't a
good idea.
BTW... Profiler may be helpful in understanding the CPU usage.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||We had some CPU spin and server instability issues that were instantaneously
and permenantly solved by turning off the /3GB switch and reducing max
server mem to 1.5GB less than physical. PSS said there was potential kernel
memory starvation with /3GB and max server memory set to near physical. Not
sure if this applies to your scenario.
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||Hi Phil,
I am viewing your post and since we have not heard from you for some time
and I wonder how things go on your side. To disable the AWE to check if the
performance issue is related to the AWE is the method to narrow down
performance problems to AWE. Also, you could refer to the link of the
followings for reference:
How To Gather Information for Effective Troubleshooting of Performance
Issues
http://support.microsoft.com/defaul...microsoft.com:
80/support/kb/articles/Q175/6/58.ASP&NoWebContent=1
http://support.microsoft.com/defaul...kb;en-us;298475
Also, if the case is critical and it should be troubleshot by some advanced
tools which are not supported in the newsgroup. Therefore, we probably will
not be able to resolve the issue through the newsgroups. I'd recommend
opening a Support incident with Microsoft Support Services, so that a
dedicated Support Professional can assist with your advisory case. Please
be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thanks.
Hope this helps.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
AM. The setting seems to have made the difference in RAM usage, but we are e
xperiencing extremely high CPU utilization and overall the system does not s
eem to be any faster. If an
ything, it seems to have slowed down some. There are a lot of variables, but
I was wondering of anyone has had adverse effects with the AWE setting.From BOL.
<<
To enable AWE, set awe enabled to 1. SQL Server will reserve almost all
available memory, leaving 128 megabytes (MB) or less, unless a value has
been specified for max server memory.
What is your max memory setting? Leaving 128M for the OS probably isn't a
good idea.
BTW... Profiler may be helpful in understanding the CPU usage.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||We had some CPU spin and server instability issues that were instantaneously
and permenantly solved by turning off the /3GB switch and reducing max
server mem to 1.5GB less than physical. PSS said there was potential kernel
memory starvation with /3GB and max server memory set to near physical. Not
sure if this applies to your scenario.
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||Hi Phil,
I am viewing your post and since we have not heard from you for some time
and I wonder how things go on your side. To disable the AWE to check if the
performance issue is related to the AWE is the method to narrow down
performance problems to AWE. Also, you could refer to the link of the
followings for reference:
How To Gather Information for Effective Troubleshooting of Performance
Issues
http://support.microsoft.com/defaul...microsoft.com:
80/support/kb/articles/Q175/6/58.ASP&NoWebContent=1
http://support.microsoft.com/defaul...kb;en-us;298475
Also, if the case is critical and it should be troubleshot by some advanced
tools which are not supported in the newsgroup. Therefore, we probably will
not be able to resolve the issue through the newsgroups. I'd recommend
opening a Support incident with Microsoft Support Services, so that a
dedicated Support Professional can assist with your advisory case. Please
be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thanks.
Hope this helps.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Thursday, March 8, 2012
awe settings.
SQL2K Ent SP3a Win2k SP3
I've recently enabled awe memory on 2 of our servers.
Everything seems to be going OK, AWE memory counters
are active in performance monitor and the sql serror log
shows awe memory enabled on startup.
My question is, is the above information enough to know that
awe is working correctly? If not, what other things can be looked
at?
TIA.see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274750#6
--
BR,
Mark Broadbent mcdba,mcse+i
_________________________
"Stressed" <k@.c.co.uk> wrote in message
news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
> SQL2K Ent SP3a Win2k SP3
> I've recently enabled awe memory on 2 of our servers.
> Everything seems to be going OK, AWE memory counters
> are active in performance monitor and the sql serror log
> shows awe memory enabled on startup.
> My question is, is the above information enough to know that
> awe is working correctly? If not, what other things can be looked
> at?
> TIA.
>
>|||Also, when SQL Server starts you should see a line time in
the event log that says:
"Address Windowing Extensions enabled."
Ron
>--Original Message--
>see
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q274750#6
>--
>BR,
>Mark Broadbent mcdba,mcse+i
>_________________________
>"Stressed" <k@.c.co.uk> wrote in message
>news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
>> SQL2K Ent SP3a Win2k SP3
>> I've recently enabled awe memory on 2 of our servers.
>> Everything seems to be going OK, AWE memory counters
>> are active in performance monitor and the sql serror log
>> shows awe memory enabled on startup.
>> My question is, is the above information enough to know
that
>> awe is working correctly? If not, what other things can
be looked
>> at?
>> TIA.
>>
>>
>
>.
>
I've recently enabled awe memory on 2 of our servers.
Everything seems to be going OK, AWE memory counters
are active in performance monitor and the sql serror log
shows awe memory enabled on startup.
My question is, is the above information enough to know that
awe is working correctly? If not, what other things can be looked
at?
TIA.see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q274750#6
--
BR,
Mark Broadbent mcdba,mcse+i
_________________________
"Stressed" <k@.c.co.uk> wrote in message
news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
> SQL2K Ent SP3a Win2k SP3
> I've recently enabled awe memory on 2 of our servers.
> Everything seems to be going OK, AWE memory counters
> are active in performance monitor and the sql serror log
> shows awe memory enabled on startup.
> My question is, is the above information enough to know that
> awe is working correctly? If not, what other things can be looked
> at?
> TIA.
>
>|||Also, when SQL Server starts you should see a line time in
the event log that says:
"Address Windowing Extensions enabled."
Ron
>--Original Message--
>see
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;Q274750#6
>--
>BR,
>Mark Broadbent mcdba,mcse+i
>_________________________
>"Stressed" <k@.c.co.uk> wrote in message
>news:%23oI0KZzVDHA.2164@.TK2MSFTNGP09.phx.gbl...
>> SQL2K Ent SP3a Win2k SP3
>> I've recently enabled awe memory on 2 of our servers.
>> Everything seems to be going OK, AWE memory counters
>> are active in performance monitor and the sql serror log
>> shows awe memory enabled on startup.
>> My question is, is the above information enough to know
that
>> awe is working correctly? If not, what other things can
be looked
>> at?
>> TIA.
>>
>>
>
>.
>
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
________________________________________
__________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
________________________________________
___________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
________________________________________
___________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> ________________________________________
__________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ________________________________________
___________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ________________________________________
___________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/d...-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
________________________________________
__________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
________________________________________
___________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
________________________________________
___________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> ________________________________________
__________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ________________________________________
___________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ________________________________________
___________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/d...-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________ ________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________ _________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________ _________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________ ________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________ _________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________ _________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/de...us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/de...us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________ ________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________ _________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________ _________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________ ________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________ _________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________ _________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/de...us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/de...us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition with SP3.
The boot.ini is set with /3gb /PAE. The server system properties list 8GB of RAM. Within SQL Server sp_configure AWE running is set to 1. SQL Server Memory properties the Maximum is set to 5.12 GB. But SQL Server does not recognize AWE setting.
I look in the SQL Server errorlog after the server was rebooted and did not list AWE memory settings.
The Server Performance Monitor Counter under SQL Server Memory Manager with Target Server Memory list 2.7GB.
This should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
___________________________________________________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
___________________________________________________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ___________________________________________________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ___________________________________________________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the ?Lock Pages in Memory?
privilege:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_server_1fnd.asp
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
--
Andrew J. Kelly SQL MVP
"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> > I have a server with SQL Server 2000 Enterprise Edition
> > with SP3. The boot.ini is set with /3gb /PAE. The server
> > system properties list 8GB of RAM. Within SQL Server
> > sp_configure AWE running is set to 1. SQL Server Memory
> > properties the Maximum is set to 5.12 GB. But SQL Server
> > does not recognize AWE setting. I look in the SQL Server
> > errorlog after the server was rebooted and did not list
> > AWE memory settings. The Server Performance Monitor
> > Counter under SQL Server Memory Manager with Target Server
> > Memory list 2.7GB. This should be 5.12 GB of memory for
> > SQL Server.
> >
> > Please help me resolve this problem.
> >
> > Mike
> >
> > __________________________________________________________
> > [boot loader]
> > timeout=10
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> > Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> > ___________________________________________________________
> > sp_configure "show advanced options", 1
> > RECONFIGURE
> > GO
> > sp_configure "awe enabled", 1
> > RECONFIGURE
> > GO
> > sp_configure "max server memory", 5120
> > RECONFIGURE
> > GO
> > sp_configure "min server memory", 0
> > RECONFIGURE
> > GO
> > ___________________________________________________________
> > Output from SP_CONFIGURE
> > name minimum
> > maximum config_value run_value
> > -- -- --
> > -- --
> > affinity mask -2147483648
> > 2147483647 0 0
> > allow updates 0
> > 1 0 0
> > awe enabled 0
> > 1 1 1
> > c2 audit mode 0
> > 1 0 0
> > cost threshold for parallelism 0
> > 32767 5 5
> > Cross DB Ownership Chaining 0
> > 1 0 0
> > cursor threshold -1
> > 2147483647 -1 -1
> > default full-text language 0
> > 2147483647 1033 1033
> > default language 0
> > 9999 0 0
> > fill factor (%) 0
> > 100 0 0
> > index create memory (KB) 704
> > 2147483647 0 0
> > lightweight pooling 0
> > 1 0 0
> > locks 5000
> > 2147483647 0 0
> > max degree of parallelism 0
> > 32 0 0
> > max server memory (MB) 4
> > 2147483647 5120 5120
> > max text repl size (B) 0
> > 2147483647 65536 65536
> > max worker threads 32
> > 32767 255 255
> > media retention 0
> > 365 0 0
> > min memory per query (KB) 512
> > 2147483647 1024 1024
> > min server memory (MB) 0
> > 2147483647 0 0
> > nested triggers 0
> > 1 1 1
> > network packet size (B) 512
> > 65536 4096 4096
> > open objects 0
> > 2147483647 0 0
> > priority boost 0
> > 1 0 0
> > query governor cost limit 0
> > 2147483647 0 0
> > query wait (s) -1
> > 2147483647 -1 -1
> > recovery interval (min) 0
> > 32767 0 0
> > remote access 0
> > 1 1 1
> > remote login timeout (s) 0
> > 2147483647 20 20
> > remote proc trans 0
> > 1 0 0
> > remote query timeout (s) 0
> > 2147483647 600 600
> > scan for startup procs 0
> > 1 1 0
> > set working set size 0
> > 1 0 0
> > show advanced options 0
> > 1 1 1
> > two digit year cutoff 1753
> > 9999 2049 2049
> > user connections 0
> > 32767 0 0
> > user options 0
> > 32767 56 56
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
The boot.ini is set with /3gb /PAE. The server system properties list 8GB of RAM. Within SQL Server sp_configure AWE running is set to 1. SQL Server Memory properties the Maximum is set to 5.12 GB. But SQL Server does not recognize AWE setting.
I look in the SQL Server errorlog after the server was rebooted and did not list AWE memory settings.
The Server Performance Monitor Counter under SQL Server Memory Manager with Target Server Memory list 2.7GB.
This should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
___________________________________________________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
___________________________________________________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ___________________________________________________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ___________________________________________________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the ?Lock Pages in Memory?
privilege:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_server_1fnd.asp
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
--
Andrew J. Kelly SQL MVP
"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> > I have a server with SQL Server 2000 Enterprise Edition
> > with SP3. The boot.ini is set with /3gb /PAE. The server
> > system properties list 8GB of RAM. Within SQL Server
> > sp_configure AWE running is set to 1. SQL Server Memory
> > properties the Maximum is set to 5.12 GB. But SQL Server
> > does not recognize AWE setting. I look in the SQL Server
> > errorlog after the server was rebooted and did not list
> > AWE memory settings. The Server Performance Monitor
> > Counter under SQL Server Memory Manager with Target Server
> > Memory list 2.7GB. This should be 5.12 GB of memory for
> > SQL Server.
> >
> > Please help me resolve this problem.
> >
> > Mike
> >
> > __________________________________________________________
> > [boot loader]
> > timeout=10
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> > Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> > ___________________________________________________________
> > sp_configure "show advanced options", 1
> > RECONFIGURE
> > GO
> > sp_configure "awe enabled", 1
> > RECONFIGURE
> > GO
> > sp_configure "max server memory", 5120
> > RECONFIGURE
> > GO
> > sp_configure "min server memory", 0
> > RECONFIGURE
> > GO
> > ___________________________________________________________
> > Output from SP_CONFIGURE
> > name minimum
> > maximum config_value run_value
> > -- -- --
> > -- --
> > affinity mask -2147483648
> > 2147483647 0 0
> > allow updates 0
> > 1 0 0
> > awe enabled 0
> > 1 1 1
> > c2 audit mode 0
> > 1 0 0
> > cost threshold for parallelism 0
> > 32767 5 5
> > Cross DB Ownership Chaining 0
> > 1 0 0
> > cursor threshold -1
> > 2147483647 -1 -1
> > default full-text language 0
> > 2147483647 1033 1033
> > default language 0
> > 9999 0 0
> > fill factor (%) 0
> > 100 0 0
> > index create memory (KB) 704
> > 2147483647 0 0
> > lightweight pooling 0
> > 1 0 0
> > locks 5000
> > 2147483647 0 0
> > max degree of parallelism 0
> > 32 0 0
> > max server memory (MB) 4
> > 2147483647 5120 5120
> > max text repl size (B) 0
> > 2147483647 65536 65536
> > max worker threads 32
> > 32767 255 255
> > media retention 0
> > 365 0 0
> > min memory per query (KB) 512
> > 2147483647 1024 1024
> > min server memory (MB) 0
> > 2147483647 0 0
> > nested triggers 0
> > 1 1 1
> > network packet size (B) 512
> > 65536 4096 4096
> > open objects 0
> > 2147483647 0 0
> > priority boost 0
> > 1 0 0
> > query governor cost limit 0
> > 2147483647 0 0
> > query wait (s) -1
> > 2147483647 -1 -1
> > recovery interval (min) 0
> > 32767 0 0
> > remote access 0
> > 1 1 1
> > remote login timeout (s) 0
> > 2147483647 20 20
> > remote proc trans 0
> > 1 0 0
> > remote query timeout (s) 0
> > 2147483647 600 600
> > scan for startup procs 0
> > 1 1 0
> > set working set size 0
> > 1 0 0
> > show advanced options 0
> > 1 1 1
> > two digit year cutoff 1753
> > 9999 2049 2049
> > user connections 0
> > 32767 0 0
> > user options 0
> > 32767 56 56
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
Subscribe to:
Posts (Atom)