We have a 32 bit SQL 2005 active-active clusterd server, with 8GB RAM in 
each node. What should we do with boot.ini?

1 /3GB
2 /PAE
3 /3GB /PAE

You sepcify /3GB if you want the SQL process to be able to use 3GB virtual 
address space. On most modern servers (at least the ones from tier-1 system 
suppliers), if you are running Win2K3 Enterrprise, you don't need to specify 
/PAE for the OS to see 8GB of physical memory. In fact, if the OS can see 8GB 
of RAM, you don't need to specify /PAE.

Linchi

"NT007" wrote:

> We have a 32 bit SQL 2005 active-active clusterd server, with 8GB RAM in 
> each node. What should we do with boot.ini?
> 
> 1 /3GB
> 2 /PAE
> 3 /3GB /PAE 
> 
> 
>

NT007
In addition on Linchi's comment , do  you consider to set MAX memory for SQL 
Server?

http://support.microsoft.com/kb/274750

"NT007"  wrote in message 
news:%23tpCVux0IHA.416@TK2MSFTNGP04.phx.gbl...
> We have a 32 bit SQL 2005 active-active clusterd server, with 8GB RAM in 
> each node. What should we do with boot.ini?
>
> 1 /3GB
> 2 /PAE
> 3 /3GB /PAE
>

On 21 Giu, 00:07, Linchi Shea 
wrote:
> .....if you are running Win2K3 Enterrprise, you don't need to specify
> /PAE for the OS to see 8GB of physical memory. In fact, if the OS can see 8GB
> of RAM, you don't need to specify /PAE.


To activate AWE on 32bit system you need to add /3GB boot parameter
and /PAE switch to the boot.ini file and reboot the server. This is
required to enable operating system support of more than 4 GB of
physical memory.
AWE behaves differently depending on the underlying operating system
"only" because win2003 os supports dynamic allocation of AWE-mapped
memory.

Regards
Riccardo

On 22 Giu, 07:22, "Uri Dimant"  wrote:
> In addition on Linchi's comment , do  you consider to set MAX memory for SQL
> Server?

this setting is recommended on a win2000 os only.

Regards
Riccardo

You do not need /3GB to activate AWE.

-- 
   Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON   Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Riccardone"  wrote in message 
news:53f00fb9-8c39-4e83-a4ab-76ee79c42897@m73g2000hsh.googlegroups.com...
On 21 Giu, 00:07, Linchi Shea 
wrote:
> .....if you are running Win2K3 Enterrprise, you don't need to specify
> /PAE for the OS to see 8GB of physical memory. In fact, if the OS can see 
> 8GB
> of RAM, you don't need to specify /PAE.


To activate AWE on 32bit system you need to add /3GB boot parameter
and /PAE switch to the boot.ini file and reboot the server. This is
required to enable operating system support of more than 4 GB of
physical memory.
AWE behaves differently depending on the underlying operating system
"only" because win2003 os supports dynamic allocation of AWE-mapped
memory.

Regards
Riccardo

Assuming this is Win2003, you should also consider adding a value with the
/userva switch. We found that the system will be much more stable if you
give just a bit of the 3GB back to the OS. Think of it as /2.9GB.

"Linchi Shea"  wrote in message 
news:825E7E78-5E18-454A-9A5C-B8633F37BE97@microsoft.com...
> You sepcify /3GB if you want the SQL process to be able to use 3GB virtual
> address space. On most modern servers (at least the ones from tier-1 
> system
> suppliers), if you are running Win2K3 Enterrprise, you don't need to 
> specify
> /PAE for the OS to see 8GB of physical memory. In fact, if the OS can see 
> 8GB
> of RAM, you don't need to specify /PAE.
>
> Linchi
>
> "NT007" wrote:
>
>> We have a 32 bit SQL 2005 active-active clusterd server, with 8GB RAM in
>> each node. What should we do with boot.ini?
>>
>> 1 /3GB
>> 2 /PAE
>> 3 /3GB /PAE
>>
>>
>>

No
It applies to Microsoft SQL Server 2005 Enterprise Edition as well. See at 
the bottom of the article




"Riccardone"  wrote in message 
news:20250cb1-d5be-416e-a33c-09be39dcff65@x41g2000hsb.googlegroups.com...
On 22 Giu, 07:22, "Uri Dimant"  wrote:
> In addition on Linchi's comment , do you consider to set MAX memory for 
> SQL
> Server?

this setting is recommended on a win2000 os only.

Regards
Riccardo

cut and paste from one of million msdn articles about this recommended
setting for "windows 2000" (and not sql server enterprise or other sql
server version)
http://msdn.microsoft.com/en-us/library/ms190731.aspx
----------------------------------------------------
For Windows 2000, unless a value has been specified for max server
memory, SQL Server reserves almost all available memory during
startup, leaving 128 megabytes (MB) or less physical memory for other
applications. (When AWE is not enabled the amount of physical memory
left for other applications can be controlled by max server memory.)
For Windows Server 2003, the AWE mapped memory management is dynamic,
so that only a small portion of the total available physical memory is
allocated during startup.
----------------------------------------------------

Regards
Riccardo di Nuzzo

On 23 Giu, 07:12, "Uri Dimant"  wrote:
> No
> It applies to Microsoft SQL Server 2005 Enterprise Edition as well. See at
> the bottom of the article
>
> "Riccardone"  wrote in message
>
> news:20250cb1-d5be-416e-a33c-09be39dcff65@x41g2000hsb.googlegroups.com...
> On 22 Giu, 07:22, "Uri Dimant"  wrote:
>
> > In addition on Linchi's comment , do you consider to set MAX memory for
> > SQL
> > Server?
>
> this setting is recommended on a win2000 os only.
>
> Regards
> Riccardo

You are right. From an msdn article, the procedure to configure the
AWE enabled option:

http://msdn.microsoft.com/en-us/library/ms190961.aspx
------------------------------------------------
In Object Explorer, right-click a server and select Properties.
Click the Memory node.
Under Server memory options, select Use AWE to allocate memory.

To support more than 4 GB of physical memory on 32-bit operating
systems, you must add the /pae parameter to the boot.ini file and
reboot the computer. See your Windows documentation for details.
------------------------------------------------

or with sp_configure system stored procedure:

sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO

Regards
Riccardo di Nuzzo


On 23 Giu, 01:45, "Tom Moreau"  wrote:
> You do not need /3GB to activate AWE.
>
> --
>    Tom
>
> ----------------------------------------------------
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON   Canadahttps://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "Riccardone"  wrote in message
>
> news:53f00fb9-8c39-4e83-a4ab-76ee79c42897@m73g2000hsh.googlegroups.com...
> On 21 Giu, 00:07, Linchi Shea 
> wrote:
>
> > .....if you are running Win2K3 Enterrprise, you don't need to specify
> > /PAE for the OS to see 8GB of physical memory. In fact, if the OS can see
> > 8GB
> > of RAM, you don't need to specify /PAE.
>
> To activate AWE on 32bit system you need to add /3GB boot parameter
> and /PAE switch to the boot.ini file and reboot the server. This is
> required to enable operating system support of more than 4 GB of
> physical memory.
> AWE behaves differently depending on the underlying operating system
> "only" because win2003 os supports dynamic allocation of AWE-mapped
> memory.
>
> Regards
> Riccardo

'max server memory' is a SQL Server configuration setting regardless of what 
OS the SQL instance may be running on. It's generally a good idea to cap the 
SQL Server buffer pool size (and set the min server memory) so that you avoid 
all this give-and-take of memory at the OS level.

Linchi

"Riccardone" wrote:

> cut and paste from one of million msdn articles about this recommended
> setting for "windows 2000" (and not sql server enterprise or other sql
> server version)
> http://msdn.microsoft.com/en-us/library/ms190731.aspx
> ----------------------------------------------------
> For Windows 2000, unless a value has been specified for max server
> memory, SQL Server reserves almost all available memory during
> startup, leaving 128 megabytes (MB) or less physical memory for other
> applications. (When AWE is not enabled the amount of physical memory
> left for other applications can be controlled by max server memory.)
> For Windows Server 2003, the AWE mapped memory management is dynamic,
> so that only a small portion of the total available physical memory is
> allocated during startup.
> ----------------------------------------------------
> 
> Regards
> Riccardo di Nuzzo
> 
> On 23 Giu, 07:12, "Uri Dimant"  wrote:
> > No
> > It applies to Microsoft SQL Server 2005 Enterprise Edition as well. See at
> > the bottom of the article
> >
> > "Riccardone"  wrote in message
> >
> > news:20250cb1-d5be-416e-a33c-09be39dcff65@x41g2000hsb.googlegroups.com...
> > On 22 Giu, 07:22, "Uri Dimant"  wrote:
> >
> > > In addition on Linchi's comment , do you consider to set MAX memory for
> > > SQL
> > > Server?
> >
> > this setting is recommended on a win2000 os only.
> >
> > Regards
> > Riccardo
> 
>

Ok, I try to explain in other words:
'max server memory' is cleary an sql option
On win2000 server Microsoft "strongly recommend" to set max server
memory option always to optimize AWE enabled system.
On win2003 server, setting the min and max server memory options are
"only" a best pratice when there are more than one instance on a node
or in case of a fail over occours.

regards
Riccardo di Nuzzo


On 24 Giu, 18:05, Linchi Shea 
wrote:
> 'max server memory' is a SQL Server configuration setting regardless of what
> OS the SQL instance may be running on. It's generally a good idea to cap the
> SQL Server buffer pool size (and set the min server memory) so that you avoid
> all this give-and-take of memory at the OS level.
>
> Linchi
>
>
>
> "Riccardone" wrote:
> > cut and paste from one of million msdn articles about this recommended
> > setting for "windows 2000" (and not sql server enterprise or other sql
> > server version)
> >http://msdn.microsoft.com/en-us/library/ms190731.aspx
> > ----------------------------------------------------
> > For Windows 2000, unless a value has been specified for max server
> > memory, SQL Server reserves almost all available memory during
> > startup, leaving 128 megabytes (MB) or less physical memory for other
> > applications. (When AWE is not enabled the amount of physical memory
> > left for other applications can be controlled by max server memory.)
> > For Windows Server 2003, the AWE mapped memory management is dynamic,
> > so that only a small portion of the total available physical memory is
> > allocated during startup.
> > ----------------------------------------------------
>
> > Regards
> > Riccardo di Nuzzo
>
> > On 23 Giu, 07:12, "Uri Dimant"  wrote:
> > > No
> > > It applies to Microsoft SQL Server 2005 Enterprise Edition as well. See at
> > > the bottom of the article
>
> > > "Riccardone"  wrote in message
>
> > >news:20250cb1-d5be-416e-a33c-09be39dcff65@x41g2000hsb.googlegroups.com...
> > > On 22 Giu, 07:22, "Uri Dimant"  wrote:
>
> > > > In addition on Linchi's comment , do you consider to set MAX memory for
> > > > SQL
> > > > Server?
>
> > > this setting is recommended on a win2000 os only.
>
> > > Regards
> > > Riccardo- Nascondi testo citato
>
> - Mostra testo citato

Why is it not a best practice when there is only one SQL instance?

Linchi

"Riccardone" wrote:

> Ok, I try to explain in other words:
> 'max server memory' is cleary an sql option
> On win2000 server Microsoft "strongly recommend" to set max server
> memory option always to optimize AWE enabled system.
> On win2003 server, setting the min and max server memory options are
> "only" a best pratice when there are more than one instance on a node
> or in case of a fail over occours.
> 
> regards
> Riccardo di Nuzzo
> 
> 
> On 24 Giu, 18:05, Linchi Shea 
> wrote:
> > 'max server memory' is a SQL Server configuration setting regardless of what
> > OS the SQL instance may be running on. It's generally a good idea to cap the
> > SQL Server buffer pool size (and set the min server memory) so that you avoid
> > all this give-and-take of memory at the OS level.
> >
> > Linchi
> >
> >
> >
> > "Riccardone" wrote:
> > > cut and paste from one of million msdn articles about this recommended
> > > setting for "windows 2000" (and not sql server enterprise or other sql
> > > server version)
> > >http://msdn.microsoft.com/en-us/library/ms190731.aspx
> > > ----------------------------------------------------
> > > For Windows 2000, unless a value has been specified for max server
> > > memory, SQL Server reserves almost all available memory during
> > > startup, leaving 128 megabytes (MB) or less physical memory for other
> > > applications. (When AWE is not enabled the amount of physical memory
> > > left for other applications can be controlled by max server memory.)
> > > For Windows Server 2003, the AWE mapped memory management is dynamic,
> > > so that only a small portion of the total available physical memory is
> > > allocated during startup.
> > > ----------------------------------------------------
> >
> > > Regards
> > > Riccardo di Nuzzo
> >
> > > On 23 Giu, 07:12, "Uri Dimant"  wrote:
> > > > No
> > > > It applies to Microsoft SQL Server 2005 Enterprise Edition as well. See at
> > > > the bottom of the article
> >
> > > > "Riccardone"  wrote in message
> >
> > > >news:20250cb1-d5be-416e-a33c-09be39dcff65@x41g2000hsb.googlegroups.com...
> > > > On 22 Giu, 07:22, "Uri Dimant"  wrote:
> >
> > > > > In addition on Linchi's comment , do you consider to set MAX memory for
> > > > > SQL
> > > > > Server?
> >
> > > > this setting is recommended on a win2000 os only.
> >
> > > > Regards
> > > > Riccardo- Nascondi testo citato
> >
> > - Mostra testo citato
> 
>

Dynamic memory management is a good choice in this case but this is
off topic.

Riccardo di Nuzzo

On 26 Giu, 15:52, Linchi Shea 
wrote:
> Why is it not a best practice when there is only one SQL instance?
>
> Linchi
>
>
>
> "Riccardone" wrote:
> > Ok, I try to explain in other words:
> > 'max server memory' is cleary an sql option
> > On win2000 server Microsoft "strongly recommend" to set max server
> > memory option always to optimize AWE enabled system.
> > On win2003 server, setting the min and max server memory options are
> > "only" a best pratice when there are more than one instance on a node
> > or in case of a fail over occours.
>
> > regards
> > Riccardo di Nuzzo
>
> > On 24 Giu, 18:05, Linchi Shea 
> > wrote:
> > > 'max server memory' is a SQL Server configuration setting regardless of what
> > > OS the SQL instance may be running on. It's generally a good idea to cap the
> > > SQL Server buffer pool size (and set the min server memory) so that you avoid
> > > all this give-and-take of memory at the OS level.
>
> > > Linchi
>
> > > "Riccardone" wrote:
> > > > cut and paste from one of million msdn articles about this recommended
> > > > setting for "windows 2000" (and not sql server enterprise or other sql
> > > > server version)
> > > >http://msdn.microsoft.com/en-us/library/ms190731.aspx
> > > > ----------------------------------------------------
> > > > For Windows 2000, unless a value has been specified for max server
> > > > memory, SQL Server reserves almost all available memory during
> > > > startup, leaving 128 megabytes (MB) or less physical memory for other
> > > > applications. (When AWE is not enabled the amount of physical memory
> > > > left for other applications can be controlled by max server memory.)
> > > > For Windows Server 2003, the AWE mapped memory management is dynamic,
> > > > so that only a small portion of the total available physical memory is
> > > > allocated during startup.
> > > > ----------------------------------------------------
>
> > > > Regards
> > > > Riccardo di Nuzzo
>
> > > > On 23 Giu, 07:12, "Uri Dimant"  wrote:
> > > > > No
> > > > > It applies to Microsoft SQL Server 2005 Enterprise Edition as well. See at
> > > > > the bottom of the article
>
> > > > > "Riccardone"  wrote in message
>
> > > > >news:20250cb1-d5be-416e-a33c-09be39dcff65@x41g2000hsb.googlegroups.com...
> > > > > On 22 Giu, 07:22, "Uri Dimant"  wrote:
>
> > > > > > In addition on Linchi's comment , do you consider to set MAX memory for
> > > > > > SQL
> > > > > > Server?
>
> > > > > this setting is recommended on a win2000 os only.
>
> > > > > Regards
> > > > > Riccardo- Nascondi testo citato
>
> > > - Mostra testo citato- Nascondi testo citato
>
> - Mostra testo citato