![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello! We will be installing SQL Server 2008 64 bit EE on Windows 2008 EE (Active/Active cluster). I would like to confirm following settings considering we will have 32GB of memory on each node: 1. No need to enable AWE. 2. No need to set 'Lock Pages In Memory'. 3. Cap Min and Max Memory usage on each instance (leave memory not only to OS, but also to the second instance in case of failover). I am not exactly sure how to cap memory. Would it be possible to make memory Max adjustment when failover occurs? Otherwise, we might be wasting memory. 4. No need to set /3GB in boot.ini. Any other configurational setting to consider? Thank you in advance, Igor |
#3
| |||
| |||
|
|
1. AWE is completely ignored in 64-bit SQL. 2. Maybe. There are some differences, but not enough to matter. 3) SQL Server has min and max server memory settings internally. You can set them via Policy, SSMS, or Scripts. You can do some custom failover scripts, but that is fairly complex. 4) /3GB is ignored in 64-bit Operating Systems. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Igor Marchenko" <IgorMarchenko (AT) discussions (DOT) microsoft.com> wrote in message news:726148C9-FC7D-4746-9EA0-213FEF5A84C8 (AT) microsoft (DOT) com... Hello! We will be installing SQL Server 2008 64 bit EE on Windows 2008 EE (Active/Active cluster). I would like to confirm following settings considering we will have 32GB of memory on each node: 1. No need to enable AWE. 2. No need to set 'Lock Pages In Memory'. 3. Cap Min and Max Memory usage on each instance (leave memory not only to OS, but also to the second instance in case of failover). I am not exactly sure how to cap memory. Would it be possible to make memory Max adjustment when failover occurs? Otherwise, we might be wasting memory. 4. No need to set /3GB in boot.ini. Any other configurational setting to consider? Thank you in advance, Igor |
#4
| |||
| |||
|
|
Geoff Can you please clarify why NO (maybe)need to enable set 'Lock Pages In Memory'.? Igor We have a clustered two nodes config (Active-Active) as you refer. Each node has 16gb RAM We configured MAX memory to 8gb so on case it failed over there is enough memory to start working till the 'bad' node wikk be fixed Geoff , do you think the above is acceptable config? "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:O03sxaLaKHA.4312 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 1. AWE is completely ignored in 64-bit SQL. 2. Maybe. There are some differences, but not enough to matter. 3) SQL Server has min and max server memory settings internally. You can set them via Policy, SSMS, or Scripts. You can do some custom failover scripts, but that is fairly complex. 4) /3GB is ignored in 64-bit Operating Systems. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Igor Marchenko" <IgorMarchenko (AT) discussions (DOT) microsoft.com> wrote in message news:726148C9-FC7D-4746-9EA0-213FEF5A84C8 (AT) microsoft (DOT) com... Hello! We will be installing SQL Server 2008 64 bit EE on Windows 2008 EE (Active/Active cluster). I would like to confirm following settings considering we will have 32GB of memory on each node: 1. No need to enable AWE. 2. No need to set 'Lock Pages In Memory'. 3. Cap Min and Max Memory usage on each instance (leave memory not only to OS, but also to the second instance in case of failover). I am not exactly sure how to cap memory. Would it be possible to make memory Max adjustment when failover occurs? Otherwise, we might be wasting memory. 4. No need to set /3GB in boot.ini. Any other configurational setting to consider? Thank you in advance, Igor |
#5
| |||
| |||
|
|
I will let Bob Ward answer that. *He does it a lot better than I do. http://blogs.msdn.com/psssql/archive...h-locked-pages... -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Uri Dimant" <u... (AT) iscar (DOT) co.il> wrote in message news:eyRSRdPaKHA.3992 (AT) TK2MSFTNGP04 (DOT) phx.gbl... Geoff Can *you please clarify why NO (maybe)need to enable set 'Lock Pages In Memory'.? Igor We have a clustered *two nodes config (Active-Active) as * you refer. Each node has 16gb RAM We configured MAX memory to 8gb so on case it failed over there is enough memory to start working till *the 'bad' node wikk be fixed Geoff , do you think *the above is acceptable config? "Geoff N. Hiten" <SQLCrafts... (AT) gmail (DOT) com> wrote in message news:O03sxaLaKHA.4312 (AT) TK2MSFTNGP04 (DOT) phx.gbl... 1. *AWE is completely ignored in 64-bit SQL. 2. *Maybe. *There are some differences, but not enough to matter. 3) SQL Server has min and max server memory settings internally. *You can set them via Policy, SSMS, or Scripts. *You can do some custom failover scripts, but that is fairly complex. 4) /3GB is ignored in 64-bit Operating Systems. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Igor Marchenko" <IgorMarche... (AT) discussions (DOT) microsoft.com> wrote in messagenews:726148C9-FC7D-4746-9EA0-213FEF5A84C8 (AT) microsoft (DOT) com... Hello! * We will be installing SQL Server 2008 64 bit EE on Windows 2008 EE (Active/Active cluster). I would like to confirm following settings considering we will have 32GB of memory on each node: 1. No need to enable AWE. 2. No need to set 'Lock Pages In Memory'. 3. Cap Min and Max Memory usage on each instance (leave memory not only to OS, but also to the second instance in case of failover). I am not exactly sure how to cap memory. Would it be possible to make memory Max adjustment when failover occurs? Otherwise, we might be wasting memory. 4. No need to set /3GB in boot.ini. Any other configurational setting to consider? Thank you in advance, Igor- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |