We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editions/64bit/sql64bitadvantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3 GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Server to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegr oups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editions/64bit/sql64bitadvantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
Showing posts with label 8gb. Show all posts
Showing posts with label 8gb. Show all posts
Sunday, March 11, 2012
AWE? / Windows 2003 R2 x64 / SQL Server 2000 x86 / 8GB RAM
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly learned that SQL 2000 x64 can only be installed on 64-bit Intel Itanium (IA64) servers, so were forced to install the 32bit x86 version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no longer need to set the /3GB and /PAE switches because all of the memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx AWE is a set of memory management extensions to the Microsoft Win32 API that allows applications to address memory beyond the 4GB limitation. Using AWE, applications can acquire physical memory as nonpaged memory, and then dynamically map views of the nonpaged memory to the 32-bit address space.32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3
GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Se
rver to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegroups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no longer need to set the /3GB and /PAE switches because all of the memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx AWE is a set of memory management extensions to the Microsoft Win32 API that allows applications to address memory beyond the 4GB limitation. Using AWE, applications can acquire physical memory as nonpaged memory, and then dynamically map views of the nonpaged memory to the 32-bit address space.32 it SQL Server is 32 bit. In order of a 32 bit app to see more than 2 or 3
GB memory, it need to
use the AWE extensions. So, yes, you need to sp_configure your 32 bit SQL Se
rver to use AWE.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<mikemiller.innova@.gmail.com> wrote in message
news:1176395603.695552.226090@.b75g2000hsg.googlegroups.com...
We had to install SQL 2000 on a 64-bit Intel x64 server. We quickly
learned that SQL 2000 x64 can only be installed on 64-bit Intel
Itanium (IA64) servers, so were forced to install the 32bit x86
version.
When running a 64-bit version of Windows 2003 with 8gb of RAM, we no
longer need to set the /3GB and /PAE switches because all of the
memory is addressable on the 64-bit platform.
Now that we are running 32-bit SQL Server 2000 Enterprise x86 on 64bit
Windows 2003 R2 Enterprise x64, do we need to enable AWE in SQL Server
like we had to on 32-bit Windows?
Here's how we did it on 32bit SQL:
http://www.sql-server-performance.com/awe_memory.asp
It appears that AWE is only required/supported on 32-bit OS:
http://www.microsoft.com/sql/editio...advantages.mspx
AWE is a set of memory management extensions to the Microsoft Win32?
API that allows applications to address memory beyond the 4GB
limitation. Using AWE, applications can acquire physical memory as
nonpaged memory, and then dynamically map views of the nonpaged memory
to the 32-bit address space.
AWE SQL Performance Problem
We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB R
AM. The setting seems to have made the difference in RAM usage, but we are e
xperiencing extremely high CPU utilization and overall the system does not s
eem to be any faster. If an
ything, it seems to have slowed down some. There are a lot of variables, but
I was wondering of anyone has had adverse effects with the AWE setting.From BOL.
<<
To enable AWE, set awe enabled to 1. SQL Server will reserve almost all
available memory, leaving 128 megabytes (MB) or less, unless a value has
been specified for max server memory.
What is your max memory setting? Leaving 128M for the OS probably isn't a
good idea.
BTW... Profiler may be helpful in understanding the CPU usage.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||We had some CPU spin and server instability issues that were instantaneously
and permenantly solved by turning off the /3GB switch and reducing max
server mem to 1.5GB less than physical. PSS said there was potential kernel
memory starvation with /3GB and max server memory set to near physical. Not
sure if this applies to your scenario.
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||Hi Phil,
I am viewing your post and since we have not heard from you for some time
and I wonder how things go on your side. To disable the AWE to check if the
performance issue is related to the AWE is the method to narrow down
performance problems to AWE. Also, you could refer to the link of the
followings for reference:
How To Gather Information for Effective Troubleshooting of Performance
Issues
http://support.microsoft.com/defaul...microsoft.com:
80/support/kb/articles/Q175/6/58.ASP&NoWebContent=1
http://support.microsoft.com/defaul...kb;en-us;298475
Also, if the case is critical and it should be troubleshot by some advanced
tools which are not supported in the newsgroup. Therefore, we probably will
not be able to resolve the issue through the newsgroups. I'd recommend
opening a Support incident with Microsoft Support Services, so that a
dedicated Support Professional can assist with your advisory case. Please
be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thanks.
Hope this helps.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
AM. The setting seems to have made the difference in RAM usage, but we are e
xperiencing extremely high CPU utilization and overall the system does not s
eem to be any faster. If an
ything, it seems to have slowed down some. There are a lot of variables, but
I was wondering of anyone has had adverse effects with the AWE setting.From BOL.
<<
To enable AWE, set awe enabled to 1. SQL Server will reserve almost all
available memory, leaving 128 megabytes (MB) or less, unless a value has
been specified for max server memory.
What is your max memory setting? Leaving 128M for the OS probably isn't a
good idea.
BTW... Profiler may be helpful in understanding the CPU usage.
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||We had some CPU spin and server instability issues that were instantaneously
and permenantly solved by turning off the /3GB switch and reducing max
server mem to 1.5GB less than physical. PSS said there was potential kernel
memory starvation with /3GB and max server memory set to near physical. Not
sure if this applies to your scenario.
"Phil Appel" <phil@.chileinc.com> wrote in message
news:774F1405-0770-4A4F-B551-9CC330AE9CE4@.microsoft.com...
> We recently enabled AWE on a SQL Server cluster. Each box has 8CPU and 8GB
RAM. The setting seems to have made the difference in RAM usage, but we are
experiencing extremely high CPU utilization and overall the system does not
seem to be any faster. If anything, it seems to have slowed down some. There
are a lot of variables, but I was wondering of anyone has had adverse
effects with the AWE setting.|||Hi Phil,
I am viewing your post and since we have not heard from you for some time
and I wonder how things go on your side. To disable the AWE to check if the
performance issue is related to the AWE is the method to narrow down
performance problems to AWE. Also, you could refer to the link of the
followings for reference:
How To Gather Information for Effective Troubleshooting of Performance
Issues
http://support.microsoft.com/defaul...microsoft.com:
80/support/kb/articles/Q175/6/58.ASP&NoWebContent=1
http://support.microsoft.com/defaul...kb;en-us;298475
Also, if the case is critical and it should be troubleshot by some advanced
tools which are not supported in the newsgroup. Therefore, we probably will
not be able to resolve the issue through the newsgroups. I'd recommend
opening a Support incident with Microsoft Support Services, so that a
dedicated Support Professional can assist with your advisory case. Please
be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/defaul...US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thanks.
Hope this helps.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
Thursday, March 8, 2012
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
________________________________________
__________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
________________________________________
___________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
________________________________________
___________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> ________________________________________
__________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ________________________________________
___________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ________________________________________
___________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/d...-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
________________________________________
__________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
________________________________________
___________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
________________________________________
___________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> ________________________________________
__________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition
(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINN
T="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ________________________________________
___________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ________________________________________
___________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/d...-us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/d...-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________ ________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________ _________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________ _________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________ ________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________ _________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________ _________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/de...us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/de...us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
with SP3. The boot.ini is set with /3gb /PAE. The server
system properties list 8GB of RAM. Within SQL Server
sp_configure AWE running is set to 1. SQL Server Memory
properties the Maximum is set to 5.12 GB. But SQL Server
does not recognize AWE setting. I look in the SQL Server
errorlog after the server was rebooted and did not list
AWE memory settings. The Server Performance Monitor
Counter under SQL Server Memory Manager with Target Server
Memory list 2.7GB. This should be 5.12 GB of memory for
SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________ ________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________ _________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________ _________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________ ________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________ _________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________ _________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
Hi Mike,
Check that the SQL Server startup account has the Lock Pages in Memory
privilege:
http://msdn.microsoft.com/library/de...us/adminsql/ad
_1_server_1fnd.asp
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||I already suggested that...
Andrew J. Kelly SQL MVP
"Eric Crdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/de...us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Crdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition with SP3.
The boot.ini is set with /3gb /PAE. The server system properties list 8GB of RAM. Within SQL Server sp_configure AWE running is set to 1. SQL Server Memory properties the Maximum is set to 5.12 GB. But SQL Server does not recognize AWE setting.
I look in the SQL Server errorlog after the server was rebooted and did not list AWE memory settings.
The Server Performance Monitor Counter under SQL Server Memory Manager with Target Server Memory list 2.7GB.
This should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
___________________________________________________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
___________________________________________________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ___________________________________________________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ___________________________________________________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the ?Lock Pages in Memory?
privilege:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_server_1fnd.asp
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
--
Andrew J. Kelly SQL MVP
"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> > I have a server with SQL Server 2000 Enterprise Edition
> > with SP3. The boot.ini is set with /3gb /PAE. The server
> > system properties list 8GB of RAM. Within SQL Server
> > sp_configure AWE running is set to 1. SQL Server Memory
> > properties the Maximum is set to 5.12 GB. But SQL Server
> > does not recognize AWE setting. I look in the SQL Server
> > errorlog after the server was rebooted and did not list
> > AWE memory settings. The Server Performance Monitor
> > Counter under SQL Server Memory Manager with Target Server
> > Memory list 2.7GB. This should be 5.12 GB of memory for
> > SQL Server.
> >
> > Please help me resolve this problem.
> >
> > Mike
> >
> > __________________________________________________________
> > [boot loader]
> > timeout=10
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> > Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> > ___________________________________________________________
> > sp_configure "show advanced options", 1
> > RECONFIGURE
> > GO
> > sp_configure "awe enabled", 1
> > RECONFIGURE
> > GO
> > sp_configure "max server memory", 5120
> > RECONFIGURE
> > GO
> > sp_configure "min server memory", 0
> > RECONFIGURE
> > GO
> > ___________________________________________________________
> > Output from SP_CONFIGURE
> > name minimum
> > maximum config_value run_value
> > -- -- --
> > -- --
> > affinity mask -2147483648
> > 2147483647 0 0
> > allow updates 0
> > 1 0 0
> > awe enabled 0
> > 1 1 1
> > c2 audit mode 0
> > 1 0 0
> > cost threshold for parallelism 0
> > 32767 5 5
> > Cross DB Ownership Chaining 0
> > 1 0 0
> > cursor threshold -1
> > 2147483647 -1 -1
> > default full-text language 0
> > 2147483647 1033 1033
> > default language 0
> > 9999 0 0
> > fill factor (%) 0
> > 100 0 0
> > index create memory (KB) 704
> > 2147483647 0 0
> > lightweight pooling 0
> > 1 0 0
> > locks 5000
> > 2147483647 0 0
> > max degree of parallelism 0
> > 32 0 0
> > max server memory (MB) 4
> > 2147483647 5120 5120
> > max text repl size (B) 0
> > 2147483647 65536 65536
> > max worker threads 32
> > 32767 255 255
> > media retention 0
> > 365 0 0
> > min memory per query (KB) 512
> > 2147483647 1024 1024
> > min server memory (MB) 0
> > 2147483647 0 0
> > nested triggers 0
> > 1 1 1
> > network packet size (B) 512
> > 65536 4096 4096
> > open objects 0
> > 2147483647 0 0
> > priority boost 0
> > 1 0 0
> > query governor cost limit 0
> > 2147483647 0 0
> > query wait (s) -1
> > 2147483647 -1 -1
> > recovery interval (min) 0
> > 32767 0 0
> > remote access 0
> > 1 1 1
> > remote login timeout (s) 0
> > 2147483647 20 20
> > remote proc trans 0
> > 1 0 0
> > remote query timeout (s) 0
> > 2147483647 600 600
> > scan for startup procs 0
> > 1 1 0
> > set working set size 0
> > 1 0 0
> > show advanced options 0
> > 1 1 1
> > two digit year cutoff 1753
> > 9999 2049 2049
> > user connections 0
> > 32767 0 0
> > user options 0
> > 32767 56 56
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
The boot.ini is set with /3gb /PAE. The server system properties list 8GB of RAM. Within SQL Server sp_configure AWE running is set to 1. SQL Server Memory properties the Maximum is set to 5.12 GB. But SQL Server does not recognize AWE setting.
I look in the SQL Server errorlog after the server was rebooted and did not list AWE memory settings.
The Server Performance Monitor Counter under SQL Server Memory Manager with Target Server Memory list 2.7GB.
This should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
___________________________________________________________
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
___________________________________________________________
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The server
> system properties list 8GB of RAM. Within SQL Server
> sp_configure AWE running is set to 1. SQL Server Memory
> properties the Maximum is set to 5.12 GB. But SQL Server
> does not recognize AWE setting. I look in the SQL Server
> errorlog after the server was rebooted and did not list
> AWE memory settings. The Server Performance Monitor
> Counter under SQL Server Memory Manager with Target Server
> Memory list 2.7GB. This should be 5.12 GB of memory for
> SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> ___________________________________________________________
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> ___________________________________________________________
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
--
Hi Mike,
Check that the SQL Server startup account has the ?Lock Pages in Memory?
privilege:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
_1_server_1fnd.asp
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||I already suggested that...
--
Andrew J. Kelly SQL MVP
"Eric Cárdenas [MSFT]" <ecardena@.online.microsoft.com> wrote in message
news:dAsRybjNEHA.308@.cpmsftngxa10.phx.gbl...
> > I have a server with SQL Server 2000 Enterprise Edition
> > with SP3. The boot.ini is set with /3gb /PAE. The server
> > system properties list 8GB of RAM. Within SQL Server
> > sp_configure AWE running is set to 1. SQL Server Memory
> > properties the Maximum is set to 5.12 GB. But SQL Server
> > does not recognize AWE setting. I look in the SQL Server
> > errorlog after the server was rebooted and did not list
> > AWE memory settings. The Server Performance Monitor
> > Counter under SQL Server Memory Manager with Target Server
> > Memory list 2.7GB. This should be 5.12 GB of memory for
> > SQL Server.
> >
> > Please help me resolve this problem.
> >
> > Mike
> >
> > __________________________________________________________
> > [boot loader]
> > timeout=10
> > default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> > [operating systems]
> > multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> > Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> > ___________________________________________________________
> > sp_configure "show advanced options", 1
> > RECONFIGURE
> > GO
> > sp_configure "awe enabled", 1
> > RECONFIGURE
> > GO
> > sp_configure "max server memory", 5120
> > RECONFIGURE
> > GO
> > sp_configure "min server memory", 0
> > RECONFIGURE
> > GO
> > ___________________________________________________________
> > Output from SP_CONFIGURE
> > name minimum
> > maximum config_value run_value
> > -- -- --
> > -- --
> > affinity mask -2147483648
> > 2147483647 0 0
> > allow updates 0
> > 1 0 0
> > awe enabled 0
> > 1 1 1
> > c2 audit mode 0
> > 1 0 0
> > cost threshold for parallelism 0
> > 32767 5 5
> > Cross DB Ownership Chaining 0
> > 1 0 0
> > cursor threshold -1
> > 2147483647 -1 -1
> > default full-text language 0
> > 2147483647 1033 1033
> > default language 0
> > 9999 0 0
> > fill factor (%) 0
> > 100 0 0
> > index create memory (KB) 704
> > 2147483647 0 0
> > lightweight pooling 0
> > 1 0 0
> > locks 5000
> > 2147483647 0 0
> > max degree of parallelism 0
> > 32 0 0
> > max server memory (MB) 4
> > 2147483647 5120 5120
> > max text repl size (B) 0
> > 2147483647 65536 65536
> > max worker threads 32
> > 32767 255 255
> > media retention 0
> > 365 0 0
> > min memory per query (KB) 512
> > 2147483647 1024 1024
> > min server memory (MB) 0
> > 2147483647 0 0
> > nested triggers 0
> > 1 1 1
> > network packet size (B) 512
> > 65536 4096 4096
> > open objects 0
> > 2147483647 0 0
> > priority boost 0
> > 1 0 0
> > query governor cost limit 0
> > 2147483647 0 0
> > query wait (s) -1
> > 2147483647 -1 -1
> > recovery interval (min) 0
> > 32767 0 0
> > remote access 0
> > 1 1 1
> > remote login timeout (s) 0
> > 2147483647 20 20
> > remote proc trans 0
> > 1 0 0
> > remote query timeout (s) 0
> > 2147483647 600 600
> > scan for startup procs 0
> > 1 1 0
> > set working set size 0
> > 1 0 0
> > show advanced options 0
> > 1 1 1
> > two digit year cutoff 1753
> > 9999 2049 2049
> > user connections 0
> > 32767 0 0
> > user options 0
> > 32767 56 56
> --
> Hi Mike,
> Check that the SQL Server startup account has the 'Lock Pages in Memory'
> privilege:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad
> _1_server_1fnd.asp
> --
> Eric Cárdenas
> Senior support professional
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
AWE RAM (SQL 2K not recognizing available AWE RAM)
I have a server with SQL Server 2000 Enterprise Edition
with SP3. The boot.ini is set with /3gb /PAE. The
server system properties list 8GB of RAM. Within SQL
Server sp_configure AWE running is set to 1. When I look
in the SQL Server error log it tells me that 8 processors
and 2048 MB RAM where detected. SQL Server Memory
properties are set with the Maximum to 5.12 GB. But SQL
Server does not recognize AWE setting. The Server
Performance Monitor Counter under SQL Server Memory
Manager with Target Server Memory list 2.7GB. This
should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________________
_
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________________
_
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56Do you have Lock Pages In Memory set properly? See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811891&Product=sql2k
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The
> server system properties list 8GB of RAM. Within SQL
> Server sp_configure AWE running is set to 1. When I look
> in the SQL Server error log it tells me that 8 processors
> and 2048 MB RAM where detected. SQL Server Memory
> properties are set with the Maximum to 5.12 GB. But SQL
> Server does not recognize AWE setting. The Server
> Performance Monitor Counter under SQL Server Memory
> Manager with Target Server Memory list 2.7GB. This
> should be 5.12 GB of memory for SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________________
> _
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________________
> _
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
>
>|||The SQL Server service account is listed in the Lock
pages in memory is set the same way three other servers
that work correctly.
Is this server not recognizing this setting?
Please help me with this problem.
Thanks,
Mike
>--Original Message--
>Do you have Lock Pages In Memory set properly? See this:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;811891&Product=sql2k
>--
>Andrew J. Kelly SQL MVP
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
>> I have a server with SQL Server 2000 Enterprise Edition
>> with SP3. The boot.ini is set with /3gb /PAE. The
>> server system properties list 8GB of RAM. Within SQL
>> Server sp_configure AWE running is set to 1. When I
look
>> in the SQL Server error log it tells me that 8
processors
>> and 2048 MB RAM where detected. SQL Server Memory
>> properties are set with the Maximum to 5.12 GB. But
SQL
>> Server does not recognize AWE setting. The Server
>> Performance Monitor Counter under SQL Server Memory
>> Manager with Target Server Memory list 2.7GB. This
>> should be 5.12 GB of memory for SQL Server.
>> Please help me resolve this problem.
>> Mike
>>
__________________________________________________________
>> [boot loader]
>> timeout=10
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
>> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________________
>> _
>> sp_configure "show advanced options", 1
>> RECONFIGURE
>> GO
>> sp_configure "awe enabled", 1
>> RECONFIGURE
>> GO
>> sp_configure "max server memory", 5120
>> RECONFIGURE
>> GO
>> sp_configure "min server memory", 0
>> RECONFIGURE
>> GO
__________________________________________________________
>> _
>> Output from SP_CONFIGURE
>> name minimum
>> maximum config_value run_value
>> -- -- --
--
>> -
>> -- --
>> affinity mask -2147483648
>> 2147483647 0 0
>> allow updates 0
>> 1 0 0
>> awe enabled 0
>> 1 1 1
>> c2 audit mode 0
>> 1 0 0
>> cost threshold for parallelism 0
>> 32767 5 5
>> Cross DB Ownership Chaining 0
>> 1 0 0
>> cursor threshold -1
>> 2147483647 -1 -1
>> default full-text language 0
>> 2147483647 1033 1033
>> default language 0
>> 9999 0 0
>> fill factor (%) 0
>> 100 0 0
>> index create memory (KB) 704
>> 2147483647 0 0
>> lightweight pooling 0
>> 1 0 0
>> locks 5000
>> 2147483647 0 0
>> max degree of parallelism 0
>> 32 0 0
>> max server memory (MB) 4
>> 2147483647 5120 5120
>> max text repl size (B) 0
>> 2147483647 65536 65536
>> max worker threads 32
>> 32767 255 255
>> media retention 0
>> 365 0 0
>> min memory per query (KB) 512
>> 2147483647 1024 1024
>> min server memory (MB) 0
>> 2147483647 0 0
>> nested triggers 0
>> 1 1 1
>> network packet size (B) 512
>> 65536 4096 4096
>> open objects 0
>> 2147483647 0 0
>> priority boost 0
>> 1 0 0
>> query governor cost limit 0
>> 2147483647 0 0
>> query wait (s) -1
>> 2147483647 -1 -1
>> recovery interval (min) 0
>> 32767 0 0
>> remote access 0
>> 1 1 1
>> remote login timeout (s) 0
>> 2147483647 20 20
>> remote proc trans 0
>> 1 0 0
>> remote query timeout (s) 0
>> 2147483647 600 600
>> scan for startup procs 0
>> 1 1 0
>> set working set size 0
>> 1 0 0
>> show advanced options 0
>> 1 1 1
>> two digit year cutoff 1753
>> 9999 2049 2049
>> user connections 0
>> 32767 0 0
>> user options 0
>> 32767 56 56
>>
>>
>
>.
>|||According to the results of sp_configure your run value is still set to 0
for AWE. Did you restart the server? And are you absolutely sure you have
SQL EE? What does xp_msver show?
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a04c01c434f9$3dde5ae0$a401280a@.phx.gbl...
> The SQL Server service account is listed in the Lock
> pages in memory is set the same way three other servers
> that work correctly.
> Is this server not recognizing this setting?
> Please help me with this problem.
> Thanks,
> Mike
>
> >--Original Message--
> >Do you have Lock Pages In Memory set properly? See this:
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;811891&Product=sql2k
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
> >>
> >> I have a server with SQL Server 2000 Enterprise Edition
> >> with SP3. The boot.ini is set with /3gb /PAE. The
> >> server system properties list 8GB of RAM. Within SQL
> >> Server sp_configure AWE running is set to 1. When I
> look
> >> in the SQL Server error log it tells me that 8
> processors
> >> and 2048 MB RAM where detected. SQL Server Memory
> >> properties are set with the Maximum to 5.12 GB. But
> SQL
> >> Server does not recognize AWE setting. The Server
> >> Performance Monitor Counter under SQL Server Memory
> >> Manager with Target Server Memory list 2.7GB. This
> >> should be 5.12 GB of memory for SQL Server.
> >>
> >> Please help me resolve this problem.
> >>
> >> Mike
> >>
> >>
> __________________________________________________________
> >> [boot loader]
> >> timeout=10
> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> >> [operating systems]
> >> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> >> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> >>
> __________________________________________________________
> >> _
> >> sp_configure "show advanced options", 1
> >> RECONFIGURE
> >> GO
> >> sp_configure "awe enabled", 1
> >> RECONFIGURE
> >> GO
> >> sp_configure "max server memory", 5120
> >> RECONFIGURE
> >> GO
> >> sp_configure "min server memory", 0
> >> RECONFIGURE
> >> GO
> >>
> __________________________________________________________
> >> _
> >> Output from SP_CONFIGURE
> >> name minimum
> >> maximum config_value run_value
> >> -- -- --
> --
> >> -
> >> -- --
> >> affinity mask -2147483648
> >> 2147483647 0 0
> >> allow updates 0
> >> 1 0 0
> >> awe enabled 0
> >> 1 1 1
> >> c2 audit mode 0
> >> 1 0 0
> >> cost threshold for parallelism 0
> >> 32767 5 5
> >> Cross DB Ownership Chaining 0
> >> 1 0 0
> >> cursor threshold -1
> >> 2147483647 -1 -1
> >> default full-text language 0
> >> 2147483647 1033 1033
> >> default language 0
> >> 9999 0 0
> >> fill factor (%) 0
> >> 100 0 0
> >> index create memory (KB) 704
> >> 2147483647 0 0
> >> lightweight pooling 0
> >> 1 0 0
> >> locks 5000
> >> 2147483647 0 0
> >> max degree of parallelism 0
> >> 32 0 0
> >> max server memory (MB) 4
> >> 2147483647 5120 5120
> >> max text repl size (B) 0
> >> 2147483647 65536 65536
> >> max worker threads 32
> >> 32767 255 255
> >> media retention 0
> >> 365 0 0
> >> min memory per query (KB) 512
> >> 2147483647 1024 1024
> >> min server memory (MB) 0
> >> 2147483647 0 0
> >> nested triggers 0
> >> 1 1 1
> >> network packet size (B) 512
> >> 65536 4096 4096
> >> open objects 0
> >> 2147483647 0 0
> >> priority boost 0
> >> 1 0 0
> >> query governor cost limit 0
> >> 2147483647 0 0
> >> query wait (s) -1
> >> 2147483647 -1 -1
> >> recovery interval (min) 0
> >> 32767 0 0
> >> remote access 0
> >> 1 1 1
> >> remote login timeout (s) 0
> >> 2147483647 20 20
> >> remote proc trans 0
> >> 1 0 0
> >> remote query timeout (s) 0
> >> 2147483647 600 600
> >> scan for startup procs 0
> >> 1 1 0
> >> set working set size 0
> >> 1 0 0
> >> show advanced options 0
> >> 1 1 1
> >> two digit year cutoff 1753
> >> 9999 2049 2049
> >> user connections 0
> >> 32767 0 0
> >> user options 0
> >> 32767 56 56
> >>
> >>
> >>
> >>
> >
> >
> >.
> >
with SP3. The boot.ini is set with /3gb /PAE. The
server system properties list 8GB of RAM. Within SQL
Server sp_configure AWE running is set to 1. When I look
in the SQL Server error log it tells me that 8 processors
and 2048 MB RAM where detected. SQL Server Memory
properties are set with the Maximum to 5.12 GB. But SQL
Server does not recognize AWE setting. The Server
Performance Monitor Counter under SQL Server Memory
Manager with Target Server Memory list 2.7GB. This
should be 5.12 GB of memory for SQL Server.
Please help me resolve this problem.
Mike
__________________________________________________________
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________________
_
sp_configure "show advanced options", 1
RECONFIGURE
GO
sp_configure "awe enabled", 1
RECONFIGURE
GO
sp_configure "max server memory", 5120
RECONFIGURE
GO
sp_configure "min server memory", 0
RECONFIGURE
GO
__________________________________________________________
_
Output from SP_CONFIGURE
name minimum
maximum config_value run_value
-- -- --
-
-- --
affinity mask -2147483648
2147483647 0 0
allow updates 0
1 0 0
awe enabled 0
1 1 1
c2 audit mode 0
1 0 0
cost threshold for parallelism 0
32767 5 5
Cross DB Ownership Chaining 0
1 0 0
cursor threshold -1
2147483647 -1 -1
default full-text language 0
2147483647 1033 1033
default language 0
9999 0 0
fill factor (%) 0
100 0 0
index create memory (KB) 704
2147483647 0 0
lightweight pooling 0
1 0 0
locks 5000
2147483647 0 0
max degree of parallelism 0
32 0 0
max server memory (MB) 4
2147483647 5120 5120
max text repl size (B) 0
2147483647 65536 65536
max worker threads 32
32767 255 255
media retention 0
365 0 0
min memory per query (KB) 512
2147483647 1024 1024
min server memory (MB) 0
2147483647 0 0
nested triggers 0
1 1 1
network packet size (B) 512
65536 4096 4096
open objects 0
2147483647 0 0
priority boost 0
1 0 0
query governor cost limit 0
2147483647 0 0
query wait (s) -1
2147483647 -1 -1
recovery interval (min) 0
32767 0 0
remote access 0
1 1 1
remote login timeout (s) 0
2147483647 20 20
remote proc trans 0
1 0 0
remote query timeout (s) 0
2147483647 600 600
scan for startup procs 0
1 1 0
set working set size 0
1 0 0
show advanced options 0
1 1 1
two digit year cutoff 1753
9999 2049 2049
user connections 0
32767 0 0
user options 0
32767 56 56Do you have Lock Pages In Memory set properly? See this:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811891&Product=sql2k
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
> I have a server with SQL Server 2000 Enterprise Edition
> with SP3. The boot.ini is set with /3gb /PAE. The
> server system properties list 8GB of RAM. Within SQL
> Server sp_configure AWE running is set to 1. When I look
> in the SQL Server error log it tells me that 8 processors
> and 2048 MB RAM where detected. SQL Server Memory
> properties are set with the Maximum to 5.12 GB. But SQL
> Server does not recognize AWE setting. The Server
> Performance Monitor Counter under SQL Server Memory
> Manager with Target Server Memory list 2.7GB. This
> should be 5.12 GB of memory for SQL Server.
> Please help me resolve this problem.
> Mike
> __________________________________________________________
> [boot loader]
> timeout=10
> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> __________________________________________________________
> _
> sp_configure "show advanced options", 1
> RECONFIGURE
> GO
> sp_configure "awe enabled", 1
> RECONFIGURE
> GO
> sp_configure "max server memory", 5120
> RECONFIGURE
> GO
> sp_configure "min server memory", 0
> RECONFIGURE
> GO
> __________________________________________________________
> _
> Output from SP_CONFIGURE
> name minimum
> maximum config_value run_value
> -- -- --
> -
> -- --
> affinity mask -2147483648
> 2147483647 0 0
> allow updates 0
> 1 0 0
> awe enabled 0
> 1 1 1
> c2 audit mode 0
> 1 0 0
> cost threshold for parallelism 0
> 32767 5 5
> Cross DB Ownership Chaining 0
> 1 0 0
> cursor threshold -1
> 2147483647 -1 -1
> default full-text language 0
> 2147483647 1033 1033
> default language 0
> 9999 0 0
> fill factor (%) 0
> 100 0 0
> index create memory (KB) 704
> 2147483647 0 0
> lightweight pooling 0
> 1 0 0
> locks 5000
> 2147483647 0 0
> max degree of parallelism 0
> 32 0 0
> max server memory (MB) 4
> 2147483647 5120 5120
> max text repl size (B) 0
> 2147483647 65536 65536
> max worker threads 32
> 32767 255 255
> media retention 0
> 365 0 0
> min memory per query (KB) 512
> 2147483647 1024 1024
> min server memory (MB) 0
> 2147483647 0 0
> nested triggers 0
> 1 1 1
> network packet size (B) 512
> 65536 4096 4096
> open objects 0
> 2147483647 0 0
> priority boost 0
> 1 0 0
> query governor cost limit 0
> 2147483647 0 0
> query wait (s) -1
> 2147483647 -1 -1
> recovery interval (min) 0
> 32767 0 0
> remote access 0
> 1 1 1
> remote login timeout (s) 0
> 2147483647 20 20
> remote proc trans 0
> 1 0 0
> remote query timeout (s) 0
> 2147483647 600 600
> scan for startup procs 0
> 1 1 0
> set working set size 0
> 1 0 0
> show advanced options 0
> 1 1 1
> two digit year cutoff 1753
> 9999 2049 2049
> user connections 0
> 32767 0 0
> user options 0
> 32767 56 56
>
>|||The SQL Server service account is listed in the Lock
pages in memory is set the same way three other servers
that work correctly.
Is this server not recognizing this setting?
Please help me with this problem.
Thanks,
Mike
>--Original Message--
>Do you have Lock Pages In Memory set properly? See this:
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;811891&Product=sql2k
>--
>Andrew J. Kelly SQL MVP
>
>"Mike" <anonymous@.discussions.microsoft.com> wrote in
message
>news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
>> I have a server with SQL Server 2000 Enterprise Edition
>> with SP3. The boot.ini is set with /3gb /PAE. The
>> server system properties list 8GB of RAM. Within SQL
>> Server sp_configure AWE running is set to 1. When I
look
>> in the SQL Server error log it tells me that 8
processors
>> and 2048 MB RAM where detected. SQL Server Memory
>> properties are set with the Maximum to 5.12 GB. But
SQL
>> Server does not recognize AWE setting. The Server
>> Performance Monitor Counter under SQL Server Memory
>> Manager with Target Server Memory list 2.7GB. This
>> should be 5.12 GB of memory for SQL Server.
>> Please help me resolve this problem.
>> Mike
>>
__________________________________________________________
>> [boot loader]
>> timeout=10
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
>> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
__________________________________________________________
>> _
>> sp_configure "show advanced options", 1
>> RECONFIGURE
>> GO
>> sp_configure "awe enabled", 1
>> RECONFIGURE
>> GO
>> sp_configure "max server memory", 5120
>> RECONFIGURE
>> GO
>> sp_configure "min server memory", 0
>> RECONFIGURE
>> GO
__________________________________________________________
>> _
>> Output from SP_CONFIGURE
>> name minimum
>> maximum config_value run_value
>> -- -- --
--
>> -
>> -- --
>> affinity mask -2147483648
>> 2147483647 0 0
>> allow updates 0
>> 1 0 0
>> awe enabled 0
>> 1 1 1
>> c2 audit mode 0
>> 1 0 0
>> cost threshold for parallelism 0
>> 32767 5 5
>> Cross DB Ownership Chaining 0
>> 1 0 0
>> cursor threshold -1
>> 2147483647 -1 -1
>> default full-text language 0
>> 2147483647 1033 1033
>> default language 0
>> 9999 0 0
>> fill factor (%) 0
>> 100 0 0
>> index create memory (KB) 704
>> 2147483647 0 0
>> lightweight pooling 0
>> 1 0 0
>> locks 5000
>> 2147483647 0 0
>> max degree of parallelism 0
>> 32 0 0
>> max server memory (MB) 4
>> 2147483647 5120 5120
>> max text repl size (B) 0
>> 2147483647 65536 65536
>> max worker threads 32
>> 32767 255 255
>> media retention 0
>> 365 0 0
>> min memory per query (KB) 512
>> 2147483647 1024 1024
>> min server memory (MB) 0
>> 2147483647 0 0
>> nested triggers 0
>> 1 1 1
>> network packet size (B) 512
>> 65536 4096 4096
>> open objects 0
>> 2147483647 0 0
>> priority boost 0
>> 1 0 0
>> query governor cost limit 0
>> 2147483647 0 0
>> query wait (s) -1
>> 2147483647 -1 -1
>> recovery interval (min) 0
>> 32767 0 0
>> remote access 0
>> 1 1 1
>> remote login timeout (s) 0
>> 2147483647 20 20
>> remote proc trans 0
>> 1 0 0
>> remote query timeout (s) 0
>> 2147483647 600 600
>> scan for startup procs 0
>> 1 1 0
>> set working set size 0
>> 1 0 0
>> show advanced options 0
>> 1 1 1
>> two digit year cutoff 1753
>> 9999 2049 2049
>> user connections 0
>> 32767 0 0
>> user options 0
>> 32767 56 56
>>
>>
>
>.
>|||According to the results of sp_configure your run value is still set to 0
for AWE. Did you restart the server? And are you absolutely sure you have
SQL EE? What does xp_msver show?
--
Andrew J. Kelly SQL MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:a04c01c434f9$3dde5ae0$a401280a@.phx.gbl...
> The SQL Server service account is listed in the Lock
> pages in memory is set the same way three other servers
> that work correctly.
> Is this server not recognizing this setting?
> Please help me with this problem.
> Thanks,
> Mike
>
> >--Original Message--
> >Do you have Lock Pages In Memory set properly? See this:
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;811891&Product=sql2k
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Mike" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:9ede01c4349c$357f8a70$a401280a@.phx.gbl...
> >>
> >> I have a server with SQL Server 2000 Enterprise Edition
> >> with SP3. The boot.ini is set with /3gb /PAE. The
> >> server system properties list 8GB of RAM. Within SQL
> >> Server sp_configure AWE running is set to 1. When I
> look
> >> in the SQL Server error log it tells me that 8
> processors
> >> and 2048 MB RAM where detected. SQL Server Memory
> >> properties are set with the Maximum to 5.12 GB. But
> SQL
> >> Server does not recognize AWE setting. The Server
> >> Performance Monitor Counter under SQL Server Memory
> >> Manager with Target Server Memory list 2.7GB. This
> >> should be 5.12 GB of memory for SQL Server.
> >>
> >> Please help me resolve this problem.
> >>
> >> Mike
> >>
> >>
> __________________________________________________________
> >> [boot loader]
> >> timeout=10
> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
> >> [operating systems]
> >> multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft
> >> Windows 2000 Advanced Server" /fastdetect /3gb /PAE
> >>
> __________________________________________________________
> >> _
> >> sp_configure "show advanced options", 1
> >> RECONFIGURE
> >> GO
> >> sp_configure "awe enabled", 1
> >> RECONFIGURE
> >> GO
> >> sp_configure "max server memory", 5120
> >> RECONFIGURE
> >> GO
> >> sp_configure "min server memory", 0
> >> RECONFIGURE
> >> GO
> >>
> __________________________________________________________
> >> _
> >> Output from SP_CONFIGURE
> >> name minimum
> >> maximum config_value run_value
> >> -- -- --
> --
> >> -
> >> -- --
> >> affinity mask -2147483648
> >> 2147483647 0 0
> >> allow updates 0
> >> 1 0 0
> >> awe enabled 0
> >> 1 1 1
> >> c2 audit mode 0
> >> 1 0 0
> >> cost threshold for parallelism 0
> >> 32767 5 5
> >> Cross DB Ownership Chaining 0
> >> 1 0 0
> >> cursor threshold -1
> >> 2147483647 -1 -1
> >> default full-text language 0
> >> 2147483647 1033 1033
> >> default language 0
> >> 9999 0 0
> >> fill factor (%) 0
> >> 100 0 0
> >> index create memory (KB) 704
> >> 2147483647 0 0
> >> lightweight pooling 0
> >> 1 0 0
> >> locks 5000
> >> 2147483647 0 0
> >> max degree of parallelism 0
> >> 32 0 0
> >> max server memory (MB) 4
> >> 2147483647 5120 5120
> >> max text repl size (B) 0
> >> 2147483647 65536 65536
> >> max worker threads 32
> >> 32767 255 255
> >> media retention 0
> >> 365 0 0
> >> min memory per query (KB) 512
> >> 2147483647 1024 1024
> >> min server memory (MB) 0
> >> 2147483647 0 0
> >> nested triggers 0
> >> 1 1 1
> >> network packet size (B) 512
> >> 65536 4096 4096
> >> open objects 0
> >> 2147483647 0 0
> >> priority boost 0
> >> 1 0 0
> >> query governor cost limit 0
> >> 2147483647 0 0
> >> query wait (s) -1
> >> 2147483647 -1 -1
> >> recovery interval (min) 0
> >> 32767 0 0
> >> remote access 0
> >> 1 1 1
> >> remote login timeout (s) 0
> >> 2147483647 20 20
> >> remote proc trans 0
> >> 1 0 0
> >> remote query timeout (s) 0
> >> 2147483647 600 600
> >> scan for startup procs 0
> >> 1 1 0
> >> set working set size 0
> >> 1 0 0
> >> show advanced options 0
> >> 1 1 1
> >> two digit year cutoff 1753
> >> 9999 2049 2049
> >> user connections 0
> >> 32767 0 0
> >> user options 0
> >> 32767 56 56
> >>
> >>
> >>
> >>
> >
> >
> >.
> >
AWE question (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...
>
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
>>
>>
>
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...
>
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 SQL Server 2000 & 2005
I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
AWE on SQL Server 2000 & 2005
I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBA
You need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA
|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
SQL serer DBA
You need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA
|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>
AWE on SQL Server 2000 & 2005
I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
--
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
--
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
>> 2000 Enterprose I would like to use AWE,
>> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
>> SQL
>> 2005 Enterprose I would like to use AWE,
>> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> --
>> SQL serer DBA
>
2000 Enterprose I would like to use AWE,
to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
I have windows2003 server 32 bit version, 16Gb ram on it, running inder SQL
2005 Enterprose I would like to use AWE,
to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
please let me know if any one have this information.
--
SQL serer DBAYou need the /PAE switch although Win2003 may automatically add it for you.
The /3GB can not be used with 16GB but can with 8GB. It is up to you if you
need the extra directly addressable memory or not. IN either case you will
also need to enable AWE in SQL Server.
--
Andrew J. Kelly SQL MVP
"Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
> 2000 Enterprose I would like to use AWE,
> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
> SQL
> 2005 Enterprose I would like to use AWE,
> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
> please let me know if any one have this information.
>
> --
> SQL serer DBA|||And if you enable AWE in SQL Server without the PAE switch being on, you
aren't going to get anything. The PAE switch causes a different NT kernel
to be loaded which contains the code to manipulate memory addresses above
the 32 bit address space. Keep in mind that AWE is for data only. No
executable code can exist outside of the 32 bit address space. It's
actually quite rare to have an application with memory pressure due to data
alone.
--
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eoJ8YgtGGHA.312@.TK2MSFTNGP09.phx.gbl...
> You need the /PAE switch although Win2003 may automatically add it for
> you. The /3GB can not be used with 16GB but can with 8GB. It is up to you
> if you need the extra directly addressable memory or not. IN either case
> you will also need to enable AWE in SQL Server.
> --
> Andrew J. Kelly SQL MVP
>
> "Srikanth" <Srikanth@.discussions.microsoft.com> wrote in message
> news:61F51031-1B5D-454B-B88C-9D30442A5932@.microsoft.com...
>>I have windows2003 server 32 bit version, 8Gb ram on it, running inder SQL
>> 2000 Enterprose I would like to use AWE,
>> to enable AWE I need to add onlt \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> I have windows2003 server 32 bit version, 16Gb ram on it, running inder
>> SQL
>> 2005 Enterprose I would like to use AWE,
>> to enable AWE I need to add only \PAE or I need \3gb + \PAE in boot.ini?
>> please let me know if any one have this information.
>>
>> --
>> SQL serer DBA
>
AWE Memory on SQL Server 2000(SP4)
Hello everybody
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
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> I believe you need Enterprise versions of SQL Server and your OS to use AW
E.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confir
m
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...[vbcol=seagreen]
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
>
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
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> I believe you need Enterprise versions of SQL Server and your OS to use AW
E.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confir
m
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...[vbcol=seagreen]
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
>
AWE Memory on SQL Server 2000(SP4)
Hello everybody
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
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.
Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>
|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> I believe you need Enterprise versions of SQL Server and your OS to use AWE.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confirm
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>
|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...[vbcol=seagreen]
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
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
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.
Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>
|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> I believe you need Enterprise versions of SQL Server and your OS to use AWE.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confirm
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>
|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...[vbcol=seagreen]
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
AWE Memory on SQL Server 2000(SP4)
Hello everybody
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
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> > Hello everybody
> > 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
> >
> > SQL Server is using 2,7 GB.
> > Application is using three processes , that each one is about 50 MB .
> >
> > I took a Page Life expectancy counter which was under 300 for about 10-15
> > minuets and after grown up till 320 ... and then droped again...and up
> > again..
> >
> > Do you think I need to enable AWE? If you do , how much memory to give to
> > SQL Server?
> > I have heard that there is a problem with SP4 and AWE, am I right?
> >
> > Thank you.
> I believe you need Enterprise versions of SQL Server and your OS to use AWE.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confirm
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
>> "Alex" <test@.hotmail.com> wrote in message
>> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
>> > Hello everybody
>> > 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
>> >
>> > SQL Server is using 2,7 GB.
>> > Application is using three processes , that each one is about 50 MB .
>> >
>> > I took a Page Life expectancy counter which was under 300 for about
>> > 10-15
>> > minuets and after grown up till 320 ... and then droped again...and
>> > up
>> > again..
>> >
>> > Do you think I need to enable AWE? If you do , how much memory to give
>> > to
>> > SQL Server?
>> > I have heard that there is a problem with SP4 and AWE, am I right?
>> >
>> > Thank you.
>> I believe you need Enterprise versions of SQL Server and your OS to use
>> AWE.
>> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
>> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
>> Server to 6GB
>> sp_configure 'show advanced options', 1
>> RECONFIGURE
>> GO
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>> GO
>> sp_configure 'max server memory', 6144
>> RECONFIGURE
>> GO
>>
>> When you restart SQL Server you should see Address Windowing Extensions
>> Enabled in the log.
>>
>> You can also use the SQL Performance counter-Total Server Memory to
>> confirm
>> that SQL is using 6GB.
>>
>> Read these:
>> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>>
>>
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
SQL Server is using 2,7 GB.
Application is using three processes , that each one is about 50 MB .
I took a Page Life expectancy counter which was under 300 for about 10-15
minuets and after grown up till 320 ... and then droped again...and up
again..
Do you think I need to enable AWE? If you do , how much memory to give to
SQL Server?
I have heard that there is a problem with SP4 and AWE, am I right?
Thank you.Definitely enable AWE. Also make sure that /PAE is in the boot.ini file.
You will need to apply at least one hotfix after SP4 to get AWE to woork
correctly.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
>
>
>
>|||"Alex" <test@.hotmail.com> wrote in message
news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> Hello everybody
> 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
> SQL Server is using 2,7 GB.
> Application is using three processes , that each one is about 50 MB .
> I took a Page Life expectancy counter which was under 300 for about 10-15
> minuets and after grown up till 320 ... and then droped again...and up
> again..
> Do you think I need to enable AWE? If you do , how much memory to give to
> SQL Server?
> I have heard that there is a problem with SP4 and AWE, am I right?
> Thank you.
I believe you need Enterprise versions of SQL Server and your OS to use AWE.
If you have these I would add /PAE and /3GB to boot.ini, install the SP4
hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
Server to 6GB
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
When you restart SQL Server you should see Address Windowing Extensions
Enabled in the log.
You can also use the SQL Performance counter-Total Server Memory to confirm
that SQL is using 6GB.
Read these:
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp|||Hi,
What is the hotfix after SP4 installed ?
Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
JT
"Terri" wrote:
> "Alex" <test@.hotmail.com> wrote in message
> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
> > Hello everybody
> > 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
> >
> > SQL Server is using 2,7 GB.
> > Application is using three processes , that each one is about 50 MB .
> >
> > I took a Page Life expectancy counter which was under 300 for about 10-15
> > minuets and after grown up till 320 ... and then droped again...and up
> > again..
> >
> > Do you think I need to enable AWE? If you do , how much memory to give to
> > SQL Server?
> > I have heard that there is a problem with SP4 and AWE, am I right?
> >
> > Thank you.
> I believe you need Enterprise versions of SQL Server and your OS to use AWE.
> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
> Server to 6GB
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
> When you restart SQL Server you should see Address Windowing Extensions
> Enabled in the log.
>
> You can also use the SQL Performance counter-Total Server Memory to confirm
> that SQL is using 6GB.
>
> Read these:
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>|||The hotfix (build 2040) fixes a bug introduced in SP4 related to AWE on
32-bit host computers. The hotfix is only necessary if you have installed
SP4 and yout host computer has more than 4GB of physicl memory.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D1A4714E-D506-4D9F-912E-C44AB8595E92@.microsoft.com...
> Hi,
> What is the hotfix after SP4 installed ?
> Do I need to apply the hotfix if I am running SP3a on SQL2000 ?
> JT
> "Terri" wrote:
>> "Alex" <test@.hotmail.com> wrote in message
>> news:uzB1UnkkHHA.1240@.TK2MSFTNGP04.phx.gbl...
>> > Hello everybody
>> > 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
>> >
>> > SQL Server is using 2,7 GB.
>> > Application is using three processes , that each one is about 50 MB .
>> >
>> > I took a Page Life expectancy counter which was under 300 for about
>> > 10-15
>> > minuets and after grown up till 320 ... and then droped again...and
>> > up
>> > again..
>> >
>> > Do you think I need to enable AWE? If you do , how much memory to give
>> > to
>> > SQL Server?
>> > I have heard that there is a problem with SP4 and AWE, am I right?
>> >
>> > Thank you.
>> I believe you need Enterprise versions of SQL Server and your OS to use
>> AWE.
>> If you have these I would add /PAE and /3GB to boot.ini, install the SP4
>> hotfix pertaining to AWE and then enable AWE in SQL Server limiting SQL
>> Server to 6GB
>> sp_configure 'show advanced options', 1
>> RECONFIGURE
>> GO
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>> GO
>> sp_configure 'max server memory', 6144
>> RECONFIGURE
>> GO
>>
>> When you restart SQL Server you should see Address Windowing Extensions
>> Enabled in the log.
>>
>> You can also use the SQL Performance counter-Total Server Memory to
>> confirm
>> that SQL is using 6GB.
>>
>> Read these:
>> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>>
>>
Wednesday, March 7, 2012
AWE and Target Server Memory
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1What version of SQL Server are you using?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switche
s
>set.
>The question I have, is what I am seeing for Target and Total Server Memory
:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||What happens if you set the min server memory and restart SQL Server?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Window
s
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/defaul...kb;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windo
ws
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1What version of SQL Server are you using?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663faf808d6ce@.uwe...
Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
This is the script we used to enable AWE and set Max Memory, essentially
leaving 2GB for the OS.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
Just so you are aware, we do have the boot.ini with the PAE and 3GB switches
set.
The question I have, is what I am seeing for Target and Total Server Memory:
Target Server Memory(KB) = 4087767
Total Server Memory(KB) = 4087747
I was expecting to see more Target Server Memory being used (closer to 6GB)
rather than only 4087767KB / 3.898GB.
Please explain.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB switche
s
>set.
>The question I have, is what I am seeing for Target and Total Server Memory
:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Which SP level? What's the result of running:
SELECT @.@.VERSION
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:663fdb867f662@.uwe...
SQL 2000
Tom Moreau wrote:
>What version of SQL Server are you using?
>Prior to enabling AWE, we had 8GB RAM but utilizing only 2.7GB.
>This is the script we used to enable AWE and set Max Memory, essentially
>leaving 2GB for the OS.
>sp_configure 'show advanced options', 1
>RECONFIGURE
>GO
>sp_configure 'awe enabled', 1
>RECONFIGURE
>GO
>sp_configure 'max server memory', 6144
>RECONFIGURE
>GO
>Just so you are aware, we do have the boot.ini with the PAE and 3GB
>switches
>set.
>The question I have, is what I am seeing for Target and Total Server
>Memory:
>Target Server Memory(KB) = 4087767
>Total Server Memory(KB) = 4087747
>I was expecting to see more Target Server Memory being used (closer to 6GB)
>rather than only 4087767KB / 3.898GB.
>Please explain.
Message posted via http://www.droptable.com|||Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||What happens if you set the min server memory and restart SQL Server?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:664097d00a0ed@.uwe...
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows
NT 5.2 (Build 3790: Service Pack 1)
Tom Moreau wrote:[vbcol=seagreen]
>Which SP level? What's the result of running:
>SELECT @.@.VERSION
>SQL 2000
>Tom Moreau wrote:
>[quoted text clipped - 27 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200609/1|||I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Window
s
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||In SQL 2005, server memory will gradually climb to the max server memory,
whether or not you're using AWE. In SQL 2000, it's supposed to take it in
one chunk, IIRC. I'm thinking that if max = min = whatever you really want,
then you may be forcing it up to that level straight away.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
.
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:6641520a8602d@.uwe...
I am away from the office and will not have access to the server until
tomorrow around 10:00 MST. Even then we will not be able to restart the
service until late tomorrow evening. Do you have a theory about setting "min
server memory"? I believe I recall on the "max server memory" the minimum is
set to 4. Anyway, just trying to follow your thought process on why the "min
server memory" might be inhibiting memory use.
Tom Moreau wrote:[vbcol=seagreen]
>What happens if you set the min server memory and restart SQL Server?
>Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
>Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on
>Windows
>NT 5.2 (Build 3790: Service Pack 1)
>Tom Moreau wrote:
>[quoted text clipped - 7 lines]
Message posted via http://www.droptable.com|||This is the 'expected behavior' of 8.00.2039 and is fixed in 8.00.2040. See
http://support.microsoft.com/defaul...kb;en-us;899761
Linchi
"cbrichards via droptable.com" wrote:
> Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windo
ws
> NT 5.2 (Build 3790: Service Pack 1)
>
> Tom Moreau wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200609/1
>
Subscribe to:
Posts (Atom)