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 ram. Show all posts
Showing posts with label ram. 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 /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 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 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.
>
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. When I look
in the SQL Server error log it tells me that 8 processors
and 2048 MB RAM where detected. SQL Server Memory
properties are set with the Maximum to 5.12 GB. But SQL
Server does not recognize AWE setting. 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 56Do you have Lock Pages In Memory set properly? See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811891&Product=sql2k
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:9ede01c4349c$357f8a70$a401280a@.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. When I look
> in the SQL Server error log it tells me that 8 processors
> and 2048 MB RAM where detected. SQL Server Memory
> properties are set with the Maximum to 5.12 GB. But SQL
> Server does not recognize AWE setting. 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
>
>|||The SQL Server service account is listed in the Lock
pages in memory is set the same way three other servers
that work correctly.
Is this server not recognizing this setting?
Please help me with this problem.
Thanks,
Mike
>--Original Message--
>Do you have Lock Pages In Memory set properly? See this:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;811891&Product=sql2k
>--
>Andrew J. Kelly SQL MVP
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:9ede01c4349c$357f8a70$a401280a@.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. When I
look
>> in the SQL Server error log it tells me that 8
processors
>> and 2048 MB RAM where detected. SQL Server Memory
>> properties are set with the Maximum to 5.12 GB. But
SQL
>> Server does not recognize AWE setting. 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
>>
>>
>
>.
>|||According to the results of sp_configure your run value is still set to 0
for AWE. Did you restart the server? And are you absolutely sure you have
SQL EE? What does xp_msver show?
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a04c01c434f9$3dde5ae0$a401280a@.phx.gbl...
> The SQL Server service account is listed in the Lock
> pages in memory is set the same way three other servers
> that work correctly.
> Is this server not recognizing this setting?
> Please help me with this problem.
> Thanks,
> Mike
>
> >--Original Message--
> >Do you have Lock Pages In Memory set properly? See this:
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;811891&Product=sql2k
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:9ede01c4349c$357f8a70$a401280a@.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. When I
> look
> >> in the SQL Server error log it tells me that 8
> processors
> >> and 2048 MB RAM where detected. SQL Server Memory
> >> properties are set with the Maximum to 5.12 GB. But
> SQL
> >> Server does not recognize AWE setting. 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
> >>
> >>
> >>
> >>
> >
> >
> >.
> >
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. When I look
in the SQL Server error log it tells me that 8 processors
and 2048 MB RAM where detected. SQL Server Memory
properties are set with the Maximum to 5.12 GB. But SQL
Server does not recognize AWE setting. 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 56Do you have Lock Pages In Memory set properly? See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811891&Product=sql2k
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:9ede01c4349c$357f8a70$a401280a@.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. When I look
> in the SQL Server error log it tells me that 8 processors
> and 2048 MB RAM where detected. SQL Server Memory
> properties are set with the Maximum to 5.12 GB. But SQL
> Server does not recognize AWE setting. 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
>
>|||The SQL Server service account is listed in the Lock
pages in memory is set the same way three other servers
that work correctly.
Is this server not recognizing this setting?
Please help me with this problem.
Thanks,
Mike
>--Original Message--
>Do you have Lock Pages In Memory set properly? See this:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;811891&Product=sql2k
>--
>Andrew J. Kelly SQL MVP
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:9ede01c4349c$357f8a70$a401280a@.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. When I
look
>> in the SQL Server error log it tells me that 8
processors
>> and 2048 MB RAM where detected. SQL Server Memory
>> properties are set with the Maximum to 5.12 GB. But
SQL
>> Server does not recognize AWE setting. 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
>>
>>
>
>.
>|||According to the results of sp_configure your run value is still set to 0
for AWE. Did you restart the server? And are you absolutely sure you have
SQL EE? What does xp_msver show?
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a04c01c434f9$3dde5ae0$a401280a@.phx.gbl...
> The SQL Server service account is listed in the Lock
> pages in memory is set the same way three other servers
> that work correctly.
> Is this server not recognizing this setting?
> Please help me with this problem.
> Thanks,
> Mike
>
> >--Original Message--
> >Do you have Lock Pages In Memory set properly? See this:
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;811891&Product=sql2k
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:9ede01c4349c$357f8a70$a401280a@.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. When I
> look
> >> in the SQL Server error log it tells me that 8
> processors
> >> and 2048 MB RAM where detected. SQL Server Memory
> >> properties are set with the Maximum to 5.12 GB. But
> SQL
> >> Server does not recognize AWE setting. 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
> >>
> >>
> >>
> >>
> >
> >
> >.
> >
awe question
We are going to turn on AWE on our production environment currently
its 4 processor box with 12GB of RAM and windows advanced server 2000
loaded on it. Now my question is do i need to use /PAE and /3GB
switches in our boot.ini in order to enable 6gigs to our sql server
or /PAE will okay?kulkarni.ninad@.gmail.com wrote:
> We are going to turn on AWE on our production environment currently
> its 4 processor box with 12GB of RAM and windows advanced server 2000
> loaded on it. Now my question is do i need to use /PAE and /3GB
> switches in our boot.ini in order to enable 6gigs to our sql server
> or /PAE will okay?
>
With 6Gb of RAM, I would use the /3GB switch as well. That would
effectively allow SQL to use as much as 5GB. Without the /3Gb switch
you are pretty well limited to 4Gb.|||That is not really true. /3GB allows SQL Server (or any properly enabled
application) to use up to 3GB of the 4GB of directly addressable memory but
limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
the App to see memory above 4GB and is totally independent of the /3GB
switch. The decision to use /3GB or not is dependent on how much of that
directly addressable memory you need to use. The only part of SQL Server
that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
cache. I would question why he wants to use only 6GB when he has 12
available. I suspect he may be in a cluster and if that is true and it is
Active-Active then 6GB may be too much since AWE memory is fixed and can not
be dynamically adjusted.
Andrew J. Kelly SQL MVP
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message
news:uEmOq6LbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> kulkarni.ninad@.gmail.com wrote:
> With 6Gb of RAM, I would use the /3GB switch as well. That would
> effectively allow SQL to use as much as 5GB. Without the /3Gb switch you
> are pretty well limited to 4Gb.|||Andrew J. Kelly wrote:
> That is not really true. /3GB allows SQL Server (or any properly enabled
> application) to use up to 3GB of the 4GB of directly addressable memory bu
t
> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS a
nd
> the App to see memory above 4GB and is totally independent of the /3GB
> switch. The decision to use /3GB or not is dependent on how much of that
> directly addressable memory you need to use. The only part of SQL Server
> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
> cache. I would question why he wants to use only 6GB when he has 12
> available. I suspect he may be in a cluster and if that is true and it is
> Active-Active then 6GB may be too much since AWE memory is fixed and can n
ot
> be dynamically adjusted.
>
My thinking was that there was only 6Gb and if you didn't use the /3Gb
switch, then the OS would effectively take the full 2Gb available to it,
leaving 4Gb for applications such as SQL. While using the /3Gb switch
would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
However, now I see that there is actually 12Gb...
With 12Gb you don't need the /3Gb switch in order to allow SQL to see
6Gb (actually it could use 10Gb), however, I have to wonder why you want
to limit SQL to 6Gb when you have 12?
I think my recommendation still stands though, because if I recall, it's
not until you have over 16Gb of RAM that the OS has to use that extra Gb
of space to maintain the Address Extensions.
So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
10Gb without it. Although I'd keep a close eye on things to make sure
that the OS is not having to do a bunch of swapping. In certain
circumstances the OS might be able to make better use of that Gb than SQL.|||> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
I believe that Unisys has recommendations to not use /3GB if you have > 12GB
in the machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message news:uhqohQYbHHA.588@.TK2MSFTNGP06.phx.
gbl...
> Andrew J. Kelly wrote:
> My thinking was that there was only 6Gb and if you didn't use the /3Gb
> switch, then the OS would effectively take the full 2Gb available to it,
> leaving 4Gb for applications such as SQL. While using the /3Gb switch
> would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
> However, now I see that there is actually 12Gb...
> With 12Gb you don't need the /3Gb switch in order to allow SQL to see
> 6Gb (actually it could use 10Gb), however, I have to wonder why you want
> to limit SQL to 6Gb when you have 12?
> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
> So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
> 10Gb without it. Although I'd keep a close eye on things to make sure
> that the OS is not having to do a bunch of swapping. In certain
> circumstances the OS might be able to make better use of that Gb than SQL.
its 4 processor box with 12GB of RAM and windows advanced server 2000
loaded on it. Now my question is do i need to use /PAE and /3GB
switches in our boot.ini in order to enable 6gigs to our sql server
or /PAE will okay?kulkarni.ninad@.gmail.com wrote:
> We are going to turn on AWE on our production environment currently
> its 4 processor box with 12GB of RAM and windows advanced server 2000
> loaded on it. Now my question is do i need to use /PAE and /3GB
> switches in our boot.ini in order to enable 6gigs to our sql server
> or /PAE will okay?
>
With 6Gb of RAM, I would use the /3GB switch as well. That would
effectively allow SQL to use as much as 5GB. Without the /3Gb switch
you are pretty well limited to 4Gb.|||That is not really true. /3GB allows SQL Server (or any properly enabled
application) to use up to 3GB of the 4GB of directly addressable memory but
limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
the App to see memory above 4GB and is totally independent of the /3GB
switch. The decision to use /3GB or not is dependent on how much of that
directly addressable memory you need to use. The only part of SQL Server
that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
cache. I would question why he wants to use only 6GB when he has 12
available. I suspect he may be in a cluster and if that is true and it is
Active-Active then 6GB may be too much since AWE memory is fixed and can not
be dynamically adjusted.
Andrew J. Kelly SQL MVP
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message
news:uEmOq6LbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> kulkarni.ninad@.gmail.com wrote:
> With 6Gb of RAM, I would use the /3GB switch as well. That would
> effectively allow SQL to use as much as 5GB. Without the /3Gb switch you
> are pretty well limited to 4Gb.|||Andrew J. Kelly wrote:
> That is not really true. /3GB allows SQL Server (or any properly enabled
> application) to use up to 3GB of the 4GB of directly addressable memory bu
t
> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS a
nd
> the App to see memory above 4GB and is totally independent of the /3GB
> switch. The decision to use /3GB or not is dependent on how much of that
> directly addressable memory you need to use. The only part of SQL Server
> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
> cache. I would question why he wants to use only 6GB when he has 12
> available. I suspect he may be in a cluster and if that is true and it is
> Active-Active then 6GB may be too much since AWE memory is fixed and can n
ot
> be dynamically adjusted.
>
My thinking was that there was only 6Gb and if you didn't use the /3Gb
switch, then the OS would effectively take the full 2Gb available to it,
leaving 4Gb for applications such as SQL. While using the /3Gb switch
would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
However, now I see that there is actually 12Gb...
With 12Gb you don't need the /3Gb switch in order to allow SQL to see
6Gb (actually it could use 10Gb), however, I have to wonder why you want
to limit SQL to 6Gb when you have 12?
I think my recommendation still stands though, because if I recall, it's
not until you have over 16Gb of RAM that the OS has to use that extra Gb
of space to maintain the Address Extensions.
So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
10Gb without it. Although I'd keep a close eye on things to make sure
that the OS is not having to do a bunch of swapping. In certain
circumstances the OS might be able to make better use of that Gb than SQL.|||> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
I believe that Unisys has recommendations to not use /3GB if you have > 12GB
in the machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message news:uhqohQYbHHA.588@.TK2MSFTNGP06.phx.
gbl...
> Andrew J. Kelly wrote:
> My thinking was that there was only 6Gb and if you didn't use the /3Gb
> switch, then the OS would effectively take the full 2Gb available to it,
> leaving 4Gb for applications such as SQL. While using the /3Gb switch
> would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
> However, now I see that there is actually 12Gb...
> With 12Gb you don't need the /3Gb switch in order to allow SQL to see
> 6Gb (actually it could use 10Gb), however, I have to wonder why you want
> to limit SQL to 6Gb when you have 12?
> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
> So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
> 10Gb without it. Although I'd keep a close eye on things to make sure
> that the OS is not having to do a bunch of swapping. In certain
> circumstances the OS might be able to make better use of that Gb than SQL.
awe question
We are going to turn on AWE on our production environment currently
its 4 processor box with 12GB of RAM and windows advanced server 2000
loaded on it. Now my question is do i need to use /PAE and /3GB
switches in our boot.ini in order to enable 6gigs to our sql server
or /PAE will okay?
kulkarni.ninad@.gmail.com wrote:
> We are going to turn on AWE on our production environment currently
> its 4 processor box with 12GB of RAM and windows advanced server 2000
> loaded on it. Now my question is do i need to use /PAE and /3GB
> switches in our boot.ini in order to enable 6gigs to our sql server
> or /PAE will okay?
>
With 6Gb of RAM, I would use the /3GB switch as well. That would
effectively allow SQL to use as much as 5GB. Without the /3Gb switch
you are pretty well limited to 4Gb.
|||That is not really true. /3GB allows SQL Server (or any properly enabled
application) to use up to 3GB of the 4GB of directly addressable memory but
limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
the App to see memory above 4GB and is totally independent of the /3GB
switch. The decision to use /3GB or not is dependent on how much of that
directly addressable memory you need to use. The only part of SQL Server
that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
cache. I would question why he wants to use only 6GB when he has 12
available. I suspect he may be in a cluster and if that is true and it is
Active-Active then 6GB may be too much since AWE memory is fixed and can not
be dynamically adjusted.
Andrew J. Kelly SQL MVP
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message
news:uEmOq6LbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> kulkarni.ninad@.gmail.com wrote:
> With 6Gb of RAM, I would use the /3GB switch as well. That would
> effectively allow SQL to use as much as 5GB. Without the /3Gb switch you
> are pretty well limited to 4Gb.
|||Andrew J. Kelly wrote:
> That is not really true. /3GB allows SQL Server (or any properly enabled
> application) to use up to 3GB of the 4GB of directly addressable memory but
> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
> the App to see memory above 4GB and is totally independent of the /3GB
> switch. The decision to use /3GB or not is dependent on how much of that
> directly addressable memory you need to use. The only part of SQL Server
> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
> cache. I would question why he wants to use only 6GB when he has 12
> available. I suspect he may be in a cluster and if that is true and it is
> Active-Active then 6GB may be too much since AWE memory is fixed and can not
> be dynamically adjusted.
>
My thinking was that there was only 6Gb and if you didn't use the /3Gb
switch, then the OS would effectively take the full 2Gb available to it,
leaving 4Gb for applications such as SQL. While using the /3Gb switch
would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
However, now I see that there is actually 12Gb...
With 12Gb you don't need the /3Gb switch in order to allow SQL to see
6Gb (actually it could use 10Gb), however, I have to wonder why you want
to limit SQL to 6Gb when you have 12?
I think my recommendation still stands though, because if I recall, it's
not until you have over 16Gb of RAM that the OS has to use that extra Gb
of space to maintain the Address Extensions.
So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
10Gb without it. Although I'd keep a close eye on things to make sure
that the OS is not having to do a bunch of swapping. In certain
circumstances the OS might be able to make better use of that Gb than SQL.
its 4 processor box with 12GB of RAM and windows advanced server 2000
loaded on it. Now my question is do i need to use /PAE and /3GB
switches in our boot.ini in order to enable 6gigs to our sql server
or /PAE will okay?
kulkarni.ninad@.gmail.com wrote:
> We are going to turn on AWE on our production environment currently
> its 4 processor box with 12GB of RAM and windows advanced server 2000
> loaded on it. Now my question is do i need to use /PAE and /3GB
> switches in our boot.ini in order to enable 6gigs to our sql server
> or /PAE will okay?
>
With 6Gb of RAM, I would use the /3GB switch as well. That would
effectively allow SQL to use as much as 5GB. Without the /3Gb switch
you are pretty well limited to 4Gb.
|||That is not really true. /3GB allows SQL Server (or any properly enabled
application) to use up to 3GB of the 4GB of directly addressable memory but
limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
the App to see memory above 4GB and is totally independent of the /3GB
switch. The decision to use /3GB or not is dependent on how much of that
directly addressable memory you need to use. The only part of SQL Server
that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
cache. I would question why he wants to use only 6GB when he has 12
available. I suspect he may be in a cluster and if that is true and it is
Active-Active then 6GB may be too much since AWE memory is fixed and can not
be dynamically adjusted.
Andrew J. Kelly SQL MVP
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message
news:uEmOq6LbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> kulkarni.ninad@.gmail.com wrote:
> With 6Gb of RAM, I would use the /3GB switch as well. That would
> effectively allow SQL to use as much as 5GB. Without the /3Gb switch you
> are pretty well limited to 4Gb.
|||Andrew J. Kelly wrote:
> That is not really true. /3GB allows SQL Server (or any properly enabled
> application) to use up to 3GB of the 4GB of directly addressable memory but
> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
> the App to see memory above 4GB and is totally independent of the /3GB
> switch. The decision to use /3GB or not is dependent on how much of that
> directly addressable memory you need to use. The only part of SQL Server
> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
> cache. I would question why he wants to use only 6GB when he has 12
> available. I suspect he may be in a cluster and if that is true and it is
> Active-Active then 6GB may be too much since AWE memory is fixed and can not
> be dynamically adjusted.
>
My thinking was that there was only 6Gb and if you didn't use the /3Gb
switch, then the OS would effectively take the full 2Gb available to it,
leaving 4Gb for applications such as SQL. While using the /3Gb switch
would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
However, now I see that there is actually 12Gb...
With 12Gb you don't need the /3Gb switch in order to allow SQL to see
6Gb (actually it could use 10Gb), however, I have to wonder why you want
to limit SQL to 6Gb when you have 12?
I think my recommendation still stands though, because if I recall, it's
not until you have over 16Gb of RAM that the OS has to use that extra Gb
of space to maintain the Address Extensions.
So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
10Gb without it. Although I'd keep a close eye on things to make sure
that the OS is not having to do a bunch of swapping. In certain
circumstances the OS might be able to make better use of that Gb than SQL.
awe question
We are going to turn on AWE on our production environment currently
its 4 processor box with 12GB of RAM and windows advanced server 2000
loaded on it. Now my question is do i need to use /PAE and /3GB
switches in our boot.ini in order to enable 6gigs to our sql server
or /PAE will okay?kulkarni.ninad@.gmail.com wrote:
> We are going to turn on AWE on our production environment currently
> its 4 processor box with 12GB of RAM and windows advanced server 2000
> loaded on it. Now my question is do i need to use /PAE and /3GB
> switches in our boot.ini in order to enable 6gigs to our sql server
> or /PAE will okay?
>
With 6Gb of RAM, I would use the /3GB switch as well. That would
effectively allow SQL to use as much as 5GB. Without the /3Gb switch
you are pretty well limited to 4Gb.|||That is not really true. /3GB allows SQL Server (or any properly enabled
application) to use up to 3GB of the 4GB of directly addressable memory but
limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
the App to see memory above 4GB and is totally independent of the /3GB
switch. The decision to use /3GB or not is dependent on how much of that
directly addressable memory you need to use. The only part of SQL Server
that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
cache. I would question why he wants to use only 6GB when he has 12
available. I suspect he may be in a cluster and if that is true and it is
Active-Active then 6GB may be too much since AWE memory is fixed and can not
be dynamically adjusted.
--
Andrew J. Kelly SQL MVP
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message
news:uEmOq6LbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> kulkarni.ninad@.gmail.com wrote:
>> We are going to turn on AWE on our production environment currently
>> its 4 processor box with 12GB of RAM and windows advanced server 2000
>> loaded on it. Now my question is do i need to use /PAE and /3GB
>> switches in our boot.ini in order to enable 6gigs to our sql server
>> or /PAE will okay?
> With 6Gb of RAM, I would use the /3GB switch as well. That would
> effectively allow SQL to use as much as 5GB. Without the /3Gb switch you
> are pretty well limited to 4Gb.|||Andrew J. Kelly wrote:
> That is not really true. /3GB allows SQL Server (or any properly enabled
> application) to use up to 3GB of the 4GB of directly addressable memory but
> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
> the App to see memory above 4GB and is totally independent of the /3GB
> switch. The decision to use /3GB or not is dependent on how much of that
> directly addressable memory you need to use. The only part of SQL Server
> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
> cache. I would question why he wants to use only 6GB when he has 12
> available. I suspect he may be in a cluster and if that is true and it is
> Active-Active then 6GB may be too much since AWE memory is fixed and can not
> be dynamically adjusted.
>
My thinking was that there was only 6Gb and if you didn't use the /3Gb
switch, then the OS would effectively take the full 2Gb available to it,
leaving 4Gb for applications such as SQL. While using the /3Gb switch
would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
However, now I see that there is actually 12Gb...
With 12Gb you don't need the /3Gb switch in order to allow SQL to see
6Gb (actually it could use 10Gb), however, I have to wonder why you want
to limit SQL to 6Gb when you have 12?
I think my recommendation still stands though, because if I recall, it's
not until you have over 16Gb of RAM that the OS has to use that extra Gb
of space to maintain the Address Extensions.
So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
10Gb without it. Although I'd keep a close eye on things to make sure
that the OS is not having to do a bunch of swapping. In certain
circumstances the OS might be able to make better use of that Gb than SQL.|||> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
I believe that Unisys has recommendations to not use /3GB if you have > 12GB in the machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message news:uhqohQYbHHA.588@.TK2MSFTNGP06.phx.gbl...
> Andrew J. Kelly wrote:
>> That is not really true. /3GB allows SQL Server (or any properly enabled
>> application) to use up to 3GB of the 4GB of directly addressable memory but
>> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
>> the App to see memory above 4GB and is totally independent of the /3GB
>> switch. The decision to use /3GB or not is dependent on how much of that
>> directly addressable memory you need to use. The only part of SQL Server
>> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
>> cache. I would question why he wants to use only 6GB when he has 12
>> available. I suspect he may be in a cluster and if that is true and it is
>> Active-Active then 6GB may be too much since AWE memory is fixed and can not
>> be dynamically adjusted.
> My thinking was that there was only 6Gb and if you didn't use the /3Gb
> switch, then the OS would effectively take the full 2Gb available to it,
> leaving 4Gb for applications such as SQL. While using the /3Gb switch
> would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
> However, now I see that there is actually 12Gb...
> With 12Gb you don't need the /3Gb switch in order to allow SQL to see
> 6Gb (actually it could use 10Gb), however, I have to wonder why you want
> to limit SQL to 6Gb when you have 12?
> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
> So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
> 10Gb without it. Although I'd keep a close eye on things to make sure
> that the OS is not having to do a bunch of swapping. In certain
> circumstances the OS might be able to make better use of that Gb than SQL.
its 4 processor box with 12GB of RAM and windows advanced server 2000
loaded on it. Now my question is do i need to use /PAE and /3GB
switches in our boot.ini in order to enable 6gigs to our sql server
or /PAE will okay?kulkarni.ninad@.gmail.com wrote:
> We are going to turn on AWE on our production environment currently
> its 4 processor box with 12GB of RAM and windows advanced server 2000
> loaded on it. Now my question is do i need to use /PAE and /3GB
> switches in our boot.ini in order to enable 6gigs to our sql server
> or /PAE will okay?
>
With 6Gb of RAM, I would use the /3GB switch as well. That would
effectively allow SQL to use as much as 5GB. Without the /3Gb switch
you are pretty well limited to 4Gb.|||That is not really true. /3GB allows SQL Server (or any properly enabled
application) to use up to 3GB of the 4GB of directly addressable memory but
limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
the App to see memory above 4GB and is totally independent of the /3GB
switch. The decision to use /3GB or not is dependent on how much of that
directly addressable memory you need to use. The only part of SQL Server
that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
cache. I would question why he wants to use only 6GB when he has 12
available. I suspect he may be in a cluster and if that is true and it is
Active-Active then 6GB may be too much since AWE memory is fixed and can not
be dynamically adjusted.
--
Andrew J. Kelly SQL MVP
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message
news:uEmOq6LbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> kulkarni.ninad@.gmail.com wrote:
>> We are going to turn on AWE on our production environment currently
>> its 4 processor box with 12GB of RAM and windows advanced server 2000
>> loaded on it. Now my question is do i need to use /PAE and /3GB
>> switches in our boot.ini in order to enable 6gigs to our sql server
>> or /PAE will okay?
> With 6Gb of RAM, I would use the /3GB switch as well. That would
> effectively allow SQL to use as much as 5GB. Without the /3Gb switch you
> are pretty well limited to 4Gb.|||Andrew J. Kelly wrote:
> That is not really true. /3GB allows SQL Server (or any properly enabled
> application) to use up to 3GB of the 4GB of directly addressable memory but
> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
> the App to see memory above 4GB and is totally independent of the /3GB
> switch. The decision to use /3GB or not is dependent on how much of that
> directly addressable memory you need to use. The only part of SQL Server
> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
> cache. I would question why he wants to use only 6GB when he has 12
> available. I suspect he may be in a cluster and if that is true and it is
> Active-Active then 6GB may be too much since AWE memory is fixed and can not
> be dynamically adjusted.
>
My thinking was that there was only 6Gb and if you didn't use the /3Gb
switch, then the OS would effectively take the full 2Gb available to it,
leaving 4Gb for applications such as SQL. While using the /3Gb switch
would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
However, now I see that there is actually 12Gb...
With 12Gb you don't need the /3Gb switch in order to allow SQL to see
6Gb (actually it could use 10Gb), however, I have to wonder why you want
to limit SQL to 6Gb when you have 12?
I think my recommendation still stands though, because if I recall, it's
not until you have over 16Gb of RAM that the OS has to use that extra Gb
of space to maintain the Address Extensions.
So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
10Gb without it. Although I'd keep a close eye on things to make sure
that the OS is not having to do a bunch of swapping. In certain
circumstances the OS might be able to make better use of that Gb than SQL.|||> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
I believe that Unisys has recommendations to not use /3GB if you have > 12GB in the machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Don Peterson" <sgtp.usmc@.gmail.com> wrote in message news:uhqohQYbHHA.588@.TK2MSFTNGP06.phx.gbl...
> Andrew J. Kelly wrote:
>> That is not really true. /3GB allows SQL Server (or any properly enabled
>> application) to use up to 3GB of the 4GB of directly addressable memory but
>> limits the OS to 1GB of that same space. AWE and PAE are to allow the OS and
>> the App to see memory above 4GB and is totally independent of the /3GB
>> switch. The decision to use /3GB or not is dependent on how much of that
>> directly addressable memory you need to use. The only part of SQL Server
>> that can use memory above 2GB (or 3GB with the /3GB) is the data buffer
>> cache. I would question why he wants to use only 6GB when he has 12
>> available. I suspect he may be in a cluster and if that is true and it is
>> Active-Active then 6GB may be too much since AWE memory is fixed and can not
>> be dynamically adjusted.
> My thinking was that there was only 6Gb and if you didn't use the /3Gb
> switch, then the OS would effectively take the full 2Gb available to it,
> leaving 4Gb for applications such as SQL. While using the /3Gb switch
> would limit the OS to 1Gb, thereby allowing SQL to use a full 5Gb.
> However, now I see that there is actually 12Gb...
> With 12Gb you don't need the /3Gb switch in order to allow SQL to see
> 6Gb (actually it could use 10Gb), however, I have to wonder why you want
> to limit SQL to 6Gb when you have 12?
> I think my recommendation still stands though, because if I recall, it's
> not until you have over 16Gb of RAM that the OS has to use that extra Gb
> of space to maintain the Address Extensions.
> So, using the /3Gb switch would allow SQL to use up to 11Gb instead of
> 10Gb without it. Although I'd keep a close eye on things to make sure
> that the OS is not having to do a bunch of swapping. In certain
> circumstances the OS might be able to make better use of that Gb than SQL.
AWE on SQL Server 2000 & 2005
I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
AWE on SQL Server 2000 & 2005
I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBA
You need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA
|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBA
You need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA
|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
AWE on SQL Server 2000 & 2005
I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
--
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
--
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
>> 2000 Enterprose I would like to use AWE,
>> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
>> SQL
>> 2005 Enterprose I would like to use AWE,
>> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> --
>> SQL serer DBA
>
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
--
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
--
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
>> 2000 Enterprose I would like to use AWE,
>> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
>> SQL
>> 2005 Enterprose I would like to use AWE,
>> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> --
>> SQL serer DBA
>
AWE Memory: Seeing approx. 1 Gig less than expected
I am runnning a dedicated SQL Server 2005 Standard edition server on Win 200
3,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, bu
t
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB i
n
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1
3,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, bu
t
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB i
n
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1
AWE Memory: Seeing approx. 1 Gig less than expected
I am runnning a dedicated SQL Server 2005 Standard edition server on Win 2003,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
AWE Memory: Seeing approx. 1 Gig less than expected
I am runnning a dedicated SQL Server 2005 Standard edition server on Win 2003,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
>>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
>[quoted text clipped - 20 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
>>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
>[quoted text clipped - 20 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
Wednesday, March 7, 2012
AWE MEM
Hi ,
I have win2k server with 4 GB Ram
enabled /3gb switch to use all RAM
SQL SERVER 2K enterprise edition
enabled awe switch .
When started sql server it occupied only 2GB not all
is it correct .'
Thanks
ARRHi,
I don't think you need to enable AWE, /3GB swith is enough for 4 GB Memory..
And from where you are monitoring SQL mem usage. Task Manager shows
incorrect values sometimes, use Performance Monitor- SQL Server:Memory
Manager:Total Server Memory instead..
"Aju" wrote:
> Hi ,
> I have win2k server with 4 GB Ram
> enabled /3gb switch to use all RAM
> SQL SERVER 2K enterprise edition
> enabled awe switch .
> When started sql server it occupied only 2GB not all
> is it correct .'
> Thanks
> ARR
>
>|||The /3GB switch will allow Sql server to use up to 3GB of the 4 but only if
you are running Win2K Adv Server or higher. If it is std server you can
only use 2GB for Sql Server. You should turn off AWE and leave the rest for
the OS and any other apps running.
--
Andrew J. Kelly SQL MVP
"Aju" <ajuonline@.yahoo.com> wrote in message
news:e1SBmT8HFHA.2976@.TK2MSFTNGP15.phx.gbl...
> Hi ,
> I have win2k server with 4 GB Ram
> enabled /3gb switch to use all RAM
> SQL SERVER 2K enterprise edition
> enabled awe switch .
> When started sql server it occupied only 2GB not all
> is it correct .'
> Thanks
> ARR
>|||If you are running only Win2K Standard Edition, /3GB option is not
supported. However, with 4 GB ram and SS2K EE, you should still be able to
use AWE, either 2 GB lower, up to 2 GB AWE, or 3 GB lower and up to 1 GB AWE
depending on the /3GB switch setting.
Also check out the SQL Server:Memory Manager, Target Server Memory. If this
value is not larger than Total Server Memory, the BPool does not know to
grow.
Finally, you have to RECONFIGURE and RESTART before the enable AWE takes
effect.
Sincerely,
Anthony Thomas
"Umut Nazlica" <UmutNazlica@.discussions.microsoft.com> wrote in message
news:F53E1E3D-F422-4187-9FCC-8067C6432E0D@.microsoft.com...
Hi,
I don't think you need to enable AWE, /3GB swith is enough for 4 GB Memory..
And from where you are monitoring SQL mem usage. Task Manager shows
incorrect values sometimes, use Performance Monitor- SQL Server:Memory
Manager:Total Server Memory instead..
"Aju" wrote:
> Hi ,
> I have win2k server with 4 GB Ram
> enabled /3gb switch to use all RAM
> SQL SERVER 2K enterprise edition
> enabled awe switch .
> When started sql server it occupied only 2GB not all
> is it correct .'
> Thanks
> ARR
>
>
I have win2k server with 4 GB Ram
enabled /3gb switch to use all RAM
SQL SERVER 2K enterprise edition
enabled awe switch .
When started sql server it occupied only 2GB not all
is it correct .'
Thanks
ARRHi,
I don't think you need to enable AWE, /3GB swith is enough for 4 GB Memory..
And from where you are monitoring SQL mem usage. Task Manager shows
incorrect values sometimes, use Performance Monitor- SQL Server:Memory
Manager:Total Server Memory instead..
"Aju" wrote:
> Hi ,
> I have win2k server with 4 GB Ram
> enabled /3gb switch to use all RAM
> SQL SERVER 2K enterprise edition
> enabled awe switch .
> When started sql server it occupied only 2GB not all
> is it correct .'
> Thanks
> ARR
>
>|||The /3GB switch will allow Sql server to use up to 3GB of the 4 but only if
you are running Win2K Adv Server or higher. If it is std server you can
only use 2GB for Sql Server. You should turn off AWE and leave the rest for
the OS and any other apps running.
--
Andrew J. Kelly SQL MVP
"Aju" <ajuonline@.yahoo.com> wrote in message
news:e1SBmT8HFHA.2976@.TK2MSFTNGP15.phx.gbl...
> Hi ,
> I have win2k server with 4 GB Ram
> enabled /3gb switch to use all RAM
> SQL SERVER 2K enterprise edition
> enabled awe switch .
> When started sql server it occupied only 2GB not all
> is it correct .'
> Thanks
> ARR
>|||If you are running only Win2K Standard Edition, /3GB option is not
supported. However, with 4 GB ram and SS2K EE, you should still be able to
use AWE, either 2 GB lower, up to 2 GB AWE, or 3 GB lower and up to 1 GB AWE
depending on the /3GB switch setting.
Also check out the SQL Server:Memory Manager, Target Server Memory. If this
value is not larger than Total Server Memory, the BPool does not know to
grow.
Finally, you have to RECONFIGURE and RESTART before the enable AWE takes
effect.
Sincerely,
Anthony Thomas
"Umut Nazlica" <UmutNazlica@.discussions.microsoft.com> wrote in message
news:F53E1E3D-F422-4187-9FCC-8067C6432E0D@.microsoft.com...
Hi,
I don't think you need to enable AWE, /3GB swith is enough for 4 GB Memory..
And from where you are monitoring SQL mem usage. Task Manager shows
incorrect values sometimes, use Performance Monitor- SQL Server:Memory
Manager:Total Server Memory instead..
"Aju" wrote:
> Hi ,
> I have win2k server with 4 GB Ram
> enabled /3gb switch to use all RAM
> SQL SERVER 2K enterprise edition
> enabled awe switch .
> When started sql server it occupied only 2GB not all
> is it correct .'
> Thanks
> ARR
>
>
Subscribe to:
Posts (Atom)