You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/database-engine/availability-groups/windows/enhanced-database-failover.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,12 +15,13 @@ helpviewer_keywords:
15
15
ms.assetid:
16
16
caps.latest.revision:
17
17
author: "allanhirt"
18
+
ms.reviewer: "mikeray"
18
19
ms.author: "mikeray"
19
20
manager: "jhubbard"
20
21
ms.workload: "Inactive"
21
22
---
22
23
23
-
# Add Enhanced Database Failover to an Availability Group (SQL Server)
24
+
# Add enhanced database failover to an availability group (SQL Server)
24
25
25
26
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.
26
27
@@ -38,7 +39,7 @@ This has the same availability group configuration as Scenario 1. Rather than Dr
38
39
39
40
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.
40
41
41
-
## Configuring and Viewing the Enhanced Database Failover Option
42
+
## Configure and Viewv the enhanced database failover option
42
43
43
44
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.
44
45
@@ -57,20 +58,21 @@ Use the instructions found in the topic [Use the Availability Group Wizard (SQL
57
58
### Transact-SQL
58
59
59
60
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
61
63
CREATE AVAILABILITY GROUP [AGNAME]
62
64
WITH ( DB_FAILOVER =ON)
63
65
...
64
66
```
65
67
To add this behavior after an availability group is configured, use the ALTER AVAILABILITY GROUP command:
66
-
```
68
+
```SQL
67
69
ALTER AVAILABILITY GROUP [AGNAME] SET (DB_FAILOVER =ON)
68
70
```
69
71
To disable this behavior, issue the following ALTER AVAILABILITY GROUP command:
70
-
```
72
+
```SQL
71
73
ALTER AVAILABILITY GROUP [AGNAME] SET (DB_FAILOVER = OFF)
72
74
```
73
-
### Dynamic Management View
75
+
### Dynamic management view
74
76
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.
Copy file name to clipboardExpand all lines: docs/relational-databases/replication/concepts/replication-management-objects-concepts.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Replication Management Objects Concepts | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "03/14/2017"
4
+
ms.date: "11/08/2017"
5
5
ms.prod: "sql-server-2016"
6
6
ms.reviewer: ""
7
7
ms.suite: ""
@@ -182,7 +182,10 @@ ms.workload: "Inactive"
182
182
183
183
> [!IMPORTANT]
184
184
> 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
+
186
189
## Example
187
190
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.
0 commit comments