Good morning,
I've been looking around for a fair while and cant find an answer to my question (or I don't know the correct question to ask), so I'll try asking a new thread. Apologies for any duplication.
We currently have a SQL Cluster and the nodes are named (for arguments sake) SQL1\Inst1, SQL2\Inst2, SQL3\Inst3. These use ports 10.1.1.1 port 1501, 10.1.1.2 port 1502 and 10.1.1.3 port 1503 respectively.
We also have several older servers which are standalone and contain some legacy applications. What I want to do is migrate as many of the older databases onto the cluster.
To do this, I am looking at creating a new instance on the cluster (following the above conventions) and then migrating the databases across.
I considered doing this with a DNS change (creating an alias for the old server and pointing it at the appropriate cluster instance) and then using something locally on the cluster itself to repoint me at the corresponding port number.
I made the change in DNS, pointing HHOLDSVR to SQL4 and this resolved and worked (well, the ping responded)
I managed to get an alias to work locally, so HHOLDSVR will connect to SQL4,1504 however, when I try and do this remotely it fails completely.
What I was hoping was that the server would understand request was looking for SQL4, and then look at the alias, and connect that way.. obviously this didn't happen.
Has experienced this before, or is this simply not do-able?
Regards,