Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Use this dialog box to view the properties of an availability replica.
Automatic failover. The replica is a target for automatic failovers. This is supported only if the availability mode is set to synchronous commit.
Manual failover. The replica can only be failed over to manually by the database administrator.
Connections in primary role
The type of client connections supported when the replica owns the primary role.
Allow all connections
All connections are allowed to the databases in the primary replica. This is the default setting.
Allow read/write connections
Connections where the Application Intent connection property is set to ReadOnly are disallowed. When the Application Intent property is set to ReadWrite or the application intent connection property is not set, the connection is allowed.
Whether an availability replica that is performing the secondary role (that is, a secondary replica) can accept connections from clients, one of:
No direct connections are allowed to secondary databases of this replica. They are not available for read access. This is the default setting.
Only direct read-only connections are allowed to secondary databases of this replica. The secondary database(s) are all available for read access.
All connections are allowed to secondary databases of this replica, but only for read access. The secondary database(s) are all available for read access.
The time-out period, in seconds. The time-out period is the maximum time that the replica waits to receive a message from another replica before considering connection between the primary and secondary replica have failed. Session timeout detects whether secondaries are connected the primary replica. On detecting a failed connection with a secondary replica, the primary replica considers the secondary replica to be NOT_SYNCHRONIZED. On detecting a failed connection with the primary replica, a secondary replica simply attempts to reconnect.
Session timeouts do not cause automatic failovers.