![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||||
| |||||
|
|
I'm planning on building a SQL 2000 cluster, on 3-nodes using W2K3, with 10 instances. All nodes will be active. Each node will have 16GB RAM and 4 CPU's, connected to a SAN. Q1, is it true I can only build a max 4-node sql cluster on W2K3 EE. Yep. SQL 2000 only supports a maximum 4-node cluster on W2K3 |
|
Q2, Does anyone have any documents on how to build a 3- node cluster with 10 instances? Probably not. It isn't much different than building any other multi-node |
|
Q3, once the instances are built, can I add more instances in the future? and how ? Yes. BOL (Books on-line) has great instructions under 'Maintaining a |
|
I have built 2-node Exchange and SQL clusters Active/Active in the past but not 3-node clusters. Again, not much is different fundamentally. The tools in W2K3 are much |
| |
#3
| |||
| |||
|
|
Thanks for the advice. Do you have any info/advice on how to configure the memory for sql instances. The new servers support hot-memory, which means they will have PAE turned on by default. Should I set the max server memory or let SQL server adjust the memory automatically? "Geoff N. Hiten" wrote: Comments Inline -- Geoff N. Hiten Microsoft SQL Server MVP Senior Database Administrator Careerbuilder.com I support the Professional Association for SQL Server www.sqlpass.org "Harbhajan" <anonymous (AT) discussions (DOT) microsoft.com> wrote in message news:3b4c01c4aa6a$4284ef00$a401280a (AT) phx (DOT) gbl... I'm planning on building a SQL 2000 cluster, on 3-nodes using W2K3, with 10 instances. All nodes will be active. Each node will have 16GB RAM and 4 CPU's, connected to a SAN. Q1, is it true I can only build a max 4-node sql cluster on W2K3 EE. Yep. SQL 2000 only supports a maximum 4-node cluster on W2K3 Q2, Does anyone have any documents on how to build a 3- node cluster with 10 instances? Probably not. It isn't much different than building any other multi-node multi-instance system. Make sure and read: PRB: Installation of a named instance of SQL Server 2000 virtual server on a Windows 2003-based cluster fails http://support.microsoft.com/default...&Product=sql2k You will have to apply SP3a to each instance once you have installed the instance. Q3, once the instances are built, can I add more instances in the future? and how ? Yes. BOL (Books on-line) has great instructions under 'Maintaining a Failover Cluster'. The short version is you install the first instance (default or named) and get it up to date. You keep adding instances by rerunning the install app and specifying new disks, IP address(es) and a new network name. Each instance appears as a new virtual server on the network. I have built 2-node Exchange and SQL clusters Active/Active in the past but not 3-node clusters. Again, not much is different fundamentally. The tools in W2K3 are much better. It is more an adjustment of thinking than anything else. Good Luck. |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Do you have any update or advice on how you configured the 16GB memory on your nodes? I am looking to go to 16GB memory on W2K3, SQL 2K Enterprise (non cluster), and I am looking for others who have done this. Lots of conflicting documentation out there about whether this is stable & a good idea or not. *** Sent via Developersdex http://www.developersdex.com *** Don't just participate in USENET...get rewarded for it! |
![]() |
| Thread Tools | |
| Display Modes | |
| |