SSMS 18.1 Replication Monitor missing support for Always On
With SQL Server Management Studio 17.7 release, Replication + Always On technology was fully supported allowing registration\connections via Always On Listeners. This update fully supported use of Tracer Tokens following failover to a secondary Replica.
https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-2017#download-ssms-177
What’s new
Replication Monitor:
-
Replication monitor now supports registering a listener for scenarios where publisher database and/or distributor database is part of Availability Group. You can now monitor replication environments where publisher database and/or distribution database is part of Always On.
Problem: SSMS 18.1 Replication Monitor missing support for Always On
However, these updates were missed when building SQL Management Studio 18.1 returning various errors when attempting to register a Listener or insert Tracer Token following failover.
TITLE: Connect to Server
——————————
Cannot connect to DisAGListener.
SQL Server replication requires the actual server name to make a connection to the server. Specify the actual server name, ‘SN2\DISTRIBUTOR’. (Replication.Utilities)
TITLE: Replication Monitor
——————————
Replication Monitor could not insert the tracer token.
Failed to update database “pubs” because the database is read-only. (Microsoft SQL Server, Error: 3906)
Resolution: New SSMS 18.2 is available for DOWNLOAD
Chris Skorlinski
Microsoft SQL Server Escalation Services
