 | |
Failover Nodes - Varying Hardware
microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Failover Nodes - Varying Hardware -
04-08-2009
, 11:36 AM
#2
| |||
| |||
|
|
We are replacing one SQL 2000 cluster node. The existing two nodes have 4GB with the /3GB switch - no PAE. AWE is not enabled. The new node will have 15.2 GB with PAE. Should I still use the /3GB switch even though there is more than 8 GB? Thanks, Randy |
#3
| |||
| |||
|
|
To answer your question, /3GB should stop at no higher than 12 GB. As for replacing cluster nodes with asymmetrical hardware, that is not supported on Windows 2000/2003. There are very good technical reasons why matched HCL-listed hardware is required. Then again, with SQL 2000, you are pretty much out of support anyway. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Randy" <Randy (AT) discussions (DOT) microsoft.com> wrote in message news:CE912B74-5E2C-4EDF-A8CE-953B2767A69C (AT) microsoft (DOT) com... We are replacing one SQL 2000 cluster node. The existing two nodes have 4GB with the /3GB switch - no PAE. AWE is not enabled. The new node will have 15.2 GB with PAE. Should I still use the /3GB switch even though there is more than 8 GB? Thanks, Randy |
#4
| |||
| |||
|
|
Thanks. I will not use the switch and suggest we replace both nodes, not just the bad one. Unfortunately, the active node had been patched and requires a reboot. I can't add a new nodes until it's rebooted. Looks like we are going to be down. "Geoff N. Hiten" wrote: To answer your question, /3GB should stop at no higher than 12 GB. As for replacing cluster nodes with asymmetrical hardware, that is not supported on Windows 2000/2003. There are very good technical reasons why matched HCL-listed hardware is required. Then again, with SQL 2000, you are pretty much out of support anyway. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Randy" <Randy (AT) discussions (DOT) microsoft.com> wrote in message news:CE912B74-5E2C-4EDF-A8CE-953B2767A69C (AT) microsoft (DOT) com... We are replacing one SQL 2000 cluster node. The existing two nodes have 4GB with the /3GB switch - no PAE. AWE is not enabled. The new node will have 15.2 GB with PAE. Should I still use the /3GB switch even though there is more than 8 GB? Thanks, Randy |
#5
| |||
| |||
|
|
One more reason to go to SQL 2008. Everything is rolling upgrades. One or two failovers is all it takes. --GNH "Randy" <Randy (AT) discussions (DOT) microsoft.com> wrote in message news:7D039071-13A9-4732-B59A-DD140B7C7F53 (AT) microsoft (DOT) com... Thanks. I will not use the switch and suggest we replace both nodes, not just the bad one. Unfortunately, the active node had been patched and requires a reboot. I can't add a new nodes until it's rebooted. Looks like we are going to be down. "Geoff N. Hiten" wrote: To answer your question, /3GB should stop at no higher than 12 GB. As for replacing cluster nodes with asymmetrical hardware, that is not supported on Windows 2000/2003. There are very good technical reasons why matched HCL-listed hardware is required. Then again, with SQL 2000, you are pretty much out of support anyway. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "Randy" <Randy (AT) discussions (DOT) microsoft.com> wrote in message news:CE912B74-5E2C-4EDF-A8CE-953B2767A69C (AT) microsoft (DOT) com... We are replacing one SQL 2000 cluster node. The existing two nodes have 4GB with the /3GB switch - no PAE. AWE is not enabled. The new node will have 15.2 GB with PAE. Should I still use the /3GB switch even though there is more than 8 GB? Thanks, Randy |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.