AWE and SQL Server 2005 Standart edition

We will be running SQL Server 2005 Standart edition on Windows 2003
Enterprise Server.
My questions are about memory beyound 2GB and how to configure it
properly.
We have 4GB of RAM on db servers, in order to use them and
potentionally go to 8GB do I need any/all of the following:
1. Enable AWE on SQL Server? Will it work for Standart edition or I
need SQL SErver 2005 Enterprise?
2. Use /3GB switch?
3. Use /pae switch?
Can somebody give me clear answers for these questions,
RegardsFortunately with SQL 2005 Standard, you can use more than 2gb of ram,
something that is not true for SQL 2000.
You would need both switches to maximize the amount of memory used.
However, I would very *highly* recommend using the 64-bit version of Windows
and SQL. AWE has a performance hit that a 64-bit program does not have.
"Mike" <mguissine@.hotmail.com> wrote in message
news:1141755306.297245.266230@.p10g2000cwp.googlegroups.com...
> We will be running SQL Server 2005 Standart edition on Windows 2003
> Enterprise Server.
> My questions are about memory beyound 2GB and how to configure it
> properly.
> We have 4GB of RAM on db servers, in order to use them and
> potentionally go to 8GB do I need any/all of the following:
> 1. Enable AWE on SQL Server? Will it work for Standart edition or I
> need SQL SErver 2005 Enterprise?
> 2. Use /3GB switch?
> 3. Use /pae switch?
> Can somebody give me clear answers for these questions,
> Regards
>|||1. Enable AWE on SQL Server? Will it work for Standart edition or I
need SQL SErver 2005 Enterprise?
- I believe SQL Server 2005 Standard Edition is not AWE-enabled and cannot
take advantage of RAM in a server over 4GB. However, I have not been able t
o
confirm this.
2. Use /3GB switch?
- If you have 4GB of memory available, then you'd want to set the /3GB switc
h.
- If you go to 8GB of RAM, then you'll want to enable /3GB and /PAE
3. Use /pae switch?
- Only if you go to 8GB of RAM.
You'll also want to check with the admin of your server to see if the /PAE i
s
enabled by default since the newer servers may default it to 'on'. If
Here are a couple useful links on the topic...
- http://support.microsoft.com/?kbid=283037
- http://www.sql-server-performance.c...server/200603/1|||Michael D'Angelo wrote:

>However, I would very *highly* recommend using the 64-bit version of Window
s
>and SQL. AWE has a performance hit that a 64-bit program does not have.
>
Agreed - this would be the most advantagous route to go. AWE only extends
SQL server's memory for data pages only, while all other SQL server areas ar
e
stuck at the 2GB limit. Going to 64bit removes the 2GB limitation for all
SQL Server memory structures.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200603/1|||Thanks to everybody to quick replies.
I just would like to summarize it:
Setup: SQL Server 2005 Standart, Windows 2003 Enterprise, 32 Bit both,
4 GB Physical RAM
1./3GB switch enabled
2.AWE disabled because not used anyway
3./PAE disabled
Setup: SQL Server 2005 Standart, Windows 2003 Enterprise, 32 Bit both,
8 GB Physical RAM
1./3GB switch enabled
2.AWE enabled
3./PAE enabled
Could someone firmly confirm that this is correct.
Do I need anything else?
Regards,
Mike|||Looks fine, but how much memory are you giving the SQL instance on the serve
r
with 8GB of RAM? The rule of thumb I follow is to leave a 1GB for the OS an
d
1GB for the AWE mapping table.
Message posted via http://www.droptable.com|||I would like to give SQL as much as possible.
Would /3GB switch only allocate 3GB for SQL? What should I do to give
SQL 7GB out of 8GB available?
Mike