February 20, 2014 at 8:24 am
We have a 3 node cluster with an instance running on each.
Windows 2003 R2 32bit (16GB) / SQL 2005
I'm wanting to bring them all up to build 9.00.5266 (SP 4 + CU3). (1 Node is already updated)
The links and articles I have found haven't been very helpful in terms of order installation and gotchas.
Our test cluster nodes were already at 9.00.5266. (My predecessor did that before I arrived).
I updated the test cluster instances to 9.00.5292 (Cluster only has 2 nodes)
Although I got there, this did not go as expected....
The plan was :
1) Move all instances to node2
2) Update the instances on node1
3) Reboot node1
4) Move all instances to node1
5) Update the instances on node2
6) Reboot node2
7) Move an instance to node1
I got to step 5. Then the installer said I had to use the active node. That means that the instance must go offline.
Is this a pitfall of SQL 2005 or am I doing this wrong?
Why did the first update work?
There are only few hotfixes[/url] available after build 9.00.5292 (All via links from MS upon request) so I can't experiment any further without reinstalling the test cluster.
I'm sure there are a couple of DBAs out that have experience with updating SQL 2005 clustered instances. 🙂
Most helpful links found:
SQL Server failover cluster rolling patch and service pack process (2008+ only. No link to 2005) 🙁
February 20, 2014 at 9:34 am
I am afraid you cannot use the rolling upgrade method on SQL2005, you have to apply it to the active node and it does all the nodes together.
therefore you cannot avoid the outage.
---------------------------------------------------------------------
February 24, 2014 at 1:19 am
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply