Skip to content

Commit 2176294

Browse files
committed
Bringing even with master.
2 parents a65d232 + 5693d6a commit 2176294

30 files changed

Lines changed: 63 additions & 49 deletions

File tree

docs/database-engine/availability-groups/windows/enhanced-database-failover.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,13 @@ helpviewer_keywords:
1515
ms.assetid:
1616
caps.latest.revision:
1717
author: "allanhirt"
18+
ms.reviewer: "mikeray"
1819
ms.author: "mikeray"
1920
manager: "jhubbard"
2021
ms.workload: "Inactive"
2122
---
2223

23-
# Add Enhanced Database Failover to an Availability Group (SQL Server)
24+
# Add enhanced database failover to an availability group (SQL Server)
2425

2526
In SQL Server 2012 and 2014, if a database participating in an availability group on the primary replica loses the ability to write transactions, it will not trigger a failover even if the replicas are synchronized and configured for automatic failover.
2627

@@ -38,7 +39,7 @@ This has the same availability group configuration as Scenario 1. Rather than Dr
3839

3940
An availability group is configured between Instance A and Instance B containing two databases: DB1 and DB2. The availability mode is set to synchronous commit with a failover mode of automatic, and enhanced database failover is enabled. Access to the disk containing DB2's data and transaction log files is lost. When the problem is detected, the availability group will automatically fail over to Instance B.
4041

41-
## Configuring and Viewing the Enhanced Database Failover Option
42+
## Configure and Viewv the enhanced database failover option
4243

4344
Enhanced database failover can be configured using SQL Server Management Studio or Transact-SQL. The PowerShell cmdlets do not currently have this ability. By default, enhanced database failover is disabled.
4445

@@ -57,20 +58,21 @@ Use the instructions found in the topic [Use the Availability Group Wizard (SQL
5758
### Transact-SQL
5859

5960
To configure enhanced database failover behavior during the creation of an availability group, DB_FAILOVER must be set to ON as follows:
60-
```
61+
62+
```SQL
6163
CREATE AVAILABILITY GROUP [AGNAME]
6264
WITH ( DB_FAILOVER = ON)
6365
...
6466
```
6567
To add this behavior after an availability group is configured, use the ALTER AVAILABILITY GROUP command:
66-
```
68+
```SQL
6769
ALTER AVAILABILITY GROUP [AGNAME] SET (DB_FAILOVER = ON)
6870
```
6971
To disable this behavior, issue the following ALTER AVAILABILITY GROUP command:
70-
```
72+
```SQL
7173
ALTER AVAILABILITY GROUP [AGNAME] SET (DB_FAILOVER = OFF)
7274
```
73-
### Dynamic Management View
75+
### Dynamic management view
7476
To see whether an availability group has enhanced database failover enabled, query the dynamic management view `sys.availablity_groups`. The column `db_failover` will have a zero if disabled or 1 if enabled.
7577

7678
## Next steps

docs/database-engine/sql-server-business-continuity-dr.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
---
22
title: Disaster recovery for SQL Server | Microsoft Docs
33
description:
4-
author: mihaelab
4+
author: "allanhirt"
55
ms.author: mihaelab
6+
ms.reviewer: "mikeray"
67
manager: jhubbard
78
ms.date: 09/14/2017
89
ms.topic: article

docs/linux/sql-server-linux-business-continuity-dr.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
---
22
title: Disaster recovery for SQL Server on Linux | Microsoft Docs
33
description:
4-
author: mihaelab
4+
author: "allanhirt"
55
ms.author: mihaelab
6+
ms.reviewer: "mikeray"
67
manager: jhubbard
78
ms.date: 10/02/2017
89
ms.topic: article

docs/relational-databases/replication/concepts/replication-management-objects-concepts.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Replication Management Objects Concepts | Microsoft Docs"
33
ms.custom: ""
4-
ms.date: "03/14/2017"
4+
ms.date: "11/08/2017"
55
ms.prod: "sql-server-2016"
66
ms.reviewer: ""
77
ms.suite: ""
@@ -182,7 +182,10 @@ ms.workload: "Inactive"
182182
183183
> [!IMPORTANT]
184184
> Although the <xref:Microsoft.SqlServer.Management.Common.ServerConnection> class supports declaring explicit transactions when setting properties, such transactions may interfere with internal replication transactions, can produce unanticipated results, and should not be used with RMO.
185-
185+
186+
### Enabling TLS 1.2 Support for RMO Components
187+
TLS1.2 support for RMO Components on Windows 2012 and lower can be enabled by installing the update [KB 3140245](http://support.microsoft.com/help/3140245), and creating the registry keys as mentioned in the article. On Windows 2012 R2 and later versions, only the registry keys as mentioned in above article, need to be created.
188+
186189
## Example
187190
This example demonstrates the caching of property changes. Changes made to the attributes of a transactional publication are cached until they are explicitly sent to the server.
188191

docs/relational-databases/system-catalog-views/sys-pdw-nodes-partitions-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "sys.pdw_nodes_partitions (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/03/2017"
5-
ms.prod: "sql-non-specified"
5+
ms.prod: ""
66
ms.reviewer: ""
77
ms.service: "sql-data-warehouse"
88
ms.suite: ""

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-network-credentials-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "sys.dm_pdw_network_credentials (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/07/2017"
5-
ms.prod: "sql-non-specified"
5+
ms.prod: ""
66
ms.reviewer: ""
77
ms.service: "sql-data-warehouse"
88
ms.suite: ""

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-os-event-logs-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "sys.dm_pdw_os_event_logs (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/07/2017"
5-
ms.prod: "sql-non-specified"
5+
ms.prod: ""
66
ms.reviewer: ""
77
ms.service: "sql-data-warehouse"
88
ms.suite: ""

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-query-stats-xe-file-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "sys.dm_pdw_query_stats_xe_file (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/07/2017"
5-
ms.prod: "sql-non-specified"
5+
ms.prod: ""
66
ms.reviewer: ""
77
ms.service: "sql-data-warehouse"
88
ms.suite: ""

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-request-steps-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "sys.dm_pdw_request_steps (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "08/01/2017"
5-
ms.prod: "sql-non-specified"
5+
ms.prod: ""
66
ms.reviewer: ""
77
ms.service: "sql-data-warehouse"
88
ms.suite: ""

docs/relational-databases/system-dynamic-management-views/sys-dm-pdw-resource-waits-transact-sql.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "sys.dm_pdw_resource_waits (Transact-SQL) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/07/2017"
5-
ms.prod: "sql-non-specified"
5+
ms.prod: ""
66
ms.reviewer: ""
77
ms.service: "sql-data-warehouse"
88
ms.suite: ""

0 commit comments

Comments
 (0)