Reinstalling on a Cluster Node

  • OK.  I've discovered that the Collation is different on my two clustered SQL Servers, because I'd inadvertently left the "non-Unicode Programs" language at English - United States instead of changing it to UK. So one server has the required Latin1_CI_AS, the other has "SQL_Latin1_CP1_CI_AS" - and one of our third party applications will not work with this.

    For now, it's OK that I run this database on the node that has the right collation, but this is no help in the event of a failure or planned outage of that node, which is the whole point of clustering.

    To reset the collation set of the virtual server, I need to reinstall SQL Server on the primary node, if I understand correctly (after setting the correct language option).

    What are the "gothchas" here?  Can I do it by moving the cluster group containing the virtual server from the incorrectly configured node  (this is an active/active cluster) to the correctly configured node, reinstalling SQL Server and then moving the group back to the reinstalled node?

    Or is it horribly more complex than this?

  • I should add that I've discovered that the collation set moves with the virtual server, so fail-over does still work.  In other words, it's the virtual server that needs reinstalling, not the installation of SQL on the physical server.

    Nevertheless, some feedback would be appreciated before I leap in.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply