Autonumber field: pae

Showing posts with label pae. Show all posts

Sunday, March 11, 2012

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 vs PAE

guys,
what is the difference between AWE and PAE?PAE allows the OS to use more than 4GB of memory. AWE allows the
application to use more than 4GB.
Andrew J. Kelly SQL MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
> guys,
> what is the difference between AWE and PAE?|||for SQL server, shd i enable PAE or AWE? Can both be enabled at the same tim
e?
"Andrew J. Kelly" wrote:

> PAE allows the OS to use more than 4GB of memory. AWE allows the
> application to use more than 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
>
>|||AWE is a SQL Server setting (sp_configure) and PAE is an operating system se
tting (BOOT.INI). If you
want SQL Server to utilize > 4GB memory, you need both settings.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...[vbcol=seagreen]
> for SQL server, shd i enable PAE or AWE? Can both be enabled at the same t
ime?
> "Andrew J. Kelly" wrote:
>|||in that case...in a server with 5G of ram
should i put the /AWE /PAE swith in the same line in the boot.ini?
For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
how do i check it has 5G? Also, is there any significant on it? The
performance shd be better i suppose
Thank you
"Tibor Karaszi" wrote:

> AWE is a SQL Server setting (sp_configure) and PAE is an operating system
setting (BOOT.INI). If you
> want SQL Server to utilize > 4GB memory, you need both settings.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...
>
>|||boot.ini should have something like this:
multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
Enterprise" /fastdetect /pae /3gb
(The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
provide a little more to the apps, i.e. SQL Server.)
To check the amount of physical RAM the OS is seeing you can just check
the Performance tab in task manager.
To turn on AWE memory for SQL Server you use the sp_configure stored
proc (in Query Analyzer for example):
exec sp_configure 'awe enabled', 1
reconfigure
go
Then you have to restart the SQL instance as the AWE setting only takes
affect on server startup. Also, when SQL Server is using AWE memory, it
cannot use dynamic memory management. It *will not swap pages out of
memory *if another app requests memory and the OS doesn't have enough to
satisfy the request (unlike the SQL dynamic memory manager). So you
should specify a "max server memory" amount with sp_configure. For
example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
remaining 1GB to the OS & other apps, you would do this in QA:
exec sp_configure "max server memory", 5120
reconfigure
go
All this is documented in SQL BOL:
http://msdn.microsoft.com/library/d... />
g_3stg.asp
To see how much memory SQL Server is currently consuming you can open
the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
AWE & memory management.
HTH
*mike hodgson*
/ mallesons stephen jaques/
blog: http://sqlnerd.blogspot.com
rupart wrote:
[vbcol=seagreen]
>in that case...in a server with 5G of ram
>should i put the /AWE /PAE swith in the same line in the boot.ini?
>For the OS, i can see under system mgmt that 5G is enabled. How abt for sql
?
>how do i check it has 5G? Also, is there any significant on it? The
>performance shd be better i suppose
>Thank you
>"Tibor Karaszi" wrote:
>
>|||does /3g means the system will allocate 3g for system and the rest for
sql(that is after enabling thru AWE, rite?)?
yeah, good link...thank you
"Mike Hodgson" wrote:

> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just check
> the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only takes
> affect on server startup. Also, when SQL Server is using AWE memory, it
> cannot use dynamic memory management. It *will not swap pages out of
> memory *if another app requests memory and the OS doesn't have enough to
> satisfy the request (unlike the SQL dynamic memory manager). So you
> should specify a "max server memory" amount with sp_configure. For
> example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
> remaining 1GB to the OS & other apps, you would do this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/d...>
fig_3stg.asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
> AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
>|||The other way around. 3 GB for the application and 1 GB for the system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:4944B057-1DC7-4638-BB88-9040FDCC9B9F@.microsoft.com...[vbcol=seagreen]
> does /3g means the system will allocate 3g for system and the rest for
> sql(that is after enabling thru AWE, rite?)?
> yeah, good link...thank you
> "Mike Hodgson" wrote:
>|||Oops - slight typo in my "max server memory" statement. To set a max
server memory of 4GB you would run:
exec sp_configure "max server memory", 4096
reconfigure
go
The 5120 figure I included in my previous post would try to set it at
5GB (not 4GB).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Mike Hodgson wrote:
[vbcol=seagreen]
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WIND
OWS="Windows Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just
> check the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only
> takes affect on server startup. Also, when SQL Server is using AWE
> memory, it cannot use dynamic memory management. It *will not swap
> pages out of memory *if another app requests memory and the OS doesn't
> have enough to satisfy the request (unlike the SQL dynamic memory
> manager). So you should specify a "max server memory" amount with
> sp_configure. For example, on your 5GB box, if you wanted to allocate
> 4GB to SQL and the remaining 1GB to the OS & other apps, you would do
> this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/d...
fig_3stg..asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff
> on AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>

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.
>

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.
>

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.
>

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
> >>
> >>
> >>
> >>
> >
> >
> >.
> >

AWE on Windows 64 Bit

Hi,
By having 6GB memory on Windows 2003 64 bit:
1) Do I have to add /PAE switch to boot.ini ?
2) What about AWE option for SQL Server, it must be enabled?
Thanks in advance,
LeilaIs SQL Server 64 bit? If so, you don't need any of those settings (AWE will be ignored if set).
However, you might benefit if service account has "lock pages in memory" privileges.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Leila" <Leilas@.hotpop.com> wrote in message news:Ol%23hWXRhHHA.984@.TK2MSFTNGP04.phx.gbl...
> Hi,
> By having 6GB memory on Windows 2003 64 bit:
> 1) Do I have to add /PAE switch to boot.ini ?
> 2) What about AWE option for SQL Server, it must be enabled?
> Thanks in advance,
> Leila
>|||Thanks Tibor,
Yes SQL Server is 64 bit. If it's 32 bit AWE is required?
Is /3GB switch still beneficial for SQL Server in 64 bit environment?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ut0F$fRhHHA.960@.TK2MSFTNGP03.phx.gbl...
> Is SQL Server 64 bit? If so, you don't need any of those settings (AWE
> will be ignored if set). However, you might benefit if service account has
> "lock pages in memory" privileges.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:Ol%23hWXRhHHA.984@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> By having 6GB memory on Windows 2003 64 bit:
>> 1) Do I have to add /PAE switch to boot.ini ?
>> 2) What about AWE option for SQL Server, it must be enabled?
>> Thanks in advance,
>> Leila
>>
>|||> Is /3GB switch still beneficial for SQL Server in 64 bit environment?
No, such a switch is irrelevant in 64 bit.
> If it's 32 bit AWE is required?
Yes, if you want to utilize > 4GB memory. PAE is not needed, though Note, this applies to 32 bit SQL
Server in 64 bit OS (x64, architecture).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Leila" <Leilas@.hotpop.com> wrote in message news:OlP9cnRhHHA.4132@.TK2MSFTNGP05.phx.gbl...
> Thanks Tibor,
> Yes SQL Server is 64 bit. If it's 32 bit AWE is required?
> Is /3GB switch still beneficial for SQL Server in 64 bit environment?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:ut0F$fRhHHA.960@.TK2MSFTNGP03.phx.gbl...
>> Is SQL Server 64 bit? If so, you don't need any of those settings (AWE will be ignored if set).
>> However, you might benefit if service account has "lock pages in memory" privileges.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Leila" <Leilas@.hotpop.com> wrote in message news:Ol%23hWXRhHHA.984@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> By having 6GB memory on Windows 2003 64 bit:
>> 1) Do I have to add /PAE switch to boot.ini ?
>> 2) What about AWE option for SQL Server, it must be enabled?
>> Thanks in advance,
>> Leila
>>
>|||> No, such a switch is irrelevant in 64 bit.
Could you please explain it? AFAIK, 3GB switch forces OS to use only 1GB for
kernel mode. Therefore still it must be useable for 64 bit. Is it wrong?
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OFpOezRhHHA.4444@.TK2MSFTNGP04.phx.gbl...
>> Is /3GB switch still beneficial for SQL Server in 64 bit environment?
> No, such a switch is irrelevant in 64 bit.
>
>> If it's 32 bit AWE is required?
> Yes, if you want to utilize > 4GB memory. PAE is not needed, though Note,
> this applies to 32 bit SQL Server in 64 bit OS (x64, architecture).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:OlP9cnRhHHA.4132@.TK2MSFTNGP05.phx.gbl...
>> Thanks Tibor,
>> Yes SQL Server is 64 bit. If it's 32 bit AWE is required?
>> Is /3GB switch still beneficial for SQL Server in 64 bit environment?
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:ut0F$fRhHHA.960@.TK2MSFTNGP03.phx.gbl...
>> Is SQL Server 64 bit? If so, you don't need any of those settings (AWE
>> will be ignored if set). However, you might benefit if service account
>> has "lock pages in memory" privileges.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Leila" <Leilas@.hotpop.com> wrote in message
>> news:Ol%23hWXRhHHA.984@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> By having 6GB memory on Windows 2003 64 bit:
>> 1) Do I have to add /PAE switch to boot.ini ?
>> 2) What about AWE option for SQL Server, it must be enabled?
>> Thanks in advance,
>> Leila
>>
>>
>|||32 bit has a limitation of only being able to directly address 4GB of
memory. Beyond that it requires PAE for the OS and AWE for the apps to use
the extra memory. By default 32 bit apps can only use 2 of that 4GB and the
OS uses 2GB. With 64 bit the directly addressable memory is way beyond what
the app or OS will use in the near future. As such there is no need for the
/3GB since any 64 bit app can address all it wants as can the OS.
--
Andrew J. Kelly SQL MVP
"Leila" <Leilas@.hotpop.com> wrote in message
news:uWXaG%23RhHHA.984@.TK2MSFTNGP04.phx.gbl...
>> No, such a switch is irrelevant in 64 bit.
> Could you please explain it? AFAIK, 3GB switch forces OS to use only 1GB
> for kernel mode. Therefore still it must be useable for 64 bit. Is it
> wrong?
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:OFpOezRhHHA.4444@.TK2MSFTNGP04.phx.gbl...
>> Is /3GB switch still beneficial for SQL Server in 64 bit environment?
>> No, such a switch is irrelevant in 64 bit.
>>
>> If it's 32 bit AWE is required?
>> Yes, if you want to utilize > 4GB memory. PAE is not needed, though Note,
>> this applies to 32 bit SQL Server in 64 bit OS (x64, architecture).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Leila" <Leilas@.hotpop.com> wrote in message
>> news:OlP9cnRhHHA.4132@.TK2MSFTNGP05.phx.gbl...
>> Thanks Tibor,
>> Yes SQL Server is 64 bit. If it's 32 bit AWE is required?
>> Is /3GB switch still beneficial for SQL Server in 64 bit environment?
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:ut0F$fRhHHA.960@.TK2MSFTNGP03.phx.gbl...
>> Is SQL Server 64 bit? If so, you don't need any of those settings (AWE
>> will be ignored if set). However, you might benefit if service account
>> has "lock pages in memory" privileges.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Leila" <Leilas@.hotpop.com> wrote in message
>> news:Ol%23hWXRhHHA.984@.TK2MSFTNGP04.phx.gbl...
>> Hi,
>> By having 6GB memory on Windows 2003 64 bit:
>> 1) Do I have to add /PAE switch to boot.ini ?
>> 2) What about AWE option for SQL Server, it must be enabled?
>> Thanks in advance,
>> Leila
>>
>>
>>
>

AWE on Windows 64 Bit

AWE on SQL 2005 and W 2003 Enterprise Server

I have 8 GB on a Windows 2003 Enterprise Server running SQL 2005. I have
added /PAE to the boot.ini file and changed the max memory on SQL to 6800
MB. I start the SQL Service with a separate account that has Lock Memory
privilege. How can I tell if I have set it up right. When I do a "dbcc
memorystatus" I am not sure what to look for. It seems that I am still only
using 1.7 GB of memory.
Thanks,
TomHello Tom,
It's a x86 system right? If so...
Connect to your Instance using SSMS and go to Server Properties. Go to
Memory from the left pane and click Running Values. Be sure AWE is still
selected. This will make you sure that AWE is being used by SQL Server.
You restarted your Server after adding PAE switch, right?
If you did not add 3GB switch, then your OS is still going to be using 2GB
of RAM. So you can not make your SQL Server use 7GB over 8GB of RAM.
If this stuff is OK and your server is SQL Server dedicated server (which
means there will not be running another application on that server and that
server serves only for queries against databases on SQL Server) then
everything should be fine.
Ekrem Önsoy
"tom" <tom@.pcreducator.com> wrote in message
news:%23tUja9WBIHA.4752@.TK2MSFTNGP04.phx.gbl...
>I have 8 GB on a Windows 2003 Enterprise Server running SQL 2005. I have
>added /PAE to the boot.ini file and changed the max memory on SQL to 6800
>MB. I start the SQL Service with a separate account that has Lock Memory
>privilege. How can I tell if I have set it up right. When I do a "dbcc
>memorystatus" I am not sure what to look for. It seems that I am still only
>using 1.7 GB of memory.
> Thanks,
> Tom
>|||Ekrem,
Thanks for your response.
Yes, it's 32-bit and I did reboot after adding the /PAE switch. It turns out
that after I did some more extensive testing, and watching the performance
monitor of "Total Server Memory" under "SQL Server: Memory Manager", I was
able to see the memory go higher than 1.7 GB.
Tom
"Ekrem Önsoy" <ekrem@.btegitim.com> wrote in message
news:909509D4-D31B-4ABD-9E38-980994F9C58F@.microsoft.com...
> Hello Tom,
>
> It's a x86 system right? If so...
> Connect to your Instance using SSMS and go to Server Properties. Go to
> Memory from the left pane and click Running Values. Be sure AWE is still
> selected. This will make you sure that AWE is being used by SQL Server.
> You restarted your Server after adding PAE switch, right?
> If you did not add 3GB switch, then your OS is still going to be using 2GB
> of RAM. So you can not make your SQL Server use 7GB over 8GB of RAM.
> If this stuff is OK and your server is SQL Server dedicated server (which
> means there will not be running another application on that server and
> that server serves only for queries against databases on SQL Server) then
> everything should be fine.
>
> --
> Ekrem Önsoy
>
> "tom" <tom@.pcreducator.com> wrote in message
> news:%23tUja9WBIHA.4752@.TK2MSFTNGP04.phx.gbl...
>>I have 8 GB on a Windows 2003 Enterprise Server running SQL 2005. I have
>>added /PAE to the boot.ini file and changed the max memory on SQL to 6800
>>MB. I start the SQL Service with a separate account that has Lock Memory
>>privilege. How can I tell if I have set it up right. When I do a "dbcc
>>memorystatus" I am not sure what to look for. It seems that I am still
>>only using 1.7 GB of memory.
>> Thanks,
>> Tom
>

AWE Memory

Hello
We have 2 servers in a cluster environment with 12 GB each. We install
SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
option. We allocated 7GB for SQL along with enough room for the OS and other
apps currently running on that box. My question is, when I check the Task
manager, it only shows that SQL uses 150Kb for memory although you can see
under memory counters that 7.5 is been used. Why can we not see SQL using
more that 150KB? is there anything wrong in our setting? Below are the Store
procedures used to enable AWE and allocate 7GB.
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 7168
RECONFIGURE
GO
Thanks
Firstly... if you have AWE, you dont need /3GB switch
Now coming to your question: SQL Server when its started it starts
taking memory from 1KB and grows as the resources need more memory...
and once it reaches min server memory, it will never go back to less
than Min Server memory..until you restart the SQL again.
And by configuring 7GB as Max Server memory, you are limiting the SQL
to not consume more than that...
And incase in some scenerio where SQL has any amount of memory and if
OS need some of that.. it will release that memory only if SQL doesnt
need that at that point of time.
So if you see that SQL is using only 150KB, then dont be alarmed.. its
expected behaviour
|||Task manager isn't AWE/PAE aware. Use performance monitor.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dario" <Dario@.discussions.microsoft.com> wrote in message
news:CF884EB2-F09C-4412-8FC9-547CFC6844CC@.microsoft.com...
> Hello
> We have 2 servers in a cluster environment with 12 GB each. We install
> SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
> option. We allocated 7GB for SQL along with enough room for the OS and other
> apps currently running on that box. My question is, when I check the Task
> manager, it only shows that SQL uses 150Kb for memory although you can see
> under memory counters that 7.5 is been used. Why can we not see SQL using
> more that 150KB? is there anything wrong in our setting? Below are the Store
> procedures used to enable AWE and allocate 7GB.
> SP_CONFIGURE 'show advanced options', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'awe enabled', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'max server memory', 7168
> RECONFIGURE
> GO
> Thanks
>
>

AWE Memory

Hello
We have 2 servers in a cluster environment with 12 GB each. We install
SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
option. We allocated 7GB for SQL along with enough room for the OS and other
apps currently running on that box. My question is, when I check the Task
manager, it only shows that SQL uses 150Kb for memory although you can see
under memory counters that 7.5 is been used. Why can we not see SQL using
more that 150KB? is there anything wrong in our setting? Below are the Store
procedures used to enable AWE and allocate 7GB.
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 7168
RECONFIGURE
GO
ThanksFirstly... if you have AWE, you dont need /3GB switch
Now coming to your question: SQL Server when its started it starts
taking memory from 1KB and grows as the resources need more memory...
and once it reaches min server memory, it will never go back to less
than Min Server memory..until you restart the SQL again.
And by configuring 7GB as Max Server memory, you are limiting the SQL
to not consume more than that...
And incase in some scenerio where SQL has any amount of memory and if
OS need some of that.. it will release that memory only if SQL doesnt
need that at that point of time.
So if you see that SQL is using only 150KB, then dont be alarmed.. its
expected behaviour|||Task manager isn't AWE/PAE aware. Use performance monitor.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dario" <Dario@.discussions.microsoft.com> wrote in message
news:CF884EB2-F09C-4412-8FC9-547CFC6844CC@.microsoft.com...
> Hello
> We have 2 servers in a cluster environment with 12 GB each. We install
> SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
> option. We allocated 7GB for SQL along with enough room for the OS and other
> apps currently running on that box. My question is, when I check the Task
> manager, it only shows that SQL uses 150Kb for memory although you can see
> under memory counters that 7.5 is been used. Why can we not see SQL using
> more that 150KB? is there anything wrong in our setting? Below are the Store
> procedures used to enable AWE and allocate 7GB.
> SP_CONFIGURE 'show advanced options', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'awe enabled', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'max server memory', 7168
> RECONFIGURE
> GO
> Thanks
>
>

AWE Memory

Hello
We have 2 servers in a cluster environment with 12 GB each. We install
SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
option. We allocated 7GB for SQL along with enough room for the OS and other
apps currently running on that box. My question is, when I check the Task
manager, it only shows that SQL uses 150Kb for memory although you can see
under memory counters that 7.5 is been used. Why can we not see SQL using
more that 150KB? is there anything wrong in our setting? Below are the Store
procedures used to enable AWE and allocate 7GB.
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 7168
RECONFIGURE
GO
ThanksFirstly... if you have AWE, you dont need /3GB switch
Now coming to your question: SQL Server when its started it starts
taking memory from 1KB and grows as the resources need more memory...
and once it reaches min server memory, it will never go back to less
than Min Server memory..until you restart the SQL again.
And by configuring 7GB as Max Server memory, you are limiting the SQL
to not consume more than that...
And incase in some scenerio where SQL has any amount of memory and if
OS need some of that.. it will release that memory only if SQL doesnt
need that at that point of time.
So if you see that SQL is using only 150KB, then dont be alarmed.. its
expected behaviour|||Task manager isn't AWE/PAE aware. Use performance monitor.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dario" <Dario@.discussions.microsoft.com> wrote in message
news:CF884EB2-F09C-4412-8FC9-547CFC6844CC@.microsoft.com...
> Hello
> We have 2 servers in a cluster environment with 12 GB each. We instal
l
> SQL server 2000 in them and use the switches /3GB /PAE and use AWE enable
> option. We allocated 7GB for SQL along with enough room for the OS and oth
er
> apps currently running on that box. My question is, when I check the Task
> manager, it only shows that SQL uses 150Kb for memory although you can see
> under memory counters that 7.5 is been used. Why can we not see SQL using
> more that 150KB? is there anything wrong in our setting? Below are the Sto
re
> procedures used to enable AWE and allocate 7GB.
> SP_CONFIGURE 'show advanced options', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'awe enabled', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'max server memory', 7168
> RECONFIGURE
> GO
> Thanks
>
>

Wednesday, March 7, 2012

AWE enabled on 64 bit system ?

Do we need to enable AWE on a 64 bit system ?
Do we need to add the /PAE switch ?
Can someone send me the link that specifically talks about these settings on
a 64 bit server , if one exists ? ThanksNo
On true 64 bit Intel Itanium Processor based Systems, there is no need for
AWE /3GB or PAE switches.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> Do we need to enable AWE on a 64 bit system ?
> Do we need to add the /PAE switch ?
> Can someone send me the link that specifically talks about these settings
> on a 64 bit server , if one exists ? Thanks
>|||Although, interestingly enough, enabling 'lock pages in memory' can be
beneficial: http://blogs.msdn.com/slavao/archiv.../31/458545.aspx
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ukm9LtiuFHA.2568@.TK2MSFTNGP15.phx.gbl...
> No
> On true 64 bit Intel Itanium Processor based Systems, there is no need for
> AWE /3GB or PAE switches.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
>

AWE enabled on 64 bit system ?

Do we need to enable AWE on a 64 bit system ?
Do we need to add the /PAE switch ?
Can someone send me the link that specifically talks about these settings on
a 64 bit server , if one exists ? Thanks
No
On true 64 bit Intel Itanium Processor based Systems, there is no need for
AWE /3GB or PAE switches.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> Do we need to enable AWE on a 64 bit system ?
> Do we need to add the /PAE switch ?
> Can someone send me the link that specifically talks about these settings
> on a 64 bit server , if one exists ? Thanks
>
|||Although, interestingly enough, enabling 'lock pages in memory' can be
beneficial: http://blogs.msdn.com/slavao/archive...31/458545.aspx
Thanks,
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ukm9LtiuFHA.2568@.TK2MSFTNGP15.phx.gbl...
> No
> On true 64 bit Intel Itanium Processor based Systems, there is no need for
> AWE /3GB or PAE switches.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
>

AWE enabled on 64 bit system ?

Do we need to enable AWE on a 64 bit system ?
Do we need to add the /PAE switch ?
Can someone send me the link that specifically talks about these settings on
a 64 bit server , if one exists ? ThanksNo
On true 64 bit Intel Itanium Processor based Systems, there is no need for
AWE /3GB or PAE switches.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <hassanboy@.hotmail.com> wrote in message
news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
> Do we need to enable AWE on a 64 bit system ?
> Do we need to add the /PAE switch ?
> Can someone send me the link that specifically talks about these settings
> on a 64 bit server , if one exists ? Thanks
>|||Although, interestingly enough, enabling 'lock pages in memory' can be
beneficial: http://blogs.msdn.com/slavao/archive/2005/08/31/458545.aspx
Thanks,
--
Ryan Stonecipher
Microsoft Sql Server Storage Engine, DBCC
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ukm9LtiuFHA.2568@.TK2MSFTNGP15.phx.gbl...
> No
> On true 64 bit Intel Itanium Processor based Systems, there is no need for
> AWE /3GB or PAE switches.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Hassan" <hassanboy@.hotmail.com> wrote in message
> news:u7c7lKiuFHA.2948@.TK2MSFTNGP15.phx.gbl...
>> Do we need to enable AWE on a 64 bit system ?
>> Do we need to add the /PAE switch ?
>> Can someone send me the link that specifically talks about these settings
>> on a 64 bit server , if one exists ? Thanks
>

AWE enabled

Hi, please let me know if I enable AWE and PAE and turn on /3 GB switch, why
can't I see sqlserver.exe or total/target server memory more that 2.72 GB?
Event though there is a page/sec goes upto 6000. Server must need memory more
than 3 GB. My email address is : atiqur_rahman02@.yahoo.com or you can paste
here. Thanks for your help!
How much memory does your server machine have? What is the version and
edition of the operating system and SQL Server you are using?
Anith

AWE and SQL 2000

Win 2000 server, SQL 2000

What exactly does the /3GB do?

We have added 4GB of RAM to an existing 4, but have not yet added the switch, although /PAE has been in the boot.ini file for some time. (why would that be? THat switch is for the os, isn't it? Does win 2000 not handle the 4GB of RAM?)

In my research, it says that SQL Server will only be able to access 2GB of memory without it, however, there is 4GB on the server now, so won't it continue to use the 4? SHould the switch be different?

Should the switch ever be different? Once you get to 36GB aren't you supposed to leave the switch off, and why?

We are going to upgrade to Win 2003 - is there anything different we will need to do in order to use the full 8GB? It is not planned to enable AWE until we go to Win 2003, although I can't get an answer on why that would be from our server people - is there a known issue on upgrade?

/3GB allows Windows applications that are marked LargeAddressAware (which SS 2000 is) to have 3GB of user virtual address space instead of the usual 2GB. For SQL Server, this is usually a good idea because it greatly reduces problems related to address space management in 32-bits.

If you do not have AWE enabled, the size of the user virtual address space also forms an upper limit on how much physical memory SQL Server can use; if AWE is enabled, then SQL Server can use up to 64GB of physical memory, but still within the confines of either a 2GB or 3GB address space.

I'm not sure why one would only enable AWE for SS 2000 on Win 2003 and not Win 2000. The amount of physical memory used would be fixed in size, and allocated at server startup. Things are different for SS 2005, but that's another story.

AWE and Memory Configuration

We have a database server running Windows 2000 Advanced Server and SQL 2000
Enterprise with 4 CPU and 8MB of memory. PAE has been configured in boot.ini.
AWE has been enabled and 5120 MB of memory allocated to SQL Server default
instance. Everything has been running fine for the last two years.
Now we are planning to add a named instance on the same server for housing
Accounting database. My question is:
1) Do I need to enable AWE on both instances of SQL Server.
2) Set upper memory for both instances. Say 4GB for default instance and
1GB for the new named instance based on their usage ratio. Leave 3GB for OS.
3) Do I need to do anything with CPU allocations?
Any suggestion. Thanks...Fraz
Hi
With 8GB, can configure 1 GB and 5.5GB without starving the OS (as long as
it is a dedicated SQL Server).
/3GB must be set in boot.ini
Set AWE for the instance with 5.5GB, and a fixed memory setting.
Do not set AWE for the 1GB instance, but have a fixed memory setting for it
too.
Leave OS and SQL server to manage CPU allocations and leave the defaults.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:CD4267EB-FF45-4272-B737-6997046F38EC@.microsoft.com...
> We have a database server running Windows 2000 Advanced Server and SQL
> 2000
> Enterprise with 4 CPU and 8MB of memory. PAE has been configured in
> boot.ini.
> AWE has been enabled and 5120 MB of memory allocated to SQL Server default
> instance. Everything has been running fine for the last two years.
> Now we are planning to add a named instance on the same server for housing
> Accounting database. My question is:
> 1) Do I need to enable AWE on both instances of SQL Server.
> 2) Set upper memory for both instances. Say 4GB for default instance and
> 1GB for the new named instance based on their usage ratio. Leave 3GB for
> OS.
> 3) Do I need to do anything with CPU allocations?
> Any suggestion. Thanks...Fraz
>
|||"Fraz" <Fraz@.discussions.microsoft.com> wrote in message
news:CD4267EB-FF45-4272-B737-6997046F38EC@.microsoft.com...
> We have a database server running Windows 2000 Advanced Server and SQL
> 2000
> Enterprise with 4 CPU and 8MB of memory. PAE has been configured in
> boot.ini.
> AWE has been enabled and 5120 MB of memory allocated to SQL Server default
> instance. Everything has been running fine for the last two years.
> Now we are planning to add a named instance on the same server for housing
> Accounting database. My question is:
Why a new instance instead of just adding the database to the default
instance?
How large are these databases? How busy?

> 1) Do I need to enable AWE on both instances of SQL Server.
I would not do that. Either configure the accounting instance to use 2 or
max memory, or mount the database in the main instance. Either one big
instance with AWE, or one big instance with AWE and one small one without.
> 2) Set upper memory for both instances. Say 4GB for default instance and
> 1GB for the new named instance based on their usage ratio. Leave 3GB for
> OS.
The OS doesn't need 3GB. 200-400MB is fine. An instance will "want" a
certian amount of memory depending on its workload and database size.
Giving it more is doesn't help at all; giving it less causes increased
physical IO and a decreased cache hit ratio. AWE is slower than normal
memory, so your smaller instance will run better without AWE. You should
evaluate how much memory your instances really need. Perhaps both instances
will run better with the /3GB switch and AWE off.

> 3) Do I need to do anything with CPU allocations?
If you don't then both instances will share all 4 CPU's, which is lets them
share resources (good), but makes is more difficult to guarantee QOS to
either workload (bad).
If you put the database in the default instance you will share memory and
CPU; in a seperate instance it will not share memory, but will share CPU
unless you set CPU affinity for the instances. So assuming you want to
segregate the instances, you should probably do something with the CPU
affinity.
David
|||I really appreciate your prompt feedback. This satisfies all the questions I
had in my mind. Thanks and cheers. Fraz
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> With 8GB, can configure 1 GB and 5.5GB without starving the OS (as long as
> it is a dedicated SQL Server).
> /3GB must be set in boot.ini
> Set AWE for the instance with 5.5GB, and a fixed memory setting.
> Do not set AWE for the 1GB instance, but have a fixed memory setting for it
> too.
> Leave OS and SQL server to manage CPU allocations and leave the defaults.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:CD4267EB-FF45-4272-B737-6997046F38EC@.microsoft.com...
>
>
|||The new Accounting database (new named instance) will use different collation
setting i.e. Latin1_General, Sort order Binary whereas the default instance
is using Latin1-General, case-insensitive,for use with 1252 Character Set.
The database size in the new named instance is 5GB, it will be more busy in
the month-end than other days. The test system performance statistics (Total
Server Memory) shows that currently this instance is using 300-350MB.
The default instance in production is a busy instance as we have about 25
databases of different sizes from 5GB to 200MB. The performance statistics
for this shows that it is currently using 1.7 - 2.0GB out of allocated 5GB.
For CPU affinity, would it be okay to leave it to the Default setting.
Thanks...Fraz
"David Browne" wrote:

> "Fraz" <Fraz@.discussions.microsoft.com> wrote in message
> news:CD4267EB-FF45-4272-B737-6997046F38EC@.microsoft.com...
> Why a new instance instead of just adding the database to the default
> instance?
> How large are these databases? How busy?
>
> I would not do that. Either configure the accounting instance to use 2 or
> max memory, or mount the database in the main instance. Either one big
> instance with AWE, or one big instance with AWE and one small one without.
> The OS doesn't need 3GB. 200-400MB is fine. An instance will "want" a
> certian amount of memory depending on its workload and database size.
> Giving it more is doesn't help at all; giving it less causes increased
> physical IO and a decreased cache hit ratio. AWE is slower than normal
> memory, so your smaller instance will run better without AWE. You should
> evaluate how much memory your instances really need. Perhaps both instances
> will run better with the /3GB switch and AWE off.
>
> If you don't then both instances will share all 4 CPU's, which is lets them
> share resources (good), but makes is more difficult to guarantee QOS to
> either workload (bad).
> If you put the database in the default instance you will share memory and
> CPU; in a seperate instance it will not share memory, but will share CPU
> unless you set CPU affinity for the instances. So assuming you want to
> segregate the instances, you should probably do something with the CPU
> affinity.
> David
>
>

Sunday, March 11, 2012

AWE, /3gb and /pae stuff

AWE vs PAE

Thursday, March 8, 2012

AWE RAM (SQL 2K not recognizing available AWE RAM)

AWE RAM (SQL 2K not recognizing available AWE RAM)

AWE RAM (SQL 2K not recognizing available AWE RAM)

AWE RAM (SQL 2K not recognizing available AWE RAM)

AWE on Windows 64 Bit

AWE on Windows 64 Bit

AWE on Windows 64 Bit

AWE on SQL 2005 and W 2003 Enterprise Server

AWE Memory

AWE Memory

AWE Memory

Wednesday, March 7, 2012

AWE enabled on 64 bit system ?

AWE enabled on 64 bit system ?

AWE enabled on 64 bit system ?

AWE enabled

AWE and SQL 2000

AWE and Memory Configuration

Autonumber field

Blog Archive

About Me