I am looking for some suggestions to a problem that we ran into upgrading our SQL Server 2005 Cluster to SP4.
We have a 5 node Active-Active cluster.
While applying SP4 to the active node of one of the instances of SQL Server 2005, the instance failed over to its primary preferred node. Rather than trying intervene, we let the patch complete.
It appears that all the binaries did get upgraded on each passive node in the cluster including on the active node, but I question the integrity of any updates made to the system databases. The reason for this is that we ended up running into an issue with database mail not working because the binaries were expecting a new column in a table in msdb which is returned by a stored procedure and neither the table nor the stored procedure had this column accounted for. I compared this against another instance in the cluster where it was successful and I was able to repair the issue, but I suspect if this occurred, then there could be more system objects that might have been missed.
I had seen the suggestion to reapply SP4 to only the active node before so figured I would try pausing all the nodes in the cluster and applying SP4 to just the active node again, but the installer pretty much flew right through and returned a successful upgrade, but didn't appear to apply any updates. I know I have reapplied SP4 to a non-clustered instance before and it actually went through the whole install so maybe this has something to do with being part of the cluster.
I am hoping someone can give me some ideas on what I can do to make sure the system dbs get upgraded without having to reinstall any instances as this wouldn't go over so well in our environment.