What would be the optimal max server memory setting for the following
machine?
Dedicated SQL Server:
Intel Xeon MP 3.3 GHz (4 physical Processors)
136 GB (C Drive)
8.0 GB RAM
Microsoft Windows 2003 Enterprise Edition Service Pack 1 Build 3790
SQL Server Enterprise 2000, with SP3
The machine has following database sizes. All databases are being accessed
all the time by around 300+ concurrent users.
DB#1 - 536.44 MB
DB#2 - 1.09 GB
DB#3 - 3.27 GB
DB#4 - 4.92 GB
DB#5 - 5.29 GB
DB#6 - 15.09 GB
DB#7 - 50.13 GB
I am still learning the ins and outs of configuring higher end db servers.
Are there any other non-default server settings that I should change?"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
news:uqJkBN9uGHA.4756@.TK2MSFTNGP04.phx.gbl...
> What would be the optimal max server memory setting for the following
> machine?
> Dedicated SQL Server:
> Intel Xeon MP 3.3 GHz (4 physical Processors)
> 136 GB (C Drive)
> 8.0 GB RAM
> Microsoft Windows 2003 Enterprise Edition Service Pack 1 Build 3790
> SQL Server Enterprise 2000, with SP3
> The machine has following database sizes. All databases are being accessed
> all the time by around 300+ concurrent users.
> DB#1 - 536.44 MB
> DB#2 - 1.09 GB
> DB#3 - 3.27 GB
> DB#4 - 4.92 GB
> DB#5 - 5.29 GB
> DB#6 - 15.09 GB
> DB#7 - 50.13 GB
> I am still learning the ins and outs of configuring higher end db servers.
>
Does each user access all databases or does each database have its own set
of users?
If the different databsaes represent seperate applications, you should
consider dividing the server into multiple SQL instances to divide up the
memory on the box and optionally the CPU's into 2 or 3 different resource
pools. 32bit SQL Server works more efficiently when it doesn't have to use
AWE to access memory, and multiple instances allow you to easilly partition
memory and CPU resources between the workloads.
David|||>
> Does each user access all databases or does each database have its own set
> of users?
All databases are the same application (different clients on each db similar
to an ASP service).
Each user usually accesses only a single database. Admin users would need
access to all.
> If the different databsaes represent seperate applications, you should
> consider dividing the server into multiple SQL instances to divide up the
> memory on the box and optionally the CPU's into 2 or 3 different resource
> pools. 32bit SQL Server works more efficiently when it doesn't have to
> use AWE to access memory, and multiple instances allow you to easilly
> partition memory and CPU resources between the workloads.
>
Interesting option. Your making me think about that.
You mention that 32bit SQL Server works more efficiently when it doesn't use
AWE. Does it affect performance that much?
My concern is the 50 GB database itself would benefit from more then 2 GB of
RAM.
You also mention that you can configure CPUs into different resource pools.
How does this work? Do you have a knowledge base link?|||"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
news:%23MUPzp9uGHA.4160@.TK2MSFTNGP06.phx.gbl...
> >
>> Does each user access all databases or does each database have its own
>> set of users?
> All databases are the same application (different clients on each db
> similar to an ASP service).
> Each user usually accesses only a single database. Admin users would need
> access to all.
>> If the different databsaes represent seperate applications, you should
>> consider dividing the server into multiple SQL instances to divide up the
>> memory on the box and optionally the CPU's into 2 or 3 different resource
>> pools. 32bit SQL Server works more efficiently when it doesn't have to
>> use AWE to access memory, and multiple instances allow you to easilly
>> partition memory and CPU resources between the workloads.
> Interesting option. Your making me think about that.
> You mention that 32bit SQL Server works more efficiently when it doesn't
> use AWE. Does it affect performance that much?
> My concern is the 50 GB database itself would benefit from more then 2 GB
> of RAM.
Yes it would, but you have 7 databses and only 8G of ram. How much ram can
you afford to allocate for that one workload. And using the /3GB switch you
can give a SQL instance access to 3GB of memory without using AWE.
Also you will have one procedure cache per instance, and on 32bit SQL is
strictly limited in size. Multiple instances would have multiple procedure
caches.
"On 32-bit platforms configured with 4 GB or more of physical memory, you
can either use Address Windowing Extensions (AWE) or use multiple instances
of SQL Server as a way to fully utilize the large amount of physical memory.
AWE may work well for some scenarios; however, you should be aware that AWE
memory can only be used for data cache. The memory for procedure cache,
connections, locks, and other internal resources of SQL Server must come
from the 2 GB (or 3GB, depending on the settings used) portion of the
virtual memory. On systems needing to support a large number of databases
and user connections, multiple instances of SQL Server may be a better
approach to fully alleviate the 2 GB or 3GB memory constraint imposed by the
32-bit platform for these data structures."
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/32bitconsolidation.mspx
> You also mention that you can configure CPUs into different resource
> pools. How does this work? Do you have a knowledge base link?
>
Simple partition of CPU's to SQL Instances should be done with the "affinity
mask" server option.
SQL Server 2005 Books Online
affinity mask Option
http://msdn2.microsoft.com/en-us/library/ms187104.aspx
Dynamic CPU allocation policies can be implemented with WSRM:
Windows System Resource Manager
http://www.microsoft.com/technet/downloads/winsrvr/wsrm.mspx
David|||"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:O$v%232B%23uGHA.3428@.TK2MSFTNGP02.phx.gbl...
> "Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
> news:%23MUPzp9uGHA.4160@.TK2MSFTNGP06.phx.gbl...
>> >
>> Does each user access all databases or does each database have its own
>> set of users?
>> All databases are the same application (different clients on each db
>> similar to an ASP service).
>> Each user usually accesses only a single database. Admin users would need
>> access to all.
>>
>> If the different databsaes represent seperate applications, you should
>> consider dividing the server into multiple SQL instances to divide up
>> the memory on the box and optionally the CPU's into 2 or 3 different
>> resource pools. 32bit SQL Server works more efficiently when it doesn't
>> have to use AWE to access memory, and multiple instances allow you to
>> easilly partition memory and CPU resources between the workloads.
>>
>> Interesting option. Your making me think about that.
>> You mention that 32bit SQL Server works more efficiently when it doesn't
>> use AWE. Does it affect performance that much?
>> My concern is the 50 GB database itself would benefit from more then 2 GB
>> of RAM.
> Yes it would, but you have 7 databses and only 8G of ram. How much ram
> can you afford to allocate for that one workload. And using the /3GB
> switch you can give a SQL instance access to 3GB of memory without using
> AWE.
> Also you will have one procedure cache per instance, and on 32bit SQL is
> strictly limited in size. Multiple instances would have multiple
> procedure caches.
> "On 32-bit platforms configured with 4 GB or more of physical memory, you
> can either use Address Windowing Extensions (AWE) or use multiple
> instances of SQL Server as a way to fully utilize the large amount of
> physical memory. AWE may work well for some scenarios; however, you should
> be aware that AWE memory can only be used for data cache. The memory for
> procedure cache, connections, locks, and other internal resources of SQL
> Server must come from the 2 GB (or 3GB, depending on the settings used)
> portion of the virtual memory. On systems needing to support a large
> number of databases and user connections, multiple instances of SQL Server
> may be a better approach to fully alleviate the 2 GB or 3GB memory
> constraint imposed by the 32-bit platform for these data structures."
> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/32bitconsolidation.mspx
>> You also mention that you can configure CPUs into different resource
>> pools. How does this work? Do you have a knowledge base link?
> Simple partition of CPU's to SQL Instances should be done with the
> "affinity mask" server option.
> SQL Server 2005 Books Online
> affinity mask Option
> http://msdn2.microsoft.com/en-us/library/ms187104.aspx
>
> Dynamic CPU allocation policies can be implemented with WSRM:
> Windows System Resource Manager
> http://www.microsoft.com/technet/downloads/winsrvr/wsrm.mspx
> David
>
Thanks David. This info is very helpful.|||Isaac
> Dedicated SQL Server:
> Intel Xeon MP 3.3 GHz (4 physical Processors)
> 136 GB (C Drive)
> 8.0 GB RAM
I'd consider (based on your description) MAX Memory 7GB
"Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
news:%23$AxxK%23uGHA.4752@.TK2MSFTNGP02.phx.gbl...
> "David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
> message news:O$v%232B%23uGHA.3428@.TK2MSFTNGP02.phx.gbl...
>> "Isaac Alexander" <isaacNOSPAM@.goNOSPAMprocura.com> wrote in message
>> news:%23MUPzp9uGHA.4160@.TK2MSFTNGP06.phx.gbl...
>> >
>> Does each user access all databases or does each database have its own
>> set of users?
>> All databases are the same application (different clients on each db
>> similar to an ASP service).
>> Each user usually accesses only a single database. Admin users would
>> need access to all.
>>
>> If the different databsaes represent seperate applications, you should
>> consider dividing the server into multiple SQL instances to divide up
>> the memory on the box and optionally the CPU's into 2 or 3 different
>> resource pools. 32bit SQL Server works more efficiently when it
>> doesn't have to use AWE to access memory, and multiple instances allow
>> you to easilly partition memory and CPU resources between the
>> workloads.
>>
>> Interesting option. Your making me think about that.
>> You mention that 32bit SQL Server works more efficiently when it doesn't
>> use AWE. Does it affect performance that much?
>> My concern is the 50 GB database itself would benefit from more then 2
>> GB of RAM.
>> Yes it would, but you have 7 databses and only 8G of ram. How much ram
>> can you afford to allocate for that one workload. And using the /3GB
>> switch you can give a SQL instance access to 3GB of memory without using
>> AWE.
>> Also you will have one procedure cache per instance, and on 32bit SQL is
>> strictly limited in size. Multiple instances would have multiple
>> procedure caches.
>> "On 32-bit platforms configured with 4 GB or more of physical memory, you
>> can either use Address Windowing Extensions (AWE) or use multiple
>> instances of SQL Server as a way to fully utilize the large amount of
>> physical memory. AWE may work well for some scenarios; however, you
>> should be aware that AWE memory can only be used for data cache. The
>> memory for procedure cache, connections, locks, and other internal
>> resources of SQL Server must come from the 2 GB (or 3GB, depending on the
>> settings used) portion of the virtual memory. On systems needing to
>> support a large number of databases and user connections, multiple
>> instances of SQL Server may be a better approach to fully alleviate the 2
>> GB or 3GB memory constraint imposed by the 32-bit platform for these data
>> structures."
>> http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/32bitconsolidation.mspx
>> You also mention that you can configure CPUs into different resource
>> pools. How does this work? Do you have a knowledge base link?
>>
>> Simple partition of CPU's to SQL Instances should be done with the
>> "affinity mask" server option.
>> SQL Server 2005 Books Online
>> affinity mask Option
>> http://msdn2.microsoft.com/en-us/library/ms187104.aspx
>>
>> Dynamic CPU allocation policies can be implemented with WSRM:
>> Windows System Resource Manager
>> http://www.microsoft.com/technet/downloads/winsrvr/wsrm.mspx
>> David
> Thanks David. This info is very helpful.
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uYF1sPEvGHA.724@.TK2MSFTNGP05.phx.gbl...
> Isaac
>> Dedicated SQL Server:
>> Intel Xeon MP 3.3 GHz (4 physical Processors)
>> 136 GB (C Drive)
>> 8.0 GB RAM
>
> I'd consider (based on your description) MAX Memory 7GB
>
Thanks Uri.
Showing posts with label dedicated. Show all posts
Showing posts with label dedicated. Show all posts
Thursday, March 8, 2012
AWE Memory?
Hi all?
I've tried reading about how AWE memory works but I really can't figure it
out...
I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
as much as possible of the RAM for SQL Server.
I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
space is in my interest to use for SQL Server.
If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
than 4 Gbytes RAM?
regards
fredrik
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
I don't think you need to enable AWE memory in that case
AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik
|||If we are talking about the memory usage as measured by the SQL counter Total
Server Memory, you need to enable AWE to use more than 3GB. It is not correct
that AWE is used only for RAM that exceeds 4GB.
Linchi
"Uri Dimant" wrote:
> I don't think you need to enable AWE memory in that case
> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>
>
|||Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downlo...dv64BitEnv.doc
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter Total
> Server Memory, you need to enable AWE to use more than 3GB. It is not correct
> that AWE is used only for RAM that exceeds 4GB.
> Linchi
> "Uri Dimant" wrote:
|||Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downlo...dv64BitEnv.doc
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter Total
> Server Memory, you need to enable AWE to use more than 3GB. It is not correct
> that AWE is used only for RAM that exceeds 4GB.
> Linchi
> "Uri Dimant" wrote:
|||What you need instead of all these buggy flags is to move to x64 where the
memory issue doesn't exist at all. Of course you also need to make sure you
run SQL Server 64 bit as well, not the 32 bit version on a 64 bit system.
Unfortunately very few dedicated hosts offer Windows 2003 x64.
KL
"Fredrik" <Fredrik@.discussions.microsoft.com> skrev i meddelandet
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik
|||Here's some empirical evidence from the test scenarios in which severe memory
pressure was put on the instance with 4GB of RAM. If the following comes out
unreadable format-wise, drop me an email and I send you the charts.
Linchi
linchi_shea@.take-this-out-FIRSTml.com
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N N 500 560
1000 N N 1000 1060
1500 N N 1206 1266
2000 N N 1206 1266
2500 N N 1206 1266
3000 N N 1206 1266
3500 N N 1206 1266
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y N 500 61
1000 Y N 1000 67
1500 Y N 1500 71
2000 Y N 2000 76
2500 Y N 2500 81
3000 Y N 3000 86
3500 Y N 3500 90
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y Y 500 65
1000 Y Y 1000 70
1500 Y Y 1500 75
2000 Y Y 2000 80
2500 Y Y 2500 84
3000 Y Y 3000 89
3500 Y Y 3500 94
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N Y 500 550
1000 N Y 1000 1055
1500 N Y 1500 1561
2000 N Y 2000 2067
2500 N Y 2219 2290
3000 N Y 2219 2290
3500 N Y 2219 2290
"Arnie Rowland" wrote:
[vbcol=seagreen]
> Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
> I've been going by the following:
> "AWE is a set of memory management extensions to the Microsoft Win32? API that allows applications to address memory beyond 4 GB."
> From: http://download.microsoft.com/downlo...dv64BitEnv.doc
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
|||Hi Fredrick,
If your server is running 4 GB of memory, then you don't want to have
SQL Server running more than 3 GB. Part of the reason for that is that
you have to leave sufficient space for the OS to operate and 1 GB of
RAN for the OS is a good amount (yeah, I know it'll run on less). The
other reason is that AWE requires 1 GB of RAM just to manage the
memory swaps that are going on. So running AWE on a 4 GB server is
likely to make things worse, not better.
So if you really think you need to be running AWE:
(1) Have at least 6 GB of memory on the server and that this is the
only instance of SQL Server running on the server.
(2) After enabling AWE and setting the /3GB and /PAE switches in the
boot.ini file, configure your max memory setting to equal your total
memory minus 1 GB (for the OS). If you don't configure the max memory
setting you leave open the possibility that SQL Server will grab all
but 128 MB of RAM to operate, leaving you a memory-starved OS that
will perform poorly (if at all) due to heavy paging of the OS to the
swap file.
Before enabling AWE you need to do your homework on whether the extra
memory will actually do you any good. Our team manages 500+ instances
of SQL 2000 & 2005 and in all the 15+ years I've worked as a SQL DBA
the vast majority of performance issues I've seen are due to
application and/or database design. You'll be amazed at how well SQL
will run on 3 GB of RAM, especially with a well-designed system. Good
luck to you!
On Fri, 13 Oct 2006 00:03:01 -0700, Fredrik
<Fredrik@.discussions.microsoft.com> wrote:
>Hi all?
>I've tried reading about how AWE memory works but I really can't figure it
>out...
>I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
>2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
>as much as possible of the RAM for SQL Server.
>I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
>use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
>Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
>space is in my interest to use for SQL Server.
>If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
>able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
>than 4 Gbytes RAM?
>regards
>fredrik
I've tried reading about how AWE memory works but I really can't figure it
out...
I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
as much as possible of the RAM for SQL Server.
I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
space is in my interest to use for SQL Server.
If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
than 4 Gbytes RAM?
regards
fredrik
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
I don't think you need to enable AWE memory in that case
AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik
|||If we are talking about the memory usage as measured by the SQL counter Total
Server Memory, you need to enable AWE to use more than 3GB. It is not correct
that AWE is used only for RAM that exceeds 4GB.
Linchi
"Uri Dimant" wrote:
> I don't think you need to enable AWE memory in that case
> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>
>
|||Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downlo...dv64BitEnv.doc
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter Total
> Server Memory, you need to enable AWE to use more than 3GB. It is not correct
> that AWE is used only for RAM that exceeds 4GB.
> Linchi
> "Uri Dimant" wrote:
|||Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downlo...dv64BitEnv.doc
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter Total
> Server Memory, you need to enable AWE to use more than 3GB. It is not correct
> that AWE is used only for RAM that exceeds 4GB.
> Linchi
> "Uri Dimant" wrote:
|||What you need instead of all these buggy flags is to move to x64 where the
memory issue doesn't exist at all. Of course you also need to make sure you
run SQL Server 64 bit as well, not the 32 bit version on a 64 bit system.
Unfortunately very few dedicated hosts offer Windows 2003 x64.
KL
"Fredrik" <Fredrik@.discussions.microsoft.com> skrev i meddelandet
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik
|||Here's some empirical evidence from the test scenarios in which severe memory
pressure was put on the instance with 4GB of RAM. If the following comes out
unreadable format-wise, drop me an email and I send you the charts.
Linchi
linchi_shea@.take-this-out-FIRSTml.com
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N N 500 560
1000 N N 1000 1060
1500 N N 1206 1266
2000 N N 1206 1266
2500 N N 1206 1266
3000 N N 1206 1266
3500 N N 1206 1266
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y N 500 61
1000 Y N 1000 67
1500 Y N 1500 71
2000 Y N 2000 76
2500 Y N 2500 81
3000 Y N 3000 86
3500 Y N 3500 90
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y Y 500 65
1000 Y Y 1000 70
1500 Y Y 1500 75
2000 Y Y 2000 80
2500 Y Y 2500 84
3000 Y Y 3000 89
3500 Y Y 3500 94
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N Y 500 550
1000 N Y 1000 1055
1500 N Y 1500 1561
2000 N Y 2000 2067
2500 N Y 2219 2290
3000 N Y 2219 2290
3500 N Y 2219 2290
"Arnie Rowland" wrote:
[vbcol=seagreen]
> Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
> I've been going by the following:
> "AWE is a set of memory management extensions to the Microsoft Win32? API that allows applications to address memory beyond 4 GB."
> From: http://download.microsoft.com/downlo...dv64BitEnv.doc
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
|||Hi Fredrick,
If your server is running 4 GB of memory, then you don't want to have
SQL Server running more than 3 GB. Part of the reason for that is that
you have to leave sufficient space for the OS to operate and 1 GB of
RAN for the OS is a good amount (yeah, I know it'll run on less). The
other reason is that AWE requires 1 GB of RAM just to manage the
memory swaps that are going on. So running AWE on a 4 GB server is
likely to make things worse, not better.
So if you really think you need to be running AWE:
(1) Have at least 6 GB of memory on the server and that this is the
only instance of SQL Server running on the server.
(2) After enabling AWE and setting the /3GB and /PAE switches in the
boot.ini file, configure your max memory setting to equal your total
memory minus 1 GB (for the OS). If you don't configure the max memory
setting you leave open the possibility that SQL Server will grab all
but 128 MB of RAM to operate, leaving you a memory-starved OS that
will perform poorly (if at all) due to heavy paging of the OS to the
swap file.
Before enabling AWE you need to do your homework on whether the extra
memory will actually do you any good. Our team manages 500+ instances
of SQL 2000 & 2005 and in all the 15+ years I've worked as a SQL DBA
the vast majority of performance issues I've seen are due to
application and/or database design. You'll be amazed at how well SQL
will run on 3 GB of RAM, especially with a well-designed system. Good
luck to you!
On Fri, 13 Oct 2006 00:03:01 -0700, Fredrik
<Fredrik@.discussions.microsoft.com> wrote:
>Hi all?
>I've tried reading about how AWE memory works but I really can't figure it
>out...
>I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
>2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
>as much as possible of the RAM for SQL Server.
>I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
>use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
>Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
>space is in my interest to use for SQL Server.
>If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
>able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
>than 4 Gbytes RAM?
>regards
>fredrik
AWE Memory?
Hi all?
I've tried reading about how AWE memory works but I really can't figure it
out...
I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
as much as possible of the RAM for SQL Server.
I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
space is in my interest to use for SQL Server.
If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
than 4 Gbytes RAM?
regards
fredrik> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
I don't think you need to enable AWE memory in that case
AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||If we are talking about the memory usage as measured by the SQL counter Total
Server Memory, you need to enable AWE to use more than 3GB. It is not correct
that AWE is used only for RAM that exceeds 4GB.
Linchi
"Uri Dimant" wrote:
> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> > be
> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> > more
> > than 4 Gbytes RAM?
> I don't think you need to enable AWE memory in that case
> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> > Hi all?
> >
> > I've tried reading about how AWE memory works but I really can't figure it
> > out...
> >
> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> > use
> > as much as possible of the RAM for SQL Server.
> >
> > I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> > 1
> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> > space is in my interest to use for SQL Server.
> >
> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> > be
> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> > more
> > than 4 Gbytes RAM?
> >
> > regards
> > fredrik
>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Could you give us some support on that assertion? (It is not correct =that AWE is used only for RAM that exceeds 4GB." If my information is =incorrect, I would like to update it to reflect that which is indeed =correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 =GB."
From: =http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134=
a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message =news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
> If we are talking about the memory usage as measured by the SQL =counter Total > Server Memory, you need to enable AWE to use more than 3GB. It is not =correct > that AWE is used only for RAM that exceeds 4GB.
> > Linchi
> > "Uri Dimant" wrote:
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >> I don't think you need to enable AWE memory in that case
>> AWE memory is used only for the RAM that exceeds the base 4GB of =RAM.
>> >> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>> >> >> >> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message >> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>> > Hi all?
>> >
>> > I've tried reading about how AWE memory works but I really can't =figure it
>> > out...
>> >
>> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a =Windows
>> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be =able to >> > use
>> > as much as possible of the RAM for SQL Server.
>> >
>> > I have entered the Boot.ini with the /3GB parameter to allow SQL =Server to
>> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is =still >> > 1
>> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of =that free
>> > space is in my interest to use for SQL Server.
>> >
>> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >
>> > regards
>> > fredrik >> >> --=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Could you give us some support on that =assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." =If my information is incorrect, I would like to update it to reflect that =which is indeed correct...
I've been going by the following: ="AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4=451-8fdb-7134a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, =Ph.D.Westwood Consulting, Inc
Most good judgment comes from =experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea" wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...> =If we are talking about the memory usage as measured by the SQL counter Total > =Server Memory, you need to enable AWE to use more than 3GB. It is not correct => that AWE is used only for RAM that exceeds 4GB.> > =Linchi> > "Uri Dimant" wrote:> > > If I enable AWE =memory and set the max server memory to 3,5 Gbyte will I > > be> > able to use that extra 512 Mbytes as well? Or is AWE =only for boxes with > > more> > than 4 Gbytes RAM?> > I don't think you need to enable AWE =memory in that case> AWE memory is used only for the RAM that =exceeds the base 4GB of RAM.> >>> > > > ="Fredrik" wrote in message > news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...> > Hi all?> =>> > I've tried reading about how AWE memory works but I really can't figure it> > out...> >> > I have a =dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows> > =2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to => > use> > as much as possible of the RAM for SQL Server.> >> > I have entered the Boot.ini =with the /3GB parameter to allow SQL Server to> > use 3 Gbytes of =RAM instead of the default of 2 Gbyte. But there is still > > 1> > Gbyte "left" in the box to be used by OS. At least =512Mbytes of that free> > space is in my interest to use for SQL Server.> >> > If I enable AWE memory and set =the max server memory to 3,5 Gbyte will I > > be> > =able to use that extra 512 Mbytes as well? Or is AWE only for boxes with => > more> > than 4 Gbytes RAM?> =>> > regards> > fredrik > > >
--=_NextPart_000_0518_01C6EEA8.1744A950--|||This is a multi-part message in MIME format.
--=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Could you give us some support on that assertion? (It is not correct =that AWE is used only for RAM that exceeds 4GB." If my information is =incorrect, I would like to update it to reflect that which is indeed =correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 =GB."
From: =http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134=
a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message =news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
> If we are talking about the memory usage as measured by the SQL =counter Total > Server Memory, you need to enable AWE to use more than 3GB. It is not =correct > that AWE is used only for RAM that exceeds 4GB.
> > Linchi
> > "Uri Dimant" wrote:
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >> I don't think you need to enable AWE memory in that case
>> AWE memory is used only for the RAM that exceeds the base 4GB of =RAM.
>> >> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>> >> >> >> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message >> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>> > Hi all?
>> >
>> > I've tried reading about how AWE memory works but I really can't =figure it
>> > out...
>> >
>> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a =Windows
>> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be =able to >> > use
>> > as much as possible of the RAM for SQL Server.
>> >
>> > I have entered the Boot.ini with the /3GB parameter to allow SQL =Server to
>> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is =still >> > 1
>> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of =that free
>> > space is in my interest to use for SQL Server.
>> >
>> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >
>> > regards
>> > fredrik >> >> --=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Could you give us some support on that =assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." =If my information is incorrect, I would like to update it to reflect that =which is indeed correct...
I've been going by the following: ="AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4=451-8fdb-7134a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, =Ph.D.Westwood Consulting, Inc
Most good judgment comes from =experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea" wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...> =If we are talking about the memory usage as measured by the SQL counter Total > =Server Memory, you need to enable AWE to use more than 3GB. It is not correct => that AWE is used only for RAM that exceeds 4GB.> > =Linchi> > "Uri Dimant" wrote:> > > If I enable AWE =memory and set the max server memory to 3,5 Gbyte will I > > be> > able to use that extra 512 Mbytes as well? Or is AWE =only for boxes with > > more> > than 4 Gbytes RAM?> > I don't think you need to enable AWE =memory in that case> AWE memory is used only for the RAM that =exceeds the base 4GB of RAM.> >>> > > > ="Fredrik" wrote in message > news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...> > Hi all?> =>> > I've tried reading about how AWE memory works but I really can't figure it> > out...> >> > I have a =dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows> > =2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to => > use> > as much as possible of the RAM for SQL Server.> >> > I have entered the Boot.ini =with the /3GB parameter to allow SQL Server to> > use 3 Gbytes of =RAM instead of the default of 2 Gbyte. But there is still > > 1> > Gbyte "left" in the box to be used by OS. At least =512Mbytes of that free> > space is in my interest to use for SQL Server.> >> > If I enable AWE memory and set =the max server memory to 3,5 Gbyte will I > > be> > =able to use that extra 512 Mbytes as well? Or is AWE only for boxes with => > more> > than 4 Gbytes RAM?> =>> > regards> > fredrik > > >
--=_NextPart_000_0518_01C6EEA8.1744A950--|||What you need instead of all these buggy flags is to move to x64 where the
memory issue doesn't exist at all. Of course you also need to make sure you
run SQL Server 64 bit as well, not the 32 bit version on a 64 bit system.
Unfortunately very few dedicated hosts offer Windows 2003 x64.
KL
"Fredrik" <Fredrik@.discussions.microsoft.com> skrev i meddelandet
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||Here's some empirical evidence from the test scenarios in which severe memory
pressure was put on the instance with 4GB of RAM. If the following comes out
unreadable format-wise, drop me an email and I send you the charts.
Linchi
linchi_shea@.take-this-out-FIRSTml.com
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N N 500 560
1000 N N 1000 1060
1500 N N 1206 1266
2000 N N 1206 1266
2500 N N 1206 1266
3000 N N 1206 1266
3500 N N 1206 1266
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y N 500 61
1000 Y N 1000 67
1500 Y N 1500 71
2000 Y N 2000 76
2500 Y N 2500 81
3000 Y N 3000 86
3500 Y N 3500 90
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y Y 500 65
1000 Y Y 1000 70
1500 Y Y 1500 75
2000 Y Y 2000 80
2500 Y Y 2500 84
3000 Y Y 3000 89
3500 Y Y 3500 94
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N Y 500 550
1000 N Y 1000 1055
1500 N Y 1500 1561
2000 N Y 2000 2067
2500 N Y 2219 2290
3000 N Y 2219 2290
3500 N Y 2219 2290
"Arnie Rowland" wrote:
> Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
> I've been going by the following:
> "AWE is a set of memory management extensions to the Microsoft Win32ï?¢ API that allows applications to address memory beyond 4 GB."
> From: http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134a004f94c/Adv64BitEnv.doc
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
> > If we are talking about the memory usage as measured by the SQL counter Total
> > Server Memory, you need to enable AWE to use more than 3GB. It is not correct
> > that AWE is used only for RAM that exceeds 4GB.
> >
> > Linchi
> >
> > "Uri Dimant" wrote:
> >
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> >> > be
> >> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> >> > more
> >> > than 4 Gbytes RAM?
> >>
> >> I don't think you need to enable AWE memory in that case
> >> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> >>
> >> http://support.microsoft.com/kb/274750
> >> http://www.sql-server-performance.com/awe_memory.asp
> >>
> >>
> >>
> >> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> >> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> >> > Hi all?
> >> >
> >> > I've tried reading about how AWE memory works but I really can't figure it
> >> > out...
> >> >
> >> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> >> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> >> > use
> >> > as much as possible of the RAM for SQL Server.
> >> >
> >> > I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> >> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> >> > 1
> >> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> >> > space is in my interest to use for SQL Server.
> >> >
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> >> > be
> >> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> >> > more
> >> > than 4 Gbytes RAM?
> >> >
> >> > regards
> >> > fredrik
> >>
> >>
> >>|||Hi Fredrick,
If your server is running 4 GB of memory, then you don't want to have
SQL Server running more than 3 GB. Part of the reason for that is that
you have to leave sufficient space for the OS to operate and 1 GB of
RAN for the OS is a good amount (yeah, I know it'll run on less). The
other reason is that AWE requires 1 GB of RAM just to manage the
memory swaps that are going on. So running AWE on a 4 GB server is
likely to make things worse, not better.
So if you really think you need to be running AWE:
(1) Have at least 6 GB of memory on the server and that this is the
only instance of SQL Server running on the server.
(2) After enabling AWE and setting the /3GB and /PAE switches in the
boot.ini file, configure your max memory setting to equal your total
memory minus 1 GB (for the OS). If you don't configure the max memory
setting you leave open the possibility that SQL Server will grab all
but 128 MB of RAM to operate, leaving you a memory-starved OS that
will perform poorly (if at all) due to heavy paging of the OS to the
swap file.
Before enabling AWE you need to do your homework on whether the extra
memory will actually do you any good. Our team manages 500+ instances
of SQL 2000 & 2005 and in all the 15+ years I've worked as a SQL DBA
the vast majority of performance issues I've seen are due to
application and/or database design. You'll be amazed at how well SQL
will run on 3 GB of RAM, especially with a well-designed system. Good
luck to you!
On Fri, 13 Oct 2006 00:03:01 -0700, Fredrik
<Fredrik@.discussions.microsoft.com> wrote:
>Hi all?
>I've tried reading about how AWE memory works but I really can't figure it
>out...
>I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
>2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
>as much as possible of the RAM for SQL Server.
>I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
>use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
>Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
>space is in my interest to use for SQL Server.
>If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
>able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
>than 4 Gbytes RAM?
>regards
>fredrik
I've tried reading about how AWE memory works but I really can't figure it
out...
I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
as much as possible of the RAM for SQL Server.
I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
space is in my interest to use for SQL Server.
If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
than 4 Gbytes RAM?
regards
fredrik> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
I don't think you need to enable AWE memory in that case
AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||If we are talking about the memory usage as measured by the SQL counter Total
Server Memory, you need to enable AWE to use more than 3GB. It is not correct
that AWE is used only for RAM that exceeds 4GB.
Linchi
"Uri Dimant" wrote:
> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> > be
> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> > more
> > than 4 Gbytes RAM?
> I don't think you need to enable AWE memory in that case
> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> > Hi all?
> >
> > I've tried reading about how AWE memory works but I really can't figure it
> > out...
> >
> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> > use
> > as much as possible of the RAM for SQL Server.
> >
> > I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> > 1
> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> > space is in my interest to use for SQL Server.
> >
> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> > be
> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> > more
> > than 4 Gbytes RAM?
> >
> > regards
> > fredrik
>
>|||This is a multi-part message in MIME format.
--=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Could you give us some support on that assertion? (It is not correct =that AWE is used only for RAM that exceeds 4GB." If my information is =incorrect, I would like to update it to reflect that which is indeed =correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 =GB."
From: =http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134=
a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message =news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
> If we are talking about the memory usage as measured by the SQL =counter Total > Server Memory, you need to enable AWE to use more than 3GB. It is not =correct > that AWE is used only for RAM that exceeds 4GB.
> > Linchi
> > "Uri Dimant" wrote:
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >> I don't think you need to enable AWE memory in that case
>> AWE memory is used only for the RAM that exceeds the base 4GB of =RAM.
>> >> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>> >> >> >> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message >> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>> > Hi all?
>> >
>> > I've tried reading about how AWE memory works but I really can't =figure it
>> > out...
>> >
>> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a =Windows
>> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be =able to >> > use
>> > as much as possible of the RAM for SQL Server.
>> >
>> > I have entered the Boot.ini with the /3GB parameter to allow SQL =Server to
>> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is =still >> > 1
>> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of =that free
>> > space is in my interest to use for SQL Server.
>> >
>> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >
>> > regards
>> > fredrik >> >> --=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Could you give us some support on that =assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." =If my information is incorrect, I would like to update it to reflect that =which is indeed correct...
I've been going by the following: ="AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4=451-8fdb-7134a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, =Ph.D.Westwood Consulting, Inc
Most good judgment comes from =experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea"
--=_NextPart_000_0518_01C6EEA8.1744A950--|||This is a multi-part message in MIME format.
--=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
Could you give us some support on that assertion? (It is not correct =that AWE is used only for RAM that exceeds 4GB." If my information is =incorrect, I would like to update it to reflect that which is indeed =correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 =GB."
From: =http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134=
a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message =news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
> If we are talking about the memory usage as measured by the SQL =counter Total > Server Memory, you need to enable AWE to use more than 3GB. It is not =correct > that AWE is used only for RAM that exceeds 4GB.
> > Linchi
> > "Uri Dimant" wrote:
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >> I don't think you need to enable AWE memory in that case
>> AWE memory is used only for the RAM that exceeds the base 4GB of =RAM.
>> >> http://support.microsoft.com/kb/274750
>> http://www.sql-server-performance.com/awe_memory.asp
>> >> >> >> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message >> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>> > Hi all?
>> >
>> > I've tried reading about how AWE memory works but I really can't =figure it
>> > out...
>> >
>> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a =Windows
>> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be =able to >> > use
>> > as much as possible of the RAM for SQL Server.
>> >
>> > I have entered the Boot.ini with the /3GB parameter to allow SQL =Server to
>> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is =still >> > 1
>> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of =that free
>> > space is in my interest to use for SQL Server.
>> >
>> > If I enable AWE memory and set the max server memory to 3,5 Gbyte =will I >> > be
>> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes =with >> > more
>> > than 4 Gbytes RAM?
>> >
>> > regards
>> > fredrik >> >> --=_NextPart_000_0518_01C6EEA8.1744A950
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Could you give us some support on that =assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." =If my information is incorrect, I would like to update it to reflect that =which is indeed correct...
I've been going by the following: ="AWE is a set of memory management extensions to the Microsoft =Win32=EF=83=A2 API that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4=451-8fdb-7134a004f94c/Adv64BitEnv.doc
-- Arnie Rowland, =Ph.D.Westwood Consulting, Inc
Most good judgment comes from =experience. Most experience comes from bad judgment. - Anonymous
"Linchi Shea"
--=_NextPart_000_0518_01C6EEA8.1744A950--|||What you need instead of all these buggy flags is to move to x64 where the
memory issue doesn't exist at all. Of course you also need to make sure you
run SQL Server 64 bit as well, not the 32 bit version on a 64 bit system.
Unfortunately very few dedicated hosts offer Windows 2003 x64.
KL
"Fredrik" <Fredrik@.discussions.microsoft.com> skrev i meddelandet
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||Here's some empirical evidence from the test scenarios in which severe memory
pressure was put on the instance with 4GB of RAM. If the following comes out
unreadable format-wise, drop me an email and I send you the charts.
Linchi
linchi_shea@.take-this-out-FIRSTml.com
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N N 500 560
1000 N N 1000 1060
1500 N N 1206 1266
2000 N N 1206 1266
2500 N N 1206 1266
3000 N N 1206 1266
3500 N N 1206 1266
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y N 500 61
1000 Y N 1000 67
1500 Y N 1500 71
2000 Y N 2000 76
2500 Y N 2500 81
3000 Y N 3000 86
3500 Y N 3500 90
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y Y 500 65
1000 Y Y 1000 70
1500 Y Y 1500 75
2000 Y Y 2000 80
2500 Y Y 2500 84
3000 Y Y 3000 89
3500 Y Y 3500 94
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N Y 500 550
1000 N Y 1000 1055
1500 N Y 1500 1561
2000 N Y 2000 2067
2500 N Y 2219 2290
3000 N Y 2219 2290
3500 N Y 2219 2290
"Arnie Rowland" wrote:
> Could you give us some support on that assertion? (It is not correct that AWE is used only for RAM that exceeds 4GB." If my information is incorrect, I would like to update it to reflect that which is indeed correct...
> I've been going by the following:
> "AWE is a set of memory management extensions to the Microsoft Win32ï?¢ API that allows applications to address memory beyond 4 GB."
> From: http://download.microsoft.com/download/9/c/c/9cc42e30-538b-4451-8fdb-7134a004f94c/Adv64BitEnv.doc
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...
> > If we are talking about the memory usage as measured by the SQL counter Total
> > Server Memory, you need to enable AWE to use more than 3GB. It is not correct
> > that AWE is used only for RAM that exceeds 4GB.
> >
> > Linchi
> >
> > "Uri Dimant" wrote:
> >
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> >> > be
> >> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> >> > more
> >> > than 4 Gbytes RAM?
> >>
> >> I don't think you need to enable AWE memory in that case
> >> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> >>
> >> http://support.microsoft.com/kb/274750
> >> http://www.sql-server-performance.com/awe_memory.asp
> >>
> >>
> >>
> >> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> >> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> >> > Hi all?
> >> >
> >> > I've tried reading about how AWE memory works but I really can't figure it
> >> > out...
> >> >
> >> > I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> >> > 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> >> > use
> >> > as much as possible of the RAM for SQL Server.
> >> >
> >> > I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> >> > use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> >> > 1
> >> > Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> >> > space is in my interest to use for SQL Server.
> >> >
> >> > If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> >> > be
> >> > able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> >> > more
> >> > than 4 Gbytes RAM?
> >> >
> >> > regards
> >> > fredrik
> >>
> >>
> >>|||Hi Fredrick,
If your server is running 4 GB of memory, then you don't want to have
SQL Server running more than 3 GB. Part of the reason for that is that
you have to leave sufficient space for the OS to operate and 1 GB of
RAN for the OS is a good amount (yeah, I know it'll run on less). The
other reason is that AWE requires 1 GB of RAM just to manage the
memory swaps that are going on. So running AWE on a 4 GB server is
likely to make things worse, not better.
So if you really think you need to be running AWE:
(1) Have at least 6 GB of memory on the server and that this is the
only instance of SQL Server running on the server.
(2) After enabling AWE and setting the /3GB and /PAE switches in the
boot.ini file, configure your max memory setting to equal your total
memory minus 1 GB (for the OS). If you don't configure the max memory
setting you leave open the possibility that SQL Server will grab all
but 128 MB of RAM to operate, leaving you a memory-starved OS that
will perform poorly (if at all) due to heavy paging of the OS to the
swap file.
Before enabling AWE you need to do your homework on whether the extra
memory will actually do you any good. Our team manages 500+ instances
of SQL 2000 & 2005 and in all the 15+ years I've worked as a SQL DBA
the vast majority of performance issues I've seen are due to
application and/or database design. You'll be amazed at how well SQL
will run on 3 GB of RAM, especially with a well-designed system. Good
luck to you!
On Fri, 13 Oct 2006 00:03:01 -0700, Fredrik
<Fredrik@.discussions.microsoft.com> wrote:
>Hi all?
>I've tried reading about how AWE memory works but I really can't figure it
>out...
>I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
>2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
>as much as possible of the RAM for SQL Server.
>I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
>use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
>Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
>space is in my interest to use for SQL Server.
>If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
>able to use that extra 512 Mbytes as well? Or is AWE only for boxes with more
>than 4 Gbytes RAM?
>regards
>fredrik
AWE Memory?
Hi all?
I've tried reading about how AWE memory works but I really can't figure it
out...
I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
as much as possible of the RAM for SQL Server.
I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
space is in my interest to use for SQL Server.
If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
able to use that extra 512 Mbytes as well? Or is AWE only for boxes with mor
e
than 4 Gbytes RAM?
regards
fredrik> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
I don't think you need to enable AWE memory in that case
AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||If we are talking about the memory usage as measured by the SQL counter Tota
l
Server Memory, you need to enable AWE to use more than 3GB. It is not correc
t
that AWE is used only for RAM that exceeds 4GB.
Linchi
"Uri Dimant" wrote:
> I don't think you need to enable AWE memory in that case
> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>
>|||Could you give us some support on that assertion? (It is not correct that AW
E is used only for RAM that exceeds 4GB." If my information is incorrect, I
would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API
that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downl...Adv64BitEnv.doc
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-420
9-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter To
tal
> Server Memory, you need to enable AWE to use more than 3GB. It is not corr
ect
> that AWE is used only for RAM that exceeds 4GB.
>
> Linchi
>
> "Uri Dimant" wrote:
>|||Could you give us some support on that assertion? (It is not correct that AW
E is used only for RAM that exceeds 4GB." If my information is incorrect, I
would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API
that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downl...Adv64BitEnv.doc
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-420
9-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter To
tal
> Server Memory, you need to enable AWE to use more than 3GB. It is not corr
ect
> that AWE is used only for RAM that exceeds 4GB.
>
> Linchi
>
> "Uri Dimant" wrote:
>|||What you need instead of all these buggy flags is to move to x64 where the
memory issue doesn't exist at all. Of course you also need to make sure you
run SQL Server 64 bit as well, not the 32 bit version on a 64 bit system.
Unfortunately very few dedicated hosts offer Windows 2003 x64.
KL
"Fredrik" <Fredrik@.discussions.microsoft.com> skrev i meddelandet
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||Here's some empirical evidence from the test scenarios in which severe memor
y
pressure was put on the instance with 4GB of RAM. If the following comes out
unreadable format-wise, drop me an email and I send you the charts.
Linchi
linchi_shea@.take-this-out-FIRSTml.com
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N N 500 560
1000 N N 1000 1060
1500 N N 1206 1266
2000 N N 1206 1266
2500 N N 1206 1266
3000 N N 1206 1266
3500 N N 1206 1266
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y N 500 61
1000 Y N 1000 67
1500 Y N 1500 71
2000 Y N 2000 76
2500 Y N 2500 81
3000 Y N 3000 86
3500 Y N 3500 90
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y Y 500 65
1000 Y Y 1000 70
1500 Y Y 1500 75
2000 Y Y 2000 80
2500 Y Y 2500 84
3000 Y Y 3000 89
3500 Y Y 3500 94
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N Y 500 550
1000 N Y 1000 1055
1500 N Y 1500 1561
2000 N Y 2000 2067
2500 N Y 2219 2290
3000 N Y 2219 2290
3500 N Y 2219 2290
"Arnie Rowland" wrote:
[vbcol=seagreen]
> Could you give us some support on that assertion? (It is not correct that
AWE is used only for RAM that exceeds 4GB." If my information is incorrect,
I would like to update it to reflect that which is indeed correct...
> I've been going by the following:
> "AWE is a set of memory management extensions to the Microsoft Win32? AP
I that allows applications to address memory beyond 4 GB."
> From: http://download.microsoft.com/downl...Adv64BitEnv.doc
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news
:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...|||Hi Fredrick,
If your server is running 4 GB of memory, then you don't want to have
SQL Server running more than 3 GB. Part of the reason for that is that
you have to leave sufficient space for the OS to operate and 1 GB of
RAN for the OS is a good amount (yeah, I know it'll run on less). The
other reason is that AWE requires 1 GB of RAM just to manage the
memory swaps that are going on. So running AWE on a 4 GB server is
likely to make things worse, not better.
So if you really think you need to be running AWE:
(1) Have at least 6 GB of memory on the server and that this is the
only instance of SQL Server running on the server.
(2) After enabling AWE and setting the /3GB and /PAE switches in the
boot.ini file, configure your max memory setting to equal your total
memory minus 1 GB (for the OS). If you don't configure the max memory
setting you leave open the possibility that SQL Server will grab all
but 128 MB of RAM to operate, leaving you a memory-starved OS that
will perform poorly (if at all) due to heavy paging of the OS to the
swap file.
Before enabling AWE you need to do your homework on whether the extra
memory will actually do you any good. Our team manages 500+ instances
of SQL 2000 & 2005 and in all the 15+ years I've worked as a SQL DBA
the vast majority of performance issues I've seen are due to
application and/or database design. You'll be amazed at how well SQL
will run on 3 GB of RAM, especially with a well-designed system. Good
luck to you!
On Fri, 13 Oct 2006 00:03:01 -0700, Fredrik
<Fredrik@.discussions.microsoft.com> wrote:
>Hi all?
>I've tried reading about how AWE memory works but I really can't figure it
>out...
>I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
>2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
>as much as possible of the RAM for SQL Server.
>I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
>use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
>Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
>space is in my interest to use for SQL Server.
>If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
>able to use that extra 512 Mbytes as well? Or is AWE only for boxes with mo
re
>than 4 Gbytes RAM?
>regards
>fredrik
I've tried reading about how AWE memory works but I really can't figure it
out...
I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
as much as possible of the RAM for SQL Server.
I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
space is in my interest to use for SQL Server.
If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
able to use that extra 512 Mbytes as well? Or is AWE only for boxes with mor
e
than 4 Gbytes RAM?
regards
fredrik> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
I don't think you need to enable AWE memory in that case
AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
http://support.microsoft.com/kb/274750
http://www.sql-server-performance.com/awe_memory.asp
"Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||If we are talking about the memory usage as measured by the SQL counter Tota
l
Server Memory, you need to enable AWE to use more than 3GB. It is not correc
t
that AWE is used only for RAM that exceeds 4GB.
Linchi
"Uri Dimant" wrote:
> I don't think you need to enable AWE memory in that case
> AWE memory is used only for the RAM that exceeds the base 4GB of RAM.
> http://support.microsoft.com/kb/274750
> http://www.sql-server-performance.com/awe_memory.asp
>
> "Fredrik" <Fredrik@.discussions.microsoft.com> wrote in message
> news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
>
>|||Could you give us some support on that assertion? (It is not correct that AW
E is used only for RAM that exceeds 4GB." If my information is incorrect, I
would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API
that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downl...Adv64BitEnv.doc
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-420
9-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter To
tal
> Server Memory, you need to enable AWE to use more than 3GB. It is not corr
ect
> that AWE is used only for RAM that exceeds 4GB.
>
> Linchi
>
> "Uri Dimant" wrote:
>|||Could you give us some support on that assertion? (It is not correct that AW
E is used only for RAM that exceeds 4GB." If my information is incorrect, I
would like to update it to reflect that which is indeed correct...
I've been going by the following:
"AWE is a set of memory management extensions to the Microsoft Win32? API
that allows applications to address memory beyond 4 GB."
From: http://download.microsoft.com/downl...Adv64BitEnv.doc
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news:1C1B6C5F-B795-420
9-B6C9-06495AE71796@.microsoft.com...[vbcol=seagreen]
> If we are talking about the memory usage as measured by the SQL counter To
tal
> Server Memory, you need to enable AWE to use more than 3GB. It is not corr
ect
> that AWE is used only for RAM that exceeds 4GB.
>
> Linchi
>
> "Uri Dimant" wrote:
>|||What you need instead of all these buggy flags is to move to x64 where the
memory issue doesn't exist at all. Of course you also need to make sure you
run SQL Server 64 bit as well, not the 32 bit version on a 64 bit system.
Unfortunately very few dedicated hosts offer Windows 2003 x64.
KL
"Fredrik" <Fredrik@.discussions.microsoft.com> skrev i meddelandet
news:14470AFA-E4E7-4D2E-A605-B3651A618913@.microsoft.com...
> Hi all?
> I've tried reading about how AWE memory works but I really can't figure it
> out...
> I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
> 2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to
> use
> as much as possible of the RAM for SQL Server.
> I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
> use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still
> 1
> Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
> space is in my interest to use for SQL Server.
> If I enable AWE memory and set the max server memory to 3,5 Gbyte will I
> be
> able to use that extra 512 Mbytes as well? Or is AWE only for boxes with
> more
> than 4 Gbytes RAM?
> regards
> fredrik|||Here's some empirical evidence from the test scenarios in which severe memor
y
pressure was put on the instance with 4GB of RAM. If the following comes out
unreadable format-wise, drop me an email and I send you the charts.
Linchi
linchi_shea@.take-this-out-FIRSTml.com
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N N 500 560
1000 N N 1000 1060
1500 N N 1206 1266
2000 N N 1206 1266
2500 N N 1206 1266
3000 N N 1206 1266
3500 N N 1206 1266
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y N 500 61
1000 Y N 1000 67
1500 Y N 1500 71
2000 Y N 2000 76
2500 Y N 2500 81
3000 Y N 3000 86
3500 Y N 3500 90
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 Y Y 500 65
1000 Y Y 1000 70
1500 Y Y 1500 75
2000 Y Y 2000 80
2500 Y Y 2500 84
3000 Y Y 3000 89
3500 Y Y 3500 94
Observed Target Sqlservr.exe
Max server AWE 3GB /Total server memory observed
memory (MB) enabled enabled memory (MB) on TaskMan (MB)
500 N Y 500 550
1000 N Y 1000 1055
1500 N Y 1500 1561
2000 N Y 2000 2067
2500 N Y 2219 2290
3000 N Y 2219 2290
3500 N Y 2219 2290
"Arnie Rowland" wrote:
[vbcol=seagreen]
> Could you give us some support on that assertion? (It is not correct that
AWE is used only for RAM that exceeds 4GB." If my information is incorrect,
I would like to update it to reflect that which is indeed correct...
> I've been going by the following:
> "AWE is a set of memory management extensions to the Microsoft Win32? AP
I that allows applications to address memory beyond 4 GB."
> From: http://download.microsoft.com/downl...Adv64BitEnv.doc
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message news
:1C1B6C5F-B795-4209-B6C9-06495AE71796@.microsoft.com...|||Hi Fredrick,
If your server is running 4 GB of memory, then you don't want to have
SQL Server running more than 3 GB. Part of the reason for that is that
you have to leave sufficient space for the OS to operate and 1 GB of
RAN for the OS is a good amount (yeah, I know it'll run on less). The
other reason is that AWE requires 1 GB of RAM just to manage the
memory swaps that are going on. So running AWE on a 4 GB server is
likely to make things worse, not better.
So if you really think you need to be running AWE:
(1) Have at least 6 GB of memory on the server and that this is the
only instance of SQL Server running on the server.
(2) After enabling AWE and setting the /3GB and /PAE switches in the
boot.ini file, configure your max memory setting to equal your total
memory minus 1 GB (for the OS). If you don't configure the max memory
setting you leave open the possibility that SQL Server will grab all
but 128 MB of RAM to operate, leaving you a memory-starved OS that
will perform poorly (if at all) due to heavy paging of the OS to the
swap file.
Before enabling AWE you need to do your homework on whether the extra
memory will actually do you any good. Our team manages 500+ instances
of SQL 2000 & 2005 and in all the 15+ years I've worked as a SQL DBA
the vast majority of performance issues I've seen are due to
application and/or database design. You'll be amazed at how well SQL
will run on 3 GB of RAM, especially with a well-designed system. Good
luck to you!
On Fri, 13 Oct 2006 00:03:01 -0700, Fredrik
<Fredrik@.discussions.microsoft.com> wrote:
>Hi all?
>I've tried reading about how AWE memory works but I really can't figure it
>out...
>I have a dedicated SQL Server 2000 SP4, Ent Edition that runs on a Windows
>2003 Advanced server. The box has 4 Gbytes RAM and I want to be able to use
>as much as possible of the RAM for SQL Server.
>I have entered the Boot.ini with the /3GB parameter to allow SQL Server to
>use 3 Gbytes of RAM instead of the default of 2 Gbyte. But there is still 1
>Gbyte "left" in the box to be used by OS. At least 512Mbytes of that free
>space is in my interest to use for SQL Server.
>If I enable AWE memory and set the max server memory to 3,5 Gbyte will I be
>able to use that extra 512 Mbytes as well? Or is AWE only for boxes with mo
re
>than 4 Gbytes RAM?
>regards
>fredrik
AWE Memory: Seeing approx. 1 Gig less than expected
I am runnning a dedicated SQL Server 2005 Standard edition server on Win 200
3,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, bu
t
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB i
n
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1
3,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, bu
t
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB i
n
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200610/1
AWE Memory: Seeing approx. 1 Gig less than expected
I am runnning a dedicated SQL Server 2005 Standard edition server on Win 2003,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
If I recall correctly, AWE consumes about 1GB of memory as overhead.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:[vbcol=seagreen]
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>[quoted text clipped - 9 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via droptable.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200610/1
>
|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:[vbcol=seagreen]
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>[quoted text clipped - 20 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200610/1
AWE Memory: Seeing approx. 1 Gig less than expected
I am runnning a dedicated SQL Server 2005 Standard edition server on Win 2003,
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
>>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
>[quoted text clipped - 20 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
with 16 GB RAM.
I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
I have /3GB /PAE set in the boot.ini.
When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
specified.
Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1If I recall correctly, AWE consumes about 1GB of memory as overhead.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a8999d3983c@.uwe...
>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>2003,
> with 16 GB RAM.
> I have AWE enabled, with a Max Server Memory of 14336 (14 GB).
> I have /3GB /PAE set in the boot.ini.
> When I run SQLServer:Memory Manager, Target Memory (KB) in Perfmon, I only
> see 13722592 KB (or 13400.96875 MB, 13.086 GB) being used out of the 14 GB
> specified.
> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||Thanks Arnie. I do not dispute that, but it does make me scratch my head.
On another dedicated SQL Server, identical to the current one I am building,
except this other one has only 8 GB of RAM, when I set the Max Server Memory
to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB to
itself, then I would expect to only see 5 GB being used in Target Memory, but
no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes me
feel like I am being cheated out of approximately 1 GB on my 16 GB server,
since I have 14 GB specified in Max Server Memory and am only seeing 13 GB in
Target Memory.
Arnie Rowland wrote:
>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1|||I really don't recall if that 1GB overhead is in addition to the AWE
allocation, or if it is part of the AWE allocation. (I always thought that
it was outside of the AWE allocation.)
So, back to your situation.
Is it possible that there is some other usage on the box that is grabbing
memory from the OS before AWE can get it's share (thereby leaving only 13GB
for AWE)?
Another instance of SQL Server with /3GB switch?
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"cbrichards via SQLMonster.com" <u3288@.uwe> wrote in message
news:67a9b4e454ccc@.uwe...
> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
> On another dedicated SQL Server, identical to the current one I am
> building,
> except this other one has only 8 GB of RAM, when I set the Max Server
> Memory
> to 6144 (6 GB), I see all 6144 in Target Memory. If SQL Server keeps 1 GB
> to
> itself, then I would expect to only see 5 GB being used in Target Memory,
> but
> no, I am seeing all 6 GB on my 8 GB machine. Just makes me wonder...makes
> me
> feel like I am being cheated out of approximately 1 GB on my 16 GB server,
> since I have 14 GB specified in Max Server Memory and am only seeing 13 GB
> in
> Target Memory.
> Arnie Rowland wrote:
>>If I recall correctly, AWE consumes about 1GB of memory as overhead.
>>I am runnning a dedicated SQL Server 2005 Standard edition server on Win
>>2003,
>>[quoted text clipped - 9 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
>|||I suspect that is the case (some other usage on the box is grabbing memory),
but it is not another instance. I am still investigating.
Arnie Rowland wrote:
>I really don't recall if that 1GB overhead is in addition to the AWE
>allocation, or if it is part of the AWE allocation. (I always thought that
>it was outside of the AWE allocation.)
>So, back to your situation.
>Is it possible that there is some other usage on the box that is grabbing
>memory from the OS before AWE can get it's share (thereby leaving only 13GB
>for AWE)?
>Another instance of SQL Server with /3GB switch?
>> Thanks Arnie. I do not dispute that, but it does make me scratch my head.
>[quoted text clipped - 20 lines]
>> Is this normal, or am I being robbed of a Gig of memory somewhere?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200610/1
Subscribe to:
Posts (Atom)