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/replicate-track-change-data-capture-always-on-availability.md
+7-9Lines changed: 7 additions & 9 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, Change Tracking, & Change Data Capture - Availability Groups | Microsoft Docs"
3
3
ms.custom: ""
4
-
ms.date: "05/02/2017"
4
+
ms.date: "04/25/2018"
5
5
ms.prod: "sql"
6
6
ms.prod_service: "database-engine"
7
7
ms.service: ""
@@ -94,7 +94,7 @@ ms.workload: "On Demand"
94
94
95
95
The following example creates the capture job.
96
96
97
-
```
97
+
```sql
98
98
EXEC sys.sp_cdc_add_job @job_type ='capture';
99
99
```
100
100
@@ -106,7 +106,7 @@ ms.workload: "On Demand"
106
106
107
107
To ensure that appropriate cleanup occurs at the new primary database, a local cleanup job should always be created. The following example creates the cleanup job.
108
108
109
-
```
109
+
```sql
110
110
EXEC sys.sp_cdc_add_job @job_type = 'cleanup';
111
111
```
112
112
@@ -132,7 +132,7 @@ ms.workload: "On Demand"
132
132
133
133
Use the following query to determine whether an availability group listener name has been defined for the availability group hosting a CDC database. The query will return the availability group listener name if one has been created.
134
134
135
-
```
135
+
```sql
136
136
SELECT dns_name
137
137
FROM sys.availability_group_listeners AS l
138
138
INNER JOIN sys.availability_databases_cluster AS d
@@ -148,7 +148,7 @@ ms.workload: "On Demand"
148
148
149
149
The following query can be used to determine whether read-only intent is needed to connect to a readable secondary replica.
150
150
151
-
```
151
+
```sql
152
152
SELECT g.name AS AG, replica_server_name, secondary_role_allow_connections_desc
153
153
FROM sys.availability_replicas AS r
154
154
JOIN sys.availability_groups AS g
@@ -160,7 +160,7 @@ ms.workload: "On Demand"
160
160
161
161
When **sp_addlinkedserver** is used to create a linked server to access the secondary, the *@datasrc* parameter is used for the availability group listener name or the explicit server name, and the *@provstr* parameter is used to specify read-only intent.
162
162
163
-
```
163
+
```sql
164
164
EXEC sp_addlinkedserver
165
165
@server = N'linked_svr',
166
166
@srvproduct=N'SqlServer',
@@ -202,8 +202,6 @@ If Change Data Capture needs to be disabled on a database which is part of an Al
202
202
203
203
- Pull subscription: The publisher, distributor, and subscriber databases must be on at least [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)]. This is because the merge agent on the subscriber must understand how an availability group can fail over to its secondary.
204
204
205
-
- Placing the distribution database on an availability group is not supported.
206
-
207
205
- The Publisher instances satisfy all the prerequisites required to participate in an Always On availability group. For more information see [Prerequisites, Restrictions, and Recommendations for Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/prereqs-restrictions-recommendations-always-on-availability.md).
208
206
209
207
### Restrictions
@@ -219,7 +217,7 @@ If Change Data Capture needs to be disabled on a database which is part of an Al
219
217
220
218
*Failover to the replica database is a manual procedure. Automatic failover is not provided.
221
219
222
-
**The Distributor database is not supported for use with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] or database mirroring.
220
+
**The Distributor database is not supported for use with database mirroring.
0 commit comments