Right step to enable AWE on Cluster Server

We have a SQL Cluster box, passive/active. Recently, we plan to upgrade
memory to 8G and enable AWE. What's the right procedure to enable AWE? Can I
just run following scripts against virtual sever, and all change will be
populate the each node
SP_CONFIGURE 'show advanced options', 1
RECONFIGURE
GO
SP_CONFIGURE 'awe enabled', 1
RECONFIGURE
GO
SP_CONFIGURE 'max server memory', 7144
RECONFIGURE
GO
OR since it is a cluster server, I need to run scripts against each
instance. Any suggestion?
You have to put the /PAE switch in the boot.ini file on each host node so
each OS can address the extra memory.
You only need to change the SQL instance once, since it is an internal
configuration to the virtual server. You will also need to stop and restart
the SQL server to get the memory adjustments to "take". AWE memory is
allocated at service startup so by using AWE, you lose dynamic memory
allocation, even if it is enabled.
Be sure and watch your system paging to see if you have over-allocated
memory to SQL.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LanLan" <LanLan@.discussions.microsoft.com> wrote in message
news:6A9157D0-DB72-4803-B494-A71C090BF348@.microsoft.com...
> We have a SQL Cluster box, passive/active. Recently, we plan to upgrade
> memory to 8G and enable AWE. What's the right procedure to enable AWE? Can
> I
> just run following scripts against virtual sever, and all change will be
> populate the each node
> SP_CONFIGURE 'show advanced options', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'awe enabled', 1
> RECONFIGURE
> GO
> SP_CONFIGURE 'max server memory', 7144
> RECONFIGURE
> GO
> OR since it is a cluster server, I need to run scripts against each
> instance. Any suggestion?
|||Thanks Geoff. This is what I want to know! Run the script against the virtual
sever will do all the job !
Lan
"Geoff N. Hiten" wrote:

> You have to put the /PAE switch in the boot.ini file on each host node so
> each OS can address the extra memory.
> You only need to change the SQL instance once, since it is an internal
> configuration to the virtual server. You will also need to stop and restart
> the SQL server to get the memory adjustments to "take". AWE memory is
> allocated at service startup so by using AWE, you lose dynamic memory
> allocation, even if it is enabled.
> Be sure and watch your system paging to see if you have over-allocated
> memory to SQL.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "LanLan" <LanLan@.discussions.microsoft.com> wrote in message
> news:6A9157D0-DB72-4803-B494-A71C090BF348@.microsoft.com...
>
>
|||To take this one step further since it is an incredibly common
misconception.
Administering a SQL Server failover cluster instance and administering a
standalone SQL Server instance are the same. If it is a SQL Server only
operation, there are ZERO differences between a failover cluster instance
and a standalone instance. A SQL Server is a SQL Server is a SQL Server.
Only when you have to deal with things at a base OS level, are there minor
differences.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"LanLan" <LanLan@.discussions.microsoft.com> wrote in message
news:C6671447-2FBE-420E-99B0-6C4275B97D28@.microsoft.com...[vbcol=seagreen]
> Thanks Geoff. This is what I want to know! Run the script against the
> virtual
> sever will do all the job !
> Lan
> "Geoff N. Hiten" wrote: