sys-availability-replicas-transact - endpoint_url update

endpoint_url column should be NVARCHAR(256) instead of NVARCHAR(128).

Author: DavidWiseman

docs/relational-databases/system-catalog-views/sys-availability-replicas-transact-sql.md

@@ -33,7 +33,7 @@ If the local server instance is unable to talk to the WSFC failover cluster, for
 |**replica_metadata_id**|**int**|ID for the local metadata object for availability replicas in the Database Engine.|  
 |**replica_server_name**|**nvarchar(256)**|Server name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] that is hosting this replica and, for a non-default instance, its instance name.|  
 |**owner_sid**|**varbinary(85)**|Security identifier (SID) registered to this server instance for the external owner of this availability replica.<br /><br />NULL for non-local availability replicas.|  
-|**endpoint_url**|**nvarchar(128)**|String representation of the user-specified database mirroring endpoint that is used by connections between primary and secondary replicas for data synchronization. For information about the syntax of endpoint URLs, see [Specify the Endpoint URL When Adding or Modifying an Availability Replica &#40;SQL Server&#41;](../../database-engine/availability-groups/windows/specify-endpoint-url-adding-or-modifying-availability-replica.md).<br /><br />NULL = Unable to talk to the WSFC failover cluster.<br /><br />To change this endpoint, use the ENDPOINT_URL option of [ALTER AVAILABILITY GROUP](../../t-sql/statements/alter-availability-group-transact-sql.md)[!INCLUDE[tsql](../../includes/tsql-md.md)] statement.|  
+|**endpoint_url**|**nvarchar(256)**|String representation of the user-specified database mirroring endpoint that is used by connections between primary and secondary replicas for data synchronization. For information about the syntax of endpoint URLs, see [Specify the Endpoint URL When Adding or Modifying an Availability Replica &#40;SQL Server&#41;](../../database-engine/availability-groups/windows/specify-endpoint-url-adding-or-modifying-availability-replica.md).<br /><br />NULL = Unable to talk to the WSFC failover cluster.<br /><br />To change this endpoint, use the ENDPOINT_URL option of [ALTER AVAILABILITY GROUP](../../t-sql/statements/alter-availability-group-transact-sql.md)[!INCLUDE[tsql](../../includes/tsql-md.md)] statement.|  
 |**availability_mode**|**tinyint**|The availability mode of the replica, one of:<br /><br />0 &#124; Asynchronous commit. The primary replica can commit transactions without waiting for the secondary to write the log to disk.<br /><br />1 &#124; Synchronous commit. The primary replica waits to commit a given transaction until the secondary replica has written the transaction to disk.<br /><br />4 &#124; Configuration only. The primary replica sends availability group configuration metadata to the replica synchronously. User data is not transmitted to the replica. Available in SQL Server 2017 CU1 and later.<br /><br />For more information, see [Availability Modes &#40;Always On Availability Groups&#41;](../../database-engine/availability-groups/windows/availability-modes-always-on-availability-groups.md).|  
 |**availability_mode_desc**|**nvarchar(60)**|Description of **availability_mode**, one of:<br /><br />ASYNCHRONOUS_COMMIT<br /><br />SYNCHRONOUS_COMMIT<br /><br />CONFIGURATION_ONLY<br /><br />To change this the availability mode of an availability replica, use the AVAILABILITY_MODE option of [ALTER AVAILABILITY GROUP](../../t-sql/statements/alter-availability-group-transact-sql.md)[!INCLUDE[tsql](../../includes/tsql-md.md)] statement.<br/><br>You cannot change the availability mode of a replica to CONFIGURATION_ONLY. You cannot change a CONFIGURATION_ONLY replica to a secondary or primary replica. |  
 |**failover_mode**|**tinyint**|The [failover mode](../../database-engine/availability-groups/windows/failover-and-failover-modes-always-on-availability-groups.md) of the availability replica, one of:<br /><br />0 &#124; Automatic failover. The replica is a potential target for automatic failovers.  Automatic failover is supported only if the availability mode is set to synchronous commit (**availability_mode** = 1) and the availability replica is currently synchronized.<br /><br />1 &#124; Manual failover. A failover to a secondary replica set to manual failover must be manually initiated by the database administrator. The type of failover that is performed will depend on whether the secondary replica is synchronized, as follows:<br /><br />If the availability replica is not synchronizing or is still synchronizing, only forced failover (with possible data loss) can occur.<br /><br />If the availability mode is set to synchronous commit (**availability_mode** = 1) and the availability replica is currently synchronized, manual failover without data loss can occur.<br /><br />To view a rollup of the database synchronization health of every availability database in an availability replica, use the **synchronization_health** and **synchronization_health_desc** columns of  the [sys.dm_hadr_availability_replica_states](../../relational-databases/system-dynamic-management-views/sys-dm-hadr-availability-replica-states-transact-sql.md) dynamic management view. The rollup considers the synchronization state of every availability database and the availability mode of its availability replica.<br /><br />**Note:** To view the synchronization health of a given availability database, query the **synchronization_state** and **synchronization_health** columns of the [sys.dm_hadr_database_replica_states](../../relational-databases/system-dynamic-management-views/sys-dm-hadr-database-replica-states-transact-sql.md) dynamic management view.|