Skip to main content

Setup SQL Alias on SafeCom Secondary servers and Primary SQL server

Article # 3016526 - Page views: 694


I am unable to add a secondary server to my SafeCom Multi-server environment.


The Customer demands that SQL databases has to run on non-standard fixed SQL TCP ports


The Customer demands that SQL databases has to run on dynamic SQL TCP ports


How to I make my SafeCom replication work anyway ?

There are many factors that must be in place in order to run on either a dynamic SQL TCP port, or a non-standard SQL TCP port.

One of the important things to remember is that whatever SQL TCP port the Primary SQL server or Secondary SQL server instance is running, then that/these ports most be open in the various firewalls, and routable over the network. Remember that with dynamic ports, any thinkable dynamic port must also be routable over the network, and allowed through relevant firewalls.

Very often the DNS server must also be setup to allow for the Primary and Secondary SQL instance to resolve each others name.

If you know that the customer is using either a dynamic SQL TCP port or a non-standard SQL TCP port,or suspect the DNS server to not be working correctly, then the attached document will give you some hints on how to setup SQL Alias pointers on SafeCom Primary SQL and Secondary SQL instances, to help them "find" each other over the network. Thereby possibly overcoming the replication problem.



How to setup SQL alias between Primary SQL database and Secondary SQL database.docx (160 KB)

  • Was this article helpful?