Using aliases, listeners or other virtual front-end features - syncsort_capacity_management - Latest

SQL Server can be set up in high-availability configurations with shared disks so that if a primary SQL Server machine fails a secondary can spring into action and take over. These are often accompanied by a means of talking to the pair of servers by a common name, thus removing the need to “know” which one is active at any one time.

Very often this aliasing or “listener” feature will use a different port to the default.

You can treat connections to this common name in the same way as directly accessing a specific database, by putting the name and if necessary the port number to use, for example:

• If – agProdDb1 and agProdDb2 are accessible by a listener called agProdSCM using port 51009.

  Note: The port number is that of the SQL instances, not the listener itself, although confusingly they may all be the same number.
• Then – you set a SQL Server machine name of: agProdSCMListener,51109 in the Syncsort™ Capacity Management Core installation dialog, running Data Management or System Manager to create a database, when adding a data­base to the Syncsort™ Capacity Management Portal or when linking the Syncsort™ Capacity Management Job Scheduler to a database.

For a good pictorial description, you may want to review this Microsoft blog entry: https://learn.microsoft.com/en-us/archive/blogs