Insufficient data from Andrew Fryer

The place where I page to when my brain is full up of stuff about the Microsoft platform

Tricking a client into connecting to a SQL Server Instance

One of the challenges of consolidation and upgrades is that some applications might have hard coded or difficult to find references to the server instance they are connecting to.

When you want to point this hypothetical application to the non-default instance on a new server you can often use DNS to create an alia to a specific server \instance combination providing the alias (i.e. the legacy server) is no longer around.

However for side by side upgrade in a non virtual world, another simple tip is to fiddle with the SQL Server connection manager:

  • Disable all the server network protocols except TCP/IP
  • Change all the IPs of default instance to listen on port 1435 (from 1433 – default)
  • Change all the IPs port of the named instance you want to be the default to listen on port 1433
  • Restarted both default and named instance. 

Now I can connect to the named instance by simply typing host server name (or “.”) through SSMS or the legacy application.

I wouldn’t recommend this approach for any internet facing server as you will probably not want to use the default port of 1433 at all.