Skip to content

Commit b3fa5ad

Browse files
update spacing
1 parent e06d1b6 commit b3fa5ad

1 file changed

Lines changed: 22 additions & 22 deletions

File tree

docs/database-engine/availability-groups/windows/specify-availability-group-name-page.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -12,49 +12,49 @@ f1_keywords:
1212
- "sql13.swb.adddatabasewizard.specifyagname.f1"
1313
---
1414
# Specify Availability Group Options Page for an Always On Availability Group
15+
1516
[!INCLUDE [SQL Server](../../../includes/applies-to-version/sqlserver.md)]
1617
This topic describes the options of the **Specify Availability Group Name** page. This topic is used by both the [!INCLUDE[ssAoNewAgWiz](../../../includes/ssaonewagwiz-md.md)] and [!INCLUDE[ssAoAddDbWiz](../../../includes/ssaoadddbwiz-md.md)] of [!INCLUDE[ssnoversion](../../../includes/ssnoversion-md.md)].
1718

18-
## <a name="PageOptions"></a> Specify Availability Group Options
19+
## <a name="PageOptions"></a> Specify Availability Group Options
20+
1921
**Availability group name**
2022
Specify the name of the availability group. For a new availability group, specify a valid [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] identifier that is unique across all availability groups in the Windows Server failover cluster (WSFC). The maximum length for an availability group name is 128 characters.
2123

2224
**Cluster type**
2325
Next, specify the cluster type. The possible cluster types depend on the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] version and operating system. Choose one from the following list:
2426

25-
* **Windows Server Failover Clustering**
26-
27-
Use when the availability group is hosted on instances of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] that belong to a Windows Server failover cluster for high availability and disaster recovery. Applies to all supported versions of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].
27+
- **Windows Server Failover Clustering**
28+
29+
Use when the availability group is hosted on instances of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] that belong to a Windows Server failover cluster for high availability and disaster recovery. Applies to all supported versions of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].
30+
31+
- **EXTERNAL**
32+
33+
Use when the availability group is hosted on an instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] that is managed by an external cluster technology for high availability and disaster recovery, for example Pacemaker on Linux. Applies to [!INCLUDE[sssql14](../../../includes/sssql17-md.md)] and later.
2834

29-
* **EXTERNAL**
30-
31-
Use when the availability group is hosted on an instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] that is managed by an external cluster technology for high availability and disaster recovery, for example Pacemaker on Linux. Applies to [!INCLUDE[sssql14](../../../includes/sssql17-md.md)] and later.
32-
3335
>[!IMPORTANT]
3436
> Do not choose **cluster type** = `EXTERNAL` on a Windows platform. Doing so will result in the availability group going into a resolving state and will prevent you from removing databases from the availability group.
3537
36-
* **NONE**
37-
38-
Use when the availability group is hosted on an instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] that is not managed by a cluster technology for read scale and load balancing. Applies to [!INCLUDE[sssql14](../../../includes/sssql17-md.md)] and later.
39-
40-
**Database level health detection**
41-
Check this box to enable database level health detection (DB_FAILOVER) option for the availability group. The database health detection notices when a database is no longer in the online status, when something goes wrong and will trigger the automatic failover of the availability group. See [SQL Server Always On Database Health Detection Failover Option](sql-server-always-on-database-health-detection-failover-option.md).
38+
- **NONE**
39+
40+
Use when the availability group is hosted on an instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] that is not managed by a cluster technology for read scale and load balancing. Applies to [!INCLUDE[sssql14](../../../includes/sssql17-md.md)] and later.
4241

43-
**Per Database DTC Support** Check this box to enable distributed transactions for the databases in the availability group. In order to guarantee distributed transactions, the availability group must be configured to register databases as distributed transaction resource managers. See [Configure distributed transactions for an Always On availability group](configure-availability-group-for-distributed-transactions.md)
42+
**Database level health detection** Check this box to enable database level health detection (DB_FAILOVER) option for the availability group. The database health detection notices when a database is no longer in the online status, when something goes wrong and will trigger the automatic failover of the availability group. See [SQL Server Always On Database Health Detection Failover Option](sql-server-always-on-database-health-detection-failover-option.md).
4443

45-
**Contained** Check this box to create a [contained availability group](contained-availability-groups-overview.md). A contained availability group supports managing metadata objects (users, logins, permissions, SQL Agent jobs, etc.) at the availability group level in addition to the instance level.
44+
**Per Database DTC Support** Check this box to enable distributed transactions for the databases in the availability group. In order to guarantee distributed transactions, the availability group must be configured to register databases as distributed transaction resource managers. See [Configure distributed transactions for an Always On availability group](configure-availability-group-for-distributed-transactions.md)
4645

47-
* **Reuse System Databases**
46+
**Contained** Check this box to create a [contained availability group](contained-availability-groups-overview.md). A contained availability group supports managing metadata objects (users, logins, permissions, SQL Agent jobs, etc.) at the availability group level in addition to the instance level.
4847

49-
When using a contained availability group, check this box if you want to reuse existing system databases from a previously created contained availability group of the same name.
48+
**Reuse System Databases** When using a contained availability group, check this box if you want to reuse existing system databases from a previously created contained availability group of the same name.
5049

5150
Select Databases Page (New Availability Group Wizard and Add Database Wizard)
5251

5352
## <a name="LaunchWiz"></a> Related Tasks
5453

55-
- [Use the New Availability Group Dialog Box &#40;SQL Server Management Studio&#41;](../../../database-engine/availability-groups/windows/use-the-new-availability-group-dialog-box-sql-server-management-studio.md)
54+
- [Use the New Availability Group Dialog Box &#40;SQL Server Management Studio&#41;](../../../database-engine/availability-groups/windows/use-the-new-availability-group-dialog-box-sql-server-management-studio.md)
5655

57-
- [Use the Add Database to Availability Group Wizard &#40;SQL Server Management Studio&#41;](../../../database-engine/availability-groups/windows/availability-group-add-database-to-group-wizard.md)
56+
- [Use the Add Database to Availability Group Wizard &#40;SQL Server Management Studio&#41;](../../../database-engine/availability-groups/windows/availability-group-add-database-to-group-wizard.md)
5857

59-
## See Also
60-
[Overview of Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
58+
## See Also
59+
60+
[Overview of Always On Availability Groups &#40;SQL Server&#41;](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)

0 commit comments

Comments
 (0)