We have a SQL Server 2008 server that I successfully migrated to a new computer with SQL Server 2019.
The SQL Server 2008 server name is 123.123.123.123. It
It has two instances named: 123.123.123.123 and 123.123.123.123\ABC.
The SQL Server 2019 server name is CMP123456. The
The instances are named: CMP123456 and CMP123456\ABC.
I would like to use aliases on the 2019 server because unfortunately some programmers hardcoded the instance names into their code.
I created two aliases:
[123.123.123.123 TCP 1433 localhost]
[123.123.123.123\ABC TCP 1433 localhost\ABC]
[123.123.123.123 TCP 1433 localhost]
[123.123.123.123\ABC TCP 1433 localhost\ABC]
When I use SSMS to login, however both aliases connect me to CMP123456. I am unable to create an alias that will connect me to CMP123456\ABC.
These are the aliases I have tried. They
They all fail as "server not found" errors:
[123.123.123.123\ABC TCP 1434 localhost\ABC]
[123.123.123.123\ABC TCP 1433 CMP123456\ABC]
[123.123.123.123\ABC TCP 1433 ABC]
[123.123.123.123\ABC TCP 1434 localhost\ABC]
[123.123.123.123\ABC TCP 1433 CMP123456\ABC]
[123.123.123.123\ABC TCP 1433 ABC]
[(No Alias) In this case I was hoping the one localhost alias would work for both instances.]
Any ideas? Is not allowing two aliases a bug/feature of SQL Server 2019?
