I have SQL Server 2008 named "OldSQLServer". Its data is accessed by hundred of SQL Servers via linked server.

I am moving the "OldSQLServer" to AG on SQL Server 2019, windows 2019. And I want to keep connecting to it by “OldSQLServer” name.

So I created windows cluster “MyCluster” and AG group “MyAGGroup” with AG Listener “MyAGListener”. I pointed virtual computer name “oldSQLServer” to the same IP address as “MyAGListener”

Everything looks to be working. Clients connect to “OldSQLServer, they connect to “MyAGListener” IP, which takes them to the primary node, be it “MyNode1” or “MyNode2”.

I wonder if there could be any issues with such setup?


I wonder if there could be any issues with such setup?

There are some additional configuration steps required to make Windows Integrated Auth and TLS work when connecting via a DNS alias.

For the Windows Auth steps see: How to Add a Hostname Alias for a SQL Server Instance

For the Certificate configuration, it's the same as enabling connectivity via the AG Listener, documented here: Listeners & TLS/SSL certificates

And note that you can alternatively just use the name for your AG Listener.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.