I thought might save some time by upgrading an existing clustered instance of SQL2K8 to SQL2K14 instead of starting from scratch.
It hasn't worked out AT ALL. (;-)
On the Features Rules page, I get green lights on everything except "SQL2005 Clustered Instance Upgrade"! There is not a trace of SQL2K5 on this Microsoft Cluster Services cluster (NOT VMware or HyperV). Never has been since its inception in Aug 2015.
The error message reported by the installation program is "Rule 'SQL Server 2005 clustered instance upgrade' failed. The SQL Server and Analysis features of the selected clustered SQL Server 2005 instance have been installed into separate groups. SQL Server 2014 Setup can only upgrade clustered instances installed into a single group. To continue, uninstall either SQL Server or Analysis Services before you upgrade.
Hmmmmmmm.
The operating system is W2K12R2 RTM. There are three nodes in an MSCS cluster. I am working to upgrade the first passive node.
The only thing a little non-standard is I've just changed the name of the clustered instance before upgrading. It seemed to go well; I saw it update DNS. I was able to fail the instance whose name I changed among the nodes with no issues at all.
The node I'm working on has no issue resolving the name of the instance.
I had also cleared an error relating to the fact that the instance, which had never been used, was not listening on 1433. The SQL Browser was up and running so the installation program should have talked to in on port 50762, but I let that go. It is actually now listening on 1433. I tested it with the osql tool.
Is this too bizarre, or what?
Thanks, if you can help me.