Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Applies to:
SQL Server
SQL Server Replication involves complex user-defined topologies across publisher(s), distributor(s), and subscriber(s). Architecturally, replication needs to track and validate the servers associated with any given publication. Historically, the server information was tracked in the sys.sysservers table in the master
database, in addition to replication metadata tables.
When support was added for the Distribution database in Always On availability groups (AGs), the MSreplservers
table was added to the Distribution database, to persist server metadata and share it among the Distribution database AG replicas, instead of being stored as a local table to each instance. The AG persists the data on all replicas and ensures the server IDs and names are the same.
This table was introduced in SQL Server 2016 (13.x) SP 2 CU 3, and SQL Server 2017 (14.x) CU 6.
Column name | Data type | Description |
---|---|---|
srvid | smallint | ID of the remote server. |
srvname | sysname | Name of the server. May be a listener record if appropriate. |
Events
Mar 31, 11 PM - Apr 2, 11 PM
The biggest SQL, Fabric and Power BI learning event. March 31 – April 2. Use code FABINSIDER to save $400.
Register today