Skip to content

Commit 966c7a7

Browse files
author
Bruce Hamilton
committed
Metadata updates for relational-databases 3 of 5
1 parent 081618d commit 966c7a7

959 files changed

Lines changed: 5508 additions & 2168 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/relational-databases/replication/administration/administer-a-peer-to-peer-topology-replication-transact-sql-programming.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Administer a Peer-to-Peer Topology (Replication Transact-SQL Programming) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/14/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -21,6 +24,7 @@ manager: "jhubbard"
2124
ms.workload: "Inactive"
2225
---
2326
# Administer a Peer-to-Peer Topology (Replication Transact-SQL Programming)
27+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2428
Administering a peer-to-peer topology is similar to administering a typical transactional replication topology, but there are a number of areas with special considerations. The principal difference in administering a peer-to-peer topology is that some changes require the system to be *quiesced*. Quiescing a system involves stopping activity on published tables at all nodes and ensuring that each node has received all changes from all other nodes. For more information, see [Quiesce a Replication Topology (Replication Transact-SQL Programming)](../../../relational-databases/replication/administration/quiesce-a-replication-topology-replication-transact-sql-programming.md).
2529

2630
> [!NOTE]

‎docs/relational-databases/replication/administration/administration-replication.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Administration (Replication) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/01/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -23,6 +26,7 @@ manager: "jhubbard"
2326
ms.workload: "Inactive"
2427
---
2528
# Administration (Replication)
29+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2630
This section contains information on administering replication topologies. We recommend that you read the best practices topic first, and then follow the links from that topic to more detailed information in this section and other sections.
2731

2832
## In This Section

‎docs/relational-databases/replication/administration/back-up-and-restore-replicated-databases.md‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Back Up and Restore Replicated Databases | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/14/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -32,7 +35,7 @@ manager: "jhubbard"
3235
ms.workload: "On Demand"
3336
---
3437
# Back Up and Restore Replicated Databases
35-
[!INCLUDE[tsql-appliesto-ss2016-xxxx-xxxx-xxx_md](../../../includes/tsql-appliesto-ss2016-xxxx-xxxx-xxx-md.md)]
38+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
3639

3740
Replicated databases require special attention with regards to backing up and restoring data. This topic provides introductory information and links to further information on backup and restore strategies for each type of replication.
3841

‎docs/relational-databases/replication/administration/best-practices-for-replication-administration.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Best Practices for Replication Administration | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/14/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -20,6 +23,7 @@ manager: "jhubbard"
2023
ms.workload: "On Demand"
2124
---
2225
# Best Practices for Replication Administration
26+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2327
After you have configured replication, it is important to understand how to administer a replication topology. This topic provides basic best practice guidance in a number of areas with links to more information for each area. In addition to following the best practice guidance presented in this topic, consider reading through the frequently asked questions topic to acquaint yourself with common questions and issues: [Frequently Asked Questions for Replication Administrators](../../../relational-databases/replication/administration/frequently-asked-questions-for-replication-administrators.md).
2428

2529
It is useful to divide the best practice guidance into two areas:

‎docs/relational-databases/replication/administration/clean-up-merge-metadata-replication-transact-sql-programming.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Clean Up Merge Metadata (Replication Transact-SQL Programming) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/03/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -22,6 +25,7 @@ manager: "jhubbard"
2225
ms.workload: "Inactive"
2326
---
2427
# Clean Up Merge Metadata (Replication Transact-SQL Programming)
28+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2529
Merge replication metadata is cleaned up periodically by the Merge Agent based on the retention setting for the publication. This occurs at the Publisher and Subscriber in the [MSmerge_genhistory](../../../relational-databases/system-tables/msmerge-genhistory-transact-sql.md), [MSmerge_contents](../../../relational-databases/system-tables/msmerge-contents-transact-sql.md), [MSmerge_tombstone](../../../relational-databases/system-tables/msmerge-tombstone-transact-sql.md), [MSmerge_past_partition_mappings](../../../relational-databases/system-tables/msmerge-past-partition-mappings-transact-sql.md), and [MSmerge_current_partition_mappings](../../../relational-databases/system-tables/msmerge-current-partition-mappings.md) system tables. You can also programmatically clean up the data in these tables using replication stored procedures.
2630

2731
### To manually clean up merge metadata

‎docs/relational-databases/replication/administration/common-actions-requiring-an-updated-backup.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Common Actions Requiring an Updated Backup | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/04/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -21,6 +24,7 @@ manager: "jhubbard"
2124
ms.workload: "Inactive"
2225
---
2326
# Common Actions Requiring an Updated Backup
27+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2428
If you perform regular log backups, any replication-related changes should be captured in the log backups. If you don't perform log backups, perform a backup of the publication, distribution, subscription, **msdb**, and **master** databases after making modifications to your replication schema or topology.
2529

2630
## Publication Database

‎docs/relational-databases/replication/administration/compare-replicated-tables-for-differences-replication-programming.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Compare Replicated Tables for Differences (Replication Programming) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/14/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -22,6 +25,7 @@ manager: "jhubbard"
2225
ms.workload: "Inactive"
2326
---
2427
# Compare Replicated Tables for Differences (Replication Programming)
28+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2529
Article validation is used to determine if published data for table articles at the Publisher and Subscriber are not identical, which can indicate non-convergence. For more information, see [Validate Replicated Data](../../../relational-databases/replication/validate-replicated-data.md). However, validation only returns pass or fail information and does not provide any information about what is different between the source and destination tables. The **tablediff** command prompt utility returns detailed difference information between two tables and can even generate a [!INCLUDE[tsql](../../../includes/tsql-md.md)] script to bring a subscription into convergence with data at the Publisher.
2630

2731
> [!NOTE]

‎docs/relational-databases/replication/administration/configure-predefined-replication-alerts-sql-server-management-studio.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Configure Predefined Replication Alerts (SQL Server Management Studio) | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/14/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -20,6 +23,7 @@ manager: "jhubbard"
2023
ms.workload: "Inactive"
2124
---
2225
# Configure Predefined Replication Alerts (SQL Server Management Studio)
26+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2327
Replication offers the following predefined alerts, which can be configured to respond to replication events:
2428

2529
- **Replication: agent success**

‎docs/relational-databases/replication/administration/configure-the-transaction-set-job-for-an-oracle-publisher.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Configure the Transaction Set Job for an Oracle Publisher | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/07/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -22,6 +25,7 @@ manager: "jhubbard"
2225
ms.workload: "Inactive"
2326
---
2427
# Configure the Transaction Set Job for an Oracle Publisher
28+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2529
The **Xactset** job is an Oracle database job created by replication that runs at an Oracle Publisher to create transaction sets when the Log Reader Agent is not connected to the Publisher. You can enable and configure this job from the Distributor programmatically using replication stored procedures. For more information, see [Performance Tuning for Oracle Publishers](../../../relational-databases/replication/non-sql/performance-tuning-for-oracle-publishers.md).
2630

2731
### To enable the transaction set job

‎docs/relational-databases/replication/administration/distributor-and-publisher-information-script.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,12 @@
22
title: "Distributor and Publisher Information Script | Microsoft Docs"
33
ms.custom: ""
44
ms.date: "03/09/2017"
5-
ms.prod: "sql-server-2016"
5+
ms.prod: "sql-non-specified"
6+
ms.prod_service: "database-engine"
7+
ms.service: ""
8+
ms.component: "replication"
69
ms.reviewer: ""
7-
ms.suite: ""
10+
ms.suite: "sql"
811
ms.technology:
912
- "replication"
1013
ms.tgt_pltfrm: ""
@@ -20,6 +23,7 @@ manager: "jhubbard"
2023
ms.workload: "On Demand"
2124
---
2225
# Distributor and Publisher Information Script
26+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
2327
This script uses system tables and replication stored procedures to answer questions commonly asked about objects at the Distributor and Publisher. The script can be used "as-is" and can also provide the basis for customized scripts. The script might require two modifications to run in your environment:
2428

2529
- Change the line `use AdventureWorks2012` to use the name of your publication database.

0 commit comments

Comments
 (0)