Re: 16GB RAM AWE Failover vs. Stop/Start VirtInst w/3gb /pae ini

[Database Administrator]

Just a hint: if you are using AWE, try to avoid the use of the /3Gb flag.
This can push your server in big trouble if you have much RAM used on the
machine.

"Lenny" a écrit dans le message de news:
4_866268_8d71c05d06d0903566b23849870...dbforumz .com...
>I have installed 16 gigs of ram in 2 servers that each house a virtual
> server\instance of SQL.
>
> I have the /3gb sw and the /pae switch in the boot.ini and before
> failing over the group i ran the following script:
>
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
>
>
> Instead of stopping sql server, I failed it over from node a to node
> b. This took a little while but worked fine.
>
> I proceeded to add the memory allocation to use 6 gigs on the other
> node -b - and failed it over to node a.
>
>
> After getting recovery complete for all my databases, I attempted to
> move my first instance back to node a - which failed and then on its
> own moved back to node b.
>
> Please let me know if anyone has ran into this problem before and if I
> should change something etc.
> Thanks,
> Lenny
>
> --
> Posted using the http://www.dbforumz.com interface, at author's request
> Articles individually checked for conformance to usenet standards
> Topic URL:
> http://www.dbforumz.com/Clustering-1...ict250254.html
> Visit Topic URL to contact author (reg. req'd). Report abuse:
> http://www.dbforumz.com/eform.php?p=866268

[Database Administrator]

Correct. The breakover point seems to be around 12GB of physical RAM. Up
to that level, you can safely use /AWE and /3GB together. If you have more
memory than that, do not use /3GB.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP

"Pascal Deliot" wrote in message
news:ulCktyguFHA.3252@TK2MSFTNGP10.phx.gbl...
> Just a hint: if you are using AWE, try to avoid the use of the /3Gb flag.
> This can push your server in big trouble if you have much RAM used on the
> machine.
>
> "Lenny" a écrit dans le message de news:
> 4_866268_8d71c05d06d0903566b23849870...dbforumz .com...
>>I have installed 16 gigs of ram in 2 servers that each house a virtual
>> server\instance of SQL.
>>
>> I have the /3gb sw and the /pae switch in the boot.ini and before
>> failing over the group i ran the following script:
>>
>> sp_configure 'show advanced options', 1
>> RECONFIGURE
>> GO
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>> GO
>> sp_configure 'max server memory', 6144
>> RECONFIGURE
>> GO
>>
>>
>> Instead of stopping sql server, I failed it over from node a to node
>> b. This took a little while but worked fine.
>>
>> I proceeded to add the memory allocation to use 6 gigs on the other
>> node -b - and failed it over to node a.
>>
>>
>> After getting recovery complete for all my databases, I attempted to
>> move my first instance back to node a - which failed and then on its
>> own moved back to node b.
>>
>> Please let me know if anyone has ran into this problem before and if I
>> should change something etc.
>> Thanks,
>> Lenny
>>
>> --
>> Posted using the http://www.dbforumz.com interface, at author's request
>> Articles individually checked for conformance to usenet standards
>> Topic URL:
>> http://www.dbforumz.com/Clustering-1...ict250254.html
>> Visit Topic URL to contact author (reg. req'd). Report abuse:
>> http://www.dbforumz.com/eform.php?p=866268
>
>