Yes, that seems familiar. You need to create an endpoint and grant permission on it.
As for the name, you can call i Gretchen, hadr_endpoint, or whatever you prefer.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi. In the past I created AlwaysOn availability groups using the wizard. I specified the endpoint_URL as a FQDN like this example: TCP://hostname.xxx.yyy.zzz:50xx I didn't have to create any TCP endpoints. If I install using T-SQL, I will use the following including the endpoint URL:
CREATE AVAILABILITY GROUP AG1
WITH (
AUTOMATED_BACKUP_PREFERENCE = SECONDARY,
DB_FAILOVER = ON,
DTC_SUPPORT = NONE,
REQUIRED_SYNCHRONIZED_SECONDARIES_TO_COMMIT = 0
)
FOR
DATABASE Test1
REPLICA ON
N'<server_name>' WITH
(
ENDPOINT_URL = 'hostname.xxx.yyy.zzz:50xx'
etc.
etc.
I read a post that says I first separately need to create the TCP endpoint and assign connect permission to the SQL service account like the following:
CREATE ENDPOINT Hadr_endpoint
STATE=STARTED
AS TCP (LISTENER_PORT=50xx)
FOR DATABASE_MIRRORING (ROLE=ALL);
GO
GRANT CONNECT ON ENDPOINT::[Hadr_endpoint] TO [NT Service\MSSQLSERVER]
GO
I just want to validate if the CREATE ENDPOINT and GRANT CONNECT is actually necessary. Also, what can I specify as the endpoint name to substitute in place of "Hadr_endpoint"? Thanks.
Yes, that seems familiar. You need to create an endpoint and grant permission on it.
As for the name, you can call i Gretchen, hadr_endpoint, or whatever you prefer.