Autonumber field: boot

Showing posts with label boot. 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

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 question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
Thanks
Alex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>
|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>

AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
ThanksAlex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>> Hello
>> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
>> application installed on it.
>> We also have \3gb parameter in the boot.ini
>>
>> It is a cluster Active/Passive
>> What would you recommenf to insttall a hotfix to Passive first and then
>> Active or it does not matter?
>> Is it any problems installing a hotfix? What is about lock pages in
>> memory?
>> And running AWE enabling on Passive first also?
>>
>> Geoff , how much memory to give to SQL SERVER if small application is
>> using about 50MB AND SQL SERVER 2.7gb?
>> Thanks
>>
>>
>

AWE question (Geoff N. Hiten)

Hello
We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
application installed on it.
We also have \3gb parameter in the boot.ini
It is a cluster Active/Passive
What would you recommenf to insttall a hotfix to Passive first and then
Active or it does not matter?
Is it any problems installing a hotfix? What is about lock pages in memory?
And running AWE enabling on Passive first also?
Geoff , how much memory to give to SQL SERVER if small application is using
about 50MB AND SQL SERVER 2.7gb?
ThanksAlex,
There is no SQL 2004. I am guessing since you mention SP4, that is SQL
2000, since SQL 2005 is only at SP2 for now.
Hotfixes install to all nodes on a cluster for a particular instance. You
need to start the install from the node that is currently hosting the
instance. You must grant lock pages in memory to the SQL service account in
order to get AWE to work. AWE is a setting for the SQL instance, so it will
take effect whichever node hosts that instance.
For an 8GB system, I would start by setting SQL at 6GB and see how free
memory looks. You may be able to inch it up a bit, but it is better to
leave a little extra free memory than to run out. The only down side is
with SQL 2000 you have to stop and restart the service to enact an AWE
memory change.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
> Hello
> We have windows 2003 server (8GB) with SQL Server 2004(sp4) +one small
> application installed on it.
> We also have \3gb parameter in the boot.ini
>
> It is a cluster Active/Passive
> What would you recommenf to insttall a hotfix to Passive first and then
> Active or it does not matter?
> Is it any problems installing a hotfix? What is about lock pages in
> memory?
> And running AWE enabling on Passive first also?
>
> Geoff , how much memory to give to SQL SERVER if small application is
> using about 50MB AND SQL SERVER 2.7gb?
> Thanks
>
>|||Thank you Geoff N. Hiten
Yes , we are using SQL Server 2000(SP4).
Please take alook at the follwing list and tell me whether it looks good to
you.
a) SQL node1 --(Active) has 8GB
b) SQL node1 --(Passive) has 8GB
1) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL1 node
(Active)
2) Install hotfix from(http://support.microsoft.com/kb/899761) on SQL2 node
(Passive)
3) Grant 'lock pages in memory' on on SQL1 node (Active)
4) Grant 'lock pages in memory' on on SQL1 node (Passive)
5) Enabling AWE on SQL1 node (Active)--set to 6GB
6) Enabling AWE on SQL1 node (Passive)--set to 6GB
Thanks you again
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OZ4pcewkHHA.4904@.TK2MSFTNGP05.phx.gbl...
> Alex,
> There is no SQL 2004. I am guessing since you mention SP4, that is SQL
> 2000, since SQL 2005 is only at SP2 for now.
> Hotfixes install to all nodes on a cluster for a particular instance. You
> need to start the install from the node that is currently hosting the
> instance. You must grant lock pages in memory to the SQL service account
> in order to get AWE to work. AWE is a setting for the SQL instance, so it
> will take effect whichever node hosts that instance.
> For an 8GB system, I would start by setting SQL at 6GB and see how free
> memory looks. You may be able to inch it up a bit, but it is better to
> leave a little extra free memory than to run out. The only down side is
> with SQL 2000 you have to stop and restart the service to enact an AWE
> memory change.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Alex" <test@.hotmail.com> wrote in message
> news:ehk91SwkHHA.4248@.TK2MSFTNGP06.phx.gbl...
>

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
>

Saturday, February 25, 2012

AWE and Max Server Memory (MB)

What purpose does Max Server Memory (MB) serve, if I have 8 GB of RAM:
1. I have the switch properly set in the boot.ini
2. AWE Enabled is set to 1
3. Max Server Memory (MB) set to 2147483647
In other words, if I want to reserve 2 GB for my OS, then would not the Max
Server Memory (MB) set to 2147483647 allow SQL Server to use 6 GB?
Message posted via http://www.droptable.comYou want to set the max server memory to 6 GB = 6 * 1,204 MB = 7,224 MB.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:65e80daa1f3f8@.uwe...
What purpose does Max Server Memory (MB) serve, if I have 8 GB of RAM:
1. I have the switch properly set in the boot.ini
2. AWE Enabled is set to 1
3. Max Server Memory (MB) set to 2147483647
In other words, if I want to reserve 2 GB for my OS, then would not the Max
Server Memory (MB) set to 2147483647 allow SQL Server to use 6 GB?
Message posted via http://www.droptable.com|||You should also see my reply to your original post on this subject.
Andrew J. Kelly SQL MVP
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:65e80daa1f3f8@.uwe...
> What purpose does Max Server Memory (MB) serve, if I have 8 GB of RAM:
> 1. I have the switch properly set in the boot.ini
> 2. AWE Enabled is set to 1
> 3. Max Server Memory (MB) set to 2147483647
> In other words, if I want to reserve 2 GB for my OS, then would not the
> Max
> Server Memory (MB) set to 2147483647 allow SQL Server to use 6 GB?
> --
> Message posted via http://www.droptable.com
>

AWE and Max Server Memory (MB)

What purpose does Max Server Memory (MB) serve, if I have 8 GB of RAM:
1. I have the switch properly set in the boot.ini
2. AWE Enabled is set to 1
3. Max Server Memory (MB) set to 2147483647
In other words, if I want to reserve 2 GB for my OS, then would not the Max
Server Memory (MB) set to 2147483647 allow SQL Server to use 6 GB?
--
Message posted via http://www.sqlmonster.comYou want to set the max server memory to 6 GB = 6 * 1,204 MB = 7,224 MB.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:65e80daa1f3f8@.uwe...
What purpose does Max Server Memory (MB) serve, if I have 8 GB of RAM:
1. I have the switch properly set in the boot.ini
2. AWE Enabled is set to 1
3. Max Server Memory (MB) set to 2147483647
In other words, if I want to reserve 2 GB for my OS, then would not the Max
Server Memory (MB) set to 2147483647 allow SQL Server to use 6 GB?
--
Message posted via http://www.sqlmonster.com|||You should also see my reply to your original post on this subject.
--
Andrew J. Kelly SQL MVP
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:65e80daa1f3f8@.uwe...
> What purpose does Max Server Memory (MB) serve, if I have 8 GB of RAM:
> 1. I have the switch properly set in the boot.ini
> 2. AWE Enabled is set to 1
> 3. Max Server Memory (MB) set to 2147483647
> In other words, if I want to reserve 2 GB for my OS, then would not the
> Max
> Server Memory (MB) set to 2147483647 allow SQL Server to use 6 GB?
> --
> Message posted via http://www.sqlmonster.com
>

AWE + PAE + 3GB cause system to freeze?

Hi,
I have a server with 8Gb of memory
so the /3Gb and /PAE switches are in the boot.ini.
I'm using Win 2003 Ent. & SQL 2000 ent.
at regular basis, my system freeze for some seconds if the AWE option is on.
any idea of what's appends?
My server also host Analysis Services + IIS + Sharepoint + Reporting
Services.
thanks.
Jerome."Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:ecI4P2S0FHA.3000@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I have a server with 8Gb of memory
> so the /3Gb and /PAE switches are in the boot.ini.
> I'm using Win 2003 Ent. & SQL 2000 ent.
> at regular basis, my system freeze for some seconds if the AWE option is
> on.
> any idea of what's appends?
> My server also host Analysis Services + IIS + Sharepoint + Reporting
> Services.
>
It's not generally recommended to use AWE if the server is not dedicated to
SQL Server. Leave the /3GB switch, but get rid of /PAE and AWE. Give 3GB
to SQL Server and leave 2G for Analysis Services, and 2G for IIS, Sharepoint
and Reporting.
David|||in this configuration, only 4Gb is used by the applications
AS consumme 200mb, 200mb for sharepoint & RS
SQL use 2.7 Gb
So I have a lot of free memory.
But also... for the moment I'm in dev mode, and only SQL Server is used, so
the other applications don't use any ressources and are in standby.
I'm just using DTS to load data in my databases.
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:uFjaGMT0FHA.1028@.TK2MSFTNGP12.phx.gbl...
> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
> news:ecI4P2S0FHA.3000@.TK2MSFTNGP12.phx.gbl...
>> Hi,
>> I have a server with 8Gb of memory
>> so the /3Gb and /PAE switches are in the boot.ini.
>> I'm using Win 2003 Ent. & SQL 2000 ent.
>> at regular basis, my system freeze for some seconds if the AWE option is
>> on.
>> any idea of what's appends?
>> My server also host Analysis Services + IIS + Sharepoint + Reporting
>> Services.
> It's not generally recommended to use AWE if the server is not dedicated
> to SQL Server. Leave the /3GB switch, but get rid of /PAE and AWE. Give
> 3GB to SQL Server and leave 2G for Analysis Services, and 2G for IIS,
> Sharepoint and Reporting.
> David
>

AWE + 8GB

I have the \PAE switch in the boot.ini file. Do I also need the \3GB ? What
is that used for ? If i dont use it, can i still enable AWE ?
I have 8GB of RAM and also enabled AWE option. Just wondering what the \3GB
switch does in addition to \PAE/PAE is an OS switch needed if you want any application to have access to
memory beyond 4GB.
Normally, applications cannot address or use any memory beyond 2GB. However,
if you have /PAE on in the OS, you can configure AWE in SQL Server so that
SQL Server, as an application, can access memory above 2 GB. It access that
memory sort of like a page fault, using some memory as a map, to be able to
access the memory in the higher range.
/3GB is an OS flag that allows any app to ADDRESS memory up to 3GB. That
means that if you have both /3GB and AWE in SQL Server, the memory in the
203GB range can be directly accessed, rather than going through the AWE
maps. Direct access is always faster than mapped addressing.
So to summarize the two OS flags:
/PAE allows an app within the OS to use memory beyond 4GB
/3GB allows an app to directly address memory in the 2-3GB range
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:#L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
What
> is that used for ? If i dont use it, can i still enable AWE ?
> I have 8GB of RAM and also enabled AWE option. Just wondering what the
\3GB
> switch does in addition to \PAE
>|||So its best advisable then even though we may set a max limit to say 5 or
6GB on an 8GB RAM box to use both switches right ?
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:%2376kiKokDHA.2732@.TK2MSFTNGP11.phx.gbl...
> /PAE is an OS switch needed if you want any application to have access to
> memory beyond 4GB.
> Normally, applications cannot address or use any memory beyond 2GB.
However,
> if you have /PAE on in the OS, you can configure AWE in SQL Server so
that
> SQL Server, as an application, can access memory above 2 GB. It access
that
> memory sort of like a page fault, using some memory as a map, to be able
to
> access the memory in the higher range.
> /3GB is an OS flag that allows any app to ADDRESS memory up to 3GB. That
> means that if you have both /3GB and AWE in SQL Server, the memory in the
> 203GB range can be directly accessed, rather than going through the AWE
> maps. Direct access is always faster than mapped addressing.
> So to summarize the two OS flags:
> /PAE allows an app within the OS to use memory beyond 4GB
> /3GB allows an app to directly address memory in the 2-3GB range
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:#L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> > I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
> What
> > is that used for ? If i dont use it, can i still enable AWE ?
> > I have 8GB of RAM and also enabled AWE option. Just wondering what the
> \3GB
> > switch does in addition to \PAE
> >
> >
>|||Yes, up to 16 GB you should use both. After 16, the memory maps that AWE
needs take so much space and must be directly accessible, so if you use /3GB
and only leave 1 GB for the OS and the AWE maps, it is not enough. So after
16GB, you should not use AWE and /3GB both.
--
HTH
--
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OXA4IdokDHA.1948@.TK2MSFTNGP12.phx.gbl...
> So its best advisable then even though we may set a max limit to say 5 or
> 6GB on an 8GB RAM box to use both switches right ?
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:%2376kiKokDHA.2732@.TK2MSFTNGP11.phx.gbl...
> > /PAE is an OS switch needed if you want any application to have access
to
> > memory beyond 4GB.
> > Normally, applications cannot address or use any memory beyond 2GB.
> However,
> > if you have /PAE on in the OS, you can configure AWE in SQL Server so
> that
> > SQL Server, as an application, can access memory above 2 GB. It access
> that
> > memory sort of like a page fault, using some memory as a map, to be able
> to
> > access the memory in the higher range.
> >
> > /3GB is an OS flag that allows any app to ADDRESS memory up to 3GB. That
> > means that if you have both /3GB and AWE in SQL Server, the memory in
the
> > 203GB range can be directly accessed, rather than going through the AWE
> > maps. Direct access is always faster than mapped addressing.
> >
> > So to summarize the two OS flags:
> > /PAE allows an app within the OS to use memory beyond 4GB
> > /3GB allows an app to directly address memory in the 2-3GB range
> >
> > --
> > HTH
> > --
> > Kalen Delaney
> > SQL Server MVP
> > www.SolidQualityLearning.com
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:#L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> > > I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
> > What
> > > is that used for ? If i dont use it, can i still enable AWE ?
> > > I have 8GB of RAM and also enabled AWE option. Just wondering what the
> > \3GB
> > > switch does in addition to \PAE
> > >
> > >
> >
> >
>|||"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
What
> is that used for ? If i dont use it, can i still enable AWE ?
> I have 8GB of RAM and also enabled AWE option. Just wondering what the
\3GB
> switch does in addition to \PAE
Just to add to what has already been said, be careful of AWE because it does
not always provide benefit. The additional level of indirection has some
overhead: I ran a large number of benchmarks a couple of years ago on a 16Gb
32 way machine and we found that every test process of our application ran
slightly _slower_ with AWE switched on!
If your application is using AWE as cache, demanding Gb of data to be
present in RAM for it to run at an acceptable speed, it is likely that you
have an inefficient application. In this case, tweaking the app will provide
you orders of magnitude better performance than throwing hardware at the
problem.
Of course, this is assuming you live in a perfect world...
On the other hand you may be using a single SQL Server instance to host many
SQL Server applications on different databases, in which case I can see that
AWE may provide some benefit in that case. In this case, however, it may
well be that you have partitioned the applications onto separate SQL Server
instances instead.
AWE gives me palpitations from the old x86 DOS days with the 640k/1Mb memory
barrier, paging LIM/EMS banks, upper memory and extended memory. I had a
little cottage industry crafting config.sys and autoexec.bat to make
combinations of apps work together without having to reboot or crash. Ahhh
those were the days.
Kind Regards, Howard|||I want to use AWE cos we have 8GB of RAM sitting on the box and do not wish
to see it go waste . The folks always say to throw as much memory as you can
and were just doing that ...How can we determine if our AWE is using cache
as you mentioned and that we might need to tweak the app bcos of the same ?
"Howard Long" <howard@.howardlongxxx.com> wrote in message
news:bmj3ap$df8$1@.sparta.btinternet.com...
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23L1K98nkDHA.688@.TK2MSFTNGP10.phx.gbl...
> > I have the \PAE switch in the boot.ini file. Do I also need the \3GB ?
> What
> > is that used for ? If i dont use it, can i still enable AWE ?
> > I have 8GB of RAM and also enabled AWE option. Just wondering what the
> \3GB
> > switch does in addition to \PAE
> Just to add to what has already been said, be careful of AWE because it
does
> not always provide benefit. The additional level of indirection has some
> overhead: I ran a large number of benchmarks a couple of years ago on a
16Gb
> 32 way machine and we found that every test process of our application ran
> slightly _slower_ with AWE switched on!
> If your application is using AWE as cache, demanding Gb of data to be
> present in RAM for it to run at an acceptable speed, it is likely that you
> have an inefficient application. In this case, tweaking the app will
provide
> you orders of magnitude better performance than throwing hardware at the
> problem.
> Of course, this is assuming you live in a perfect world...
> On the other hand you may be using a single SQL Server instance to host
many
> SQL Server applications on different databases, in which case I can see
that
> AWE may provide some benefit in that case. In this case, however, it may
> well be that you have partitioned the applications onto separate SQL
Server
> instances instead.
> AWE gives me palpitations from the old x86 DOS days with the 640k/1Mb
memory
> barrier, paging LIM/EMS banks, upper memory and extended memory. I had a
> little cottage industry crafting config.sys and autoexec.bat to make
> combinations of apps work together without having to reboot or crash. Ahhh
> those were the days.
> Kind Regards, Howard
>

AWE

Hi,
Imagine that my server has 4GB physical memory. I have added /3GB switch to boot.ini.
Should I enable AWE configuration for my SQL Server to use 3 GB address space? Or AWE must only be used when I have more than 4GB memory?
Thanks in advance
Hello,
AWE can be used only if you have more than 4 GB physical memory. But The
/3GB switch is used to tell SQL Server to take advantage of 3GB out of the
base 4GB
of RAM that Windows OS supports natively. If you don't specify this option,
then SQL Server will only take advantage of 2GB of the first 4GB of RAM in
the
server, essentially wasting 1GB of RAM
Please post the OS and SQL Server edition. This is because For SQL Server
2005 - 64 bit running in Windows 2003 you donot want any changes in BOOT.INI
to use the additional RAM.
Thanks
Hari
"Leila" <Leilas@.hotpop.com> wrote in message
news:OEze$NnfHHA.2432@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Imagine that my server has 4GB physical memory. I have added /3GB switch
> to boot.ini.
> Should I enable AWE configuration for my SQL Server to use 3 GB address
> space? Or AWE must only be used when I have more than 4GB memory?
> Thanks in advance,
> Leila
>
|||> AWE can be used only if you have more than 4 GB physical memory.
That's not correct. Take a look at some empirical data at
http://sqlblog.com/blogs/linchi_shea/default.aspx?p=2
Linchi
"Hari Prasad" wrote:

> Hello,
> AWE can be used only if you have more than 4 GB physical memory. But The
> /3GB switch is used to tell SQL Server to take advantage of 3GB out of the
> base 4GB
> of RAM that Windows OS supports natively. If you don't specify this option,
> then SQL Server will only take advantage of 2GB of the first 4GB of RAM in
> the
> server, essentially wasting 1GB of RAM
> Please post the OS and SQL Server edition. This is because For SQL Server
> 2005 - 64 bit running in Windows 2003 you donot want any changes in BOOT.INI
> to use the additional RAM.
> Thanks
> Hari
>
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:OEze$NnfHHA.2432@.TK2MSFTNGP03.phx.gbl...
>
>
|||Hello Linchi,
If I remember correct for a server with 4 GB RAM running in SQL Server 2005
32 bit and Windows 2003 Advanced, all I did is just /3GB switch in Boot.ini
to
use 3 GB RAM. I will take a look into the server on Moday and keep you
posted
Thanks
Hari
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:45A920F2-86E6-4A86-A1B1-8306C3077E8B@.microsoft.com...[vbcol=seagreen]
> That's not correct. Take a look at some empirical data at
> http://sqlblog.com/blogs/linchi_shea/default.aspx?p=2
> Linchi
> "Hari Prasad" wrote:
|||Hari;
My comment had nothing to do with whether /3GB is used, how it should be
used, or what impact it may have. I was commenting on the statement that AWE
can be used only if you have more than 4GB physical memory. As the data at
the link indicate that setting AWE has an impact on SQL Server memory
consumption even with 4GB physical memory. And if you want your bpool to
consume a certain amount of memory under 4GB, you may need to use AWE to
accomplish that.
Now, whether or not you should use AWE with less than 4GB of physical memory
or whether there is any compelling rason for doing so are entirely different
issue.
Linchi
"Hari Prasad" wrote:

> Hello Linchi,
> If I remember correct for a server with 4 GB RAM running in SQL Server 2005
> 32 bit and Windows 2003 Advanced, all I did is just /3GB switch in Boot.ini
> to
> use 3 GB RAM. I will take a look into the server on Moday and keep you
> posted
> Thanks
> Hari
>
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:45A920F2-86E6-4A86-A1B1-8306C3077E8B@.microsoft.com...
>
>
|||Thanks Hari and Linchi!
Based on documents that I have read, /3GB causes that kernel mode use only
1GB and Virtual Address Space for applications therefore can reserve up to
3GB. Whereas 32-bit based Windows can address up to 4GB of memory, therefore
I think by using /3GB switch we don't need to enable AWE for SQL Server to
use 3GB. Because we are not beyond the 4GB limit of addressing in this
situation.
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:F6FB03D7-3B0F-4CD1-B2A2-BBFD660502EE@.microsoft.com...[vbcol=seagreen]
> Hari;
> My comment had nothing to do with whether /3GB is used, how it should be
> used, or what impact it may have. I was commenting on the statement that
> AWE
> can be used only if you have more than 4GB physical memory. As the data at
> the link indicate that setting AWE has an impact on SQL Server memory
> consumption even with 4GB physical memory. And if you want your bpool to
> consume a certain amount of memory under 4GB, you may need to use AWE to
> accomplish that.
> Now, whether or not you should use AWE with less than 4GB of physical
> memory
> or whether there is any compelling rason for doing so are entirely
> different
> issue.
> Linchi
> "Hari Prasad" wrote:
|||That is correct and the most recommended approach with 4GB.
Andrew J. Kelly SQL MVP
"Leila" <Leilas@.hotpop.com> wrote in message
news:ucNNgjyfHHA.2640@.TK2MSFTNGP06.phx.gbl...
> Thanks Hari and Linchi!
> Based on documents that I have read, /3GB causes that kernel mode use only
> 1GB and Virtual Address Space for applications therefore can reserve up to
> 3GB. Whereas 32-bit based Windows can address up to 4GB of memory,
> therefore I think by using /3GB switch we don't need to enable AWE for SQL
> Server to use 3GB. Because we are not beyond the 4GB limit of addressing
> in this situation.
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
> news:F6FB03D7-3B0F-4CD1-B2A2-BBFD660502EE@.microsoft.com...
>
|||Thanks indeed Andrew :-)
Now these two conditions:
1) 5GB RAM + /PAE switch + /3GB switch
2) 6GB RAM + /PAE switch
Can I say that neither of these situations need AWE for SQL Server?
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uW%23DbP3fHHA.4936@.TK2MSFTNGP04.phx.gbl...
> That is correct and the most recommended approach with 4GB.
> --
> Andrew J. Kelly SQL MVP
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:ucNNgjyfHHA.2640@.TK2MSFTNGP06.phx.gbl...
>
|||Depends on how much you want for SQL Server. If you want more than 3GB you
must use AWE (in addition to PAE) on 32 bit systems. In either case you
should always leave at least a GB for the OS when using AWE since it is not
dynamic. 2GB if going over 12GB total. The /3GB is optional depending on
how much you need for non-buffer pool memory such as procedure cache,
connections etc.
Andrew J. Kelly SQL MVP
"Leila" <Leilas@.hotpop.com> wrote in message
news:%2399LSA4fHHA.2396@.TK2MSFTNGP04.phx.gbl...
> Thanks indeed Andrew :-)
> Now these two conditions:
> 1) 5GB RAM + /PAE switch + /3GB switch
> 2) 6GB RAM + /PAE switch
> Can I say that neither of these situations need AWE for SQL Server?
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uW%23DbP3fHHA.4936@.TK2MSFTNGP04.phx.gbl...
>
|||If I have 5GB memory and I use both /PAE and /3GB, then SQL Server can use
up to 4GB memory and this is not beyond 32-bit addressing. Why should I
enable AWE for SQL Server?
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:utisfW8fHHA.668@.TK2MSFTNGP05.phx.gbl...
> Depends on how much you want for SQL Server. If you want more than 3GB you
> must use AWE (in addition to PAE) on 32 bit systems. In either case you
> should always leave at least a GB for the OS when using AWE since it is
> not dynamic. 2GB if going over 12GB total. The /3GB is optional depending
> on how much you need for non-buffer pool memory such as procedure cache,
> connections etc.
> --
> Andrew J. Kelly SQL MVP
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%2399LSA4fHHA.2396@.TK2MSFTNGP04.phx.gbl...
>

Sunday, March 11, 2012

AWE, /3gb and /pae stuff

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 question (Geoff N. Hiten)

AWE question (Geoff N. Hiten)

AWE question (Geoff N. Hiten)

AWE on Windows 64 Bit

AWE on Windows 64 Bit

AWE on Windows 64 Bit

AWE on SQL 2005 and W 2003 Enterprise Server

Saturday, February 25, 2012

AWE and Max Server Memory (MB)

AWE and Max Server Memory (MB)

AWE + PAE + 3GB cause system to freeze?

AWE + 8GB

AWE

Autonumber field

Blog Archive

About Me