![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm doing research to prepare a new installation of SQL 2008 on Windows 2008 cluster on 64bit IBM Blade servers. Is there any documentation on this particular environment? Another question is, if I have built such an A/P cluster, is that possible to join a third node later to be an A/A/P cluster? Regards, RG |
#3
| |||
| |||
|
|
Cluster + Blade = low availability. Clusters exist to provide hardware redundancy. Blades exist to share hardware as much as possible. Anyone else see the problem here? -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "RoyalGala" <royal.gala (AT) gmail (DOT) com> wrote in message news:CF976AF4-C10B-4E94-9A3E-AE3851ECF283 (AT) microsoft (DOT) com... I'm doing research to prepare a new installation of SQL 2008 on Windows 2008 cluster on 64bit IBM Blade servers. Is there any documentation on this particular environment? Another question is, if I have built such an A/P cluster, is that possible to join a third node later to be an A/A/P cluster? Regards, RG |
#4
| |||
| |||
|
|
Thanks GNH. But I don't see Blades will decrease availability as the shared hardware are redundant. Any voice on this is welcome. "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:O39Vi2%23iJHA.4880 (AT) TK2MSFTNGP02 (DOT) phx.gbl... Cluster + Blade = low availability. Clusters exist to provide hardware redundancy. Blades exist to share hardware as much as possible. Anyone else see the problem here? -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "RoyalGala" <royal.gala (AT) gmail (DOT) com> wrote in message news:CF976AF4-C10B-4E94-9A3E-AE3851ECF283 (AT) microsoft (DOT) com... I'm doing research to prepare a new installation of SQL 2008 on Windows 2008 cluster on 64bit IBM Blade servers. Is there any documentation on this particular environment? Another question is, if I have built such an A/P cluster, is that possible to join a third node later to be an A/A/P cluster? Regards, RG |
#5
| |||
| |||
|
|
As far as multiple nodes, you can add more nodes easily later on. You can also add more SQL Instances independent of nodes. I do recommend using Windows 2008 as your base OS for clustering. The Microsoft Clustering team did a really good job with the new improvements. -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "RoyalGala" <royal.gala (AT) gmail (DOT) com> wrote in message news:40A40119-6215-4516-8A99-F6813AC0C6DE (AT) microsoft (DOT) com... Thanks GNH. But I don't see Blades will decrease availability as the shared hardware are redundant. Any voice on this is welcome. "Geoff N. Hiten" <SQLCraftsman (AT) gmail (DOT) com> wrote in message news:O39Vi2%23iJHA.4880 (AT) TK2MSFTNGP02 (DOT) phx.gbl... Cluster + Blade = low availability. Clusters exist to provide hardware redundancy. Blades exist to share hardware as much as possible. Anyone else see the problem here? -- Geoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP "RoyalGala" <royal.gala (AT) gmail (DOT) com> wrote in message news:CF976AF4-C10B-4E94-9A3E-AE3851ECF283 (AT) microsoft (DOT) com... I'm doing research to prepare a new installation of SQL 2008 on Windows 2008 cluster on 64bit IBM Blade servers. Is there any documentation on this particular environment? Another question is, if I have built such an A/P cluster, is that possible to join a third node later to be an A/A/P cluster? Regards, RG |
![]() |
| Thread Tools | |
| Display Modes | |
| |