Merge branch 'master' of https://github.com/MicrosoftDocs/sql-docs-pr into sqlvnext_prerelease

Author: v-thepet

.openpublishing.redirection.json

@@ -1041,6 +1041,156 @@
    "source_path" : "docs/integration-services/packages/integration-services-project-conversion-wizard.md",
    "redirect_url": "/sql/integration-services/packages/deploy-integration-services-ssis-projects-and-packages",
    "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/run-a-package-in-sql-server-data-tools.md",
+   "redirect_url": "/sql/integration-services/packages/run-integration-services-ssis-packages",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/run-a-package-on-the-ssis-server-using-sql-server-management-studio.md",
+   "redirect_url": "/sql/integration-services/packages/run-integration-services-ssis-packages",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/execute-package-dialog-box.md",
+   "redirect_url": "/sql/integration-services/packages/run-integration-services-ssis-packages",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/configure-checkpoints-for-restarting-a-failed-package.md",
+   "redirect_url": "/sql/integration-services/packages/restart-packages-by-using-checkpoints",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/packages/schedule-a-package-by-using-sql-server-agent.md",
+   "redirect_url": "/sql/integration-services/packages/sql-server-agent-jobs-for-packages",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/packages/implementation-of-child-packages.md",
+   "redirect_url": "/sql/integration-services/packages/load-balancing-packages-on-remote-servers-by-using-sql-server-agent",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/implementation-of-the-parent-package.md",
+   "redirect_url": "/sql/integration-services/packages/load-balancing-packages-on-remote-servers-by-using-sql-server-agent",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/logging-for-load-balanced-packages-on-remote-servers.md",
+   "redirect_url": "/sql/integration-services/packages/load-balancing-packages-on-remote-servers-by-using-sql-server-agent",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/packages/use-the-values-of-variables-and-parameters-in-a-child-package.md",
+   "redirect_url": "/sql/integration-services/packages/legacy-package-deployment-ssis",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/walkthrough-set-up-integration-services-scale-out.md",
+   "redirect_url": "/sql/integration-services/integration-services-ssis-scale-out",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/integration-services-ssis-scale-out-master.md",
+   "redirect_url": "/sql/integration-services/integration-services-ssis-scale-out",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/integration-services-ssis-scale-out-worker.md",
+   "redirect_url": "/sql/integration-services/integration-services-ssis-scale-out",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/run-packages-in-integration-services-ssis-scale-out.md",
+   "redirect_url": "/sql/integration-services/integration-services-ssis-scale-out",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/troubleshooting/debug-a-package-by-setting-breakpoints-on-a-task-or-a-container.md",
+   "redirect_url": "/sql/integration-services/troubleshooting/debugging-control-flow",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/troubleshooting/set-breakpoints.md",
+   "redirect_url": "/sql/integration-services/troubleshooting/debugging-control-flow",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/analysis-of-data-flow.md",
+   "redirect_url": "/sql/integration-services/troubleshooting/debugging-data-flow",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/troubleshooting/configure-an-error-output-in-a-data-flow-component.md",
+   "redirect_url": "/sql/integration-services/troubleshooting/debugging-data-flow",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/troubleshooting/add-a-data-viewer-to-a-data-flow.md",
+   "redirect_url": "/sql/integration-services/troubleshooting/debugging-data-flow",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/data-flow-taps.md",
+   "redirect_url": "/sql/integration-services/troubleshooting/debugging-data-flow",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/add-a-log-for-data-flow-performance-counters.md",
+   "redirect_url": "/sql/integration-services/performance/performance-counters",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/performance/view-log-entries-in-the-log-events-window.md",
+   "redirect_url": "/sql/integration-services/performance/events-logged-by-an-integration-services-package",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/performance/active-operations-dialog-box.md",
+   "redirect_url": "/sql/integration-services/performance/monitor-running-packages-and-other-operations",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/viewing-and-stopping-packages-running-on-the-integration-services-server.md",
+   "redirect_url": "/sql/integration-services/performance/monitor-running-packages-and-other-operations",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/reports-for-the-integration-services-server.md",
+   "redirect_url": "/sql/integration-services/performance/monitor-running-packages-and-other-operations",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/view-reports-for-the-integration-services-server.md",
+   "redirect_url": "/sql/integration-services/performance/monitor-running-packages-and-other-operations",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/enable-package-logging-in-sql-server-data-tools.md",
+   "redirect_url": "/sql/integration-services/performance/integration-services-ssis-logging",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/configure-ssis-logs-dialog-box.md",
+   "redirect_url": "/sql/integration-services/performance/integration-services-ssis-logging",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/configure-logging-by-using-a-saved-configuration-file.md",
+   "redirect_url": "/sql/integration-services/performance/integration-services-ssis-logging",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/enable-logging-for-package-execution-on-the-ssis-server.md",
+   "redirect_url": "/sql/integration-services/performance/integration-services-ssis-logging",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/performance/custom-messages-for-logging.md",
+   "redirect_url": "/sql/integration-services/performance/integration-services-ssis-logging",
+   "redirect_document_id": false
   }
 
  ]

docs/database-engine/availability-groups/windows/replicate-track-change-data-capture-always-on-availability.md

@@ -1,7 +1,7 @@
 ---
-title: "Replicate, Track, Change Data Capture - Always On Availability | Microsoft Docs"
+title: "Replication, Change Tracking, & Change Data Capture - Availability Groups | Microsoft Docs"
 ms.custom: ""
-ms.date: "05/17/2016"
+ms.date: "04/18/2017"
 ms.prod: "sql-server-2016"
 ms.reviewer: ""
 ms.suite: ""
@@ -20,42 +20,24 @@ author: "MikeRayMSFT"
 ms.author: "mikeray"
 manager: "jhubbard"
 ---
-# Replicate, Track, Change Data Capture - Always On Availability
+# Replication, change tracking, & change data capture - Always On availability groups
 [!INCLUDE[tsql-appliesto-ss2016-xxxx-xxxx-xxx_md](../../../includes/tsql-appliesto-ss2016-xxxx-xxxx-xxx-md.md)]
 
   [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] Replication, change data capture (CDC), and change tracking (CT) are supported on [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)] helps provide high availability and additional database recovery capabilities.  
 
- **In this Topic:**  
-  
--   [Overview of Replication on Always On Availability Groups](#Overview)  
-  
-    -   [Publisher Redirection](#PublisherRedirect)  
-  
-    -   [Changes to Replication Agents to Support Always On Availability Groups](#Changes)  
-  
-    -   [Stored Procedures Supporting Always On](#StoredProcs)  
-  
-    -   [Change Data Capture](#CDC)  
-  
-    -   [Change Tracking](#CT)  
-  
--   [Prerequisites, Restrictions, and Considerations for Using Replication with Always On Availability Groups](#Prereqs)  
-  
--   [Related Tasks](#RelatedTasks)  
-  
-##  <a name="Overview"></a> Overview of Replication on Always On Availability Groups  
+##  <a name="Overview"></a> Overview of replication with availability groups  
 
 ###  <a name="PublisherRedirect"></a> Publisher Redirection  
  When a published database is aware of [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)], the distributor that provides agent access to the publishing database is configured with redirected_publishers entries. These entries redirect the originally configured publisher/database pair, making use of an availability group listener name to connect to the publisher and publishing database. Established connections through the availability group listener name will fail on failover. When the replication agent restarts after failover, the connection will automatically be redirected to the new primary.  
 
- In an Always On availability group a secondary database cannot be a publisher. Republishing is only supported when transactional replication is combined with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)].  
+ In an availability group a secondary database cannot be a publisher. Republishing is only supported when transactional replication is combined with [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)].  
 
  If a published database is a member of an availability group and the publisher is redirected, it must be redirected to an availability group listener name associated with the availability group. It may not be redirected to an explicit node.  
 
 > [!NOTE]  
 >  After failover to a secondary replica, Replication Monitor is unable to adjust the name of the publishing instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] and will continue to display replication information under the name of the original primary instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]. After failover, a tracer token cannot be entered by using the Replication Monitor, however a tracer token entered on the new publisher by using [!INCLUDE[tsql](../../../includes/tsql-md.md)], is visible in Replication Monitor.  
   
-###  <a name="Changes"></a> General Changes to Replication Agents to Support Always On Availability Groups  
+###  <a name="Changes"></a> General changes to replication agents to support availability groups  
  Three replication agents were modified to support [!INCLUDE[ssHADR](../../../includes/sshadr-md.md)]. The Log Reader, Snapshot, and Merge agents were modified to query the distribution database for the redirected publisher and to use the returned availability group listener name, if a redirected publisher was declared, to connect to the database publisher.  
 
  By default, when the agents query the distributor to determine whether the original publisher has been redirected, the suitability of the current target or redirection will be verified prior to returning the redirected host to the agent. This is recommended behavior. However, if agent start up occurs very frequently the overhead associated with the validation stored procedure may be deemed too costly. A new command line switch, *BypassPublisherValidation*, has been added to the Logreader, Snapshot, and Merge agents. When the switch is used, the redirected publisher is returned immediately to the agent and execution of the validation stored procedure is bypassed.  
@@ -67,15 +49,15 @@ manager: "jhubbard"
 
 -   **Replicated Database Consistency**  
 
-     When a published database is a member of an Always On availability group, by default the log reader will not process log records that have not already been hardened at all availability group secondary replicas. This insures that on failover, all rows replicated to a subscriber also are present at the new primary.  
+     When a published database is a member of an availability group, by default the log reader will not process log records that have not already been hardened at all availability group secondary replicas. This insures that on failover, all rows replicated to a subscriber also are present at the new primary.  
 
-     When the publisher has only two Always On availability replicas (one primary and one secondary) and a failover happens, the original primary replica remains down because the logreader does not move forward until all secondary databases are brought back online or until the failing secondary replicas are removed from the availability group. The logreader, now running against the secondary database, will not proceed forward since Always On cannot harden any changes to any secondary database. To allow the logreader to proceed further and still have disaster recovery capacity, remove the original primary replica from the availability group using ALTER AVAILABITY GROUP <group_name> REMOVE REPLICA. Then add a new secondary replica to the availability group.  
+     When the publisher has only two availability replicas (one primary and one secondary) and a failover happens, the original primary replica remains down because the logreader does not move forward until all secondary databases are brought back online or until the failing secondary replicas are removed from the availability group. The logreader, now running against the secondary database, will not proceed forward since Always On cannot harden any changes to any secondary database. To allow the logreader to proceed further and still have disaster recovery capacity, remove the original primary replica from the availability group using ALTER AVAILABITY GROUP <group_name> REMOVE REPLICA. Then add a new secondary replica to the availability group.  
 
 -   **Trace flag 1448**  
 
      Trace flag 1448 enables the replication log reader to move forward even if the asynchronous secondary replicas have not acknowledged the reception of a change. Even with this trace flag enabled,, the log reader always waits for the synchronous secondary replicas. The log reader will not go beyond the min ack of the synchronous secondary replicas. This trace flag applies to the instance of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], not just to an availability group, an availability database, or a log reader instance. This trace flag takes effect immediately without a restart. It can be activated ahead of time or when an asynchronous secondary replica fails.  
 
-###  <a name="StoredProcs"></a> Stored Procedures Supporting Always On  
+###  <a name="StoredProcs"></a> Stored procedures supporting availability groups  
 
 -   **sp_redirect_publisher**  
 

docs/integration-services/TOC.md

@@ -65,10 +65,6 @@
 ## [System Variables](system-variables.md)
 
 # [Scale Out](integration-services-ssis-scale-out.md)
-## [Walkthrough: Set Up Integration Services Scale Out](walkthrough-set-up-integration-services-scale-out.md)
-## [Run Packages in Integration Services (SSIS) Scale Out](run-packages-in-integration-services-ssis-scale-out.md)
-## [Integration Services (SSIS) Scale Out Master](integration-services-ssis-scale-out-master.md)
-## [Integration Services (SSIS) Scale Out Worker](integration-services-ssis-scale-out-worker.md)
 
 # [Azure Feature Pack for Integration Services (SSIS)](azure-feature-pack-for-integration-services-ssis.md)
 

docs/integration-services/change-data-capture/determine-whether-the-change-data-is-ready.md

@@ -1,23 +1,23 @@
----
-title: "Determine Whether the Change Data Is Ready | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/06/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "integration-services"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-helpviewer_keywords: 
-  - "incremental load [Integration Services],determining readiness"
-ms.assetid: 04935f35-96cc-4d70-a250-0fd326f8daff
-caps.latest.revision: 26
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Determine Whether the Change Data Is Ready
+---
+title: "Determine Whether the Change Data Is Ready | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/06/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "integration-services"
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+helpviewer_keywords: 
+  - "incremental load [Integration Services],determining readiness"
+ms.assetid: 04935f35-96cc-4d70-a250-0fd326f8daff
+caps.latest.revision: 26
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Determine Whether the Change Data Is Ready
   In the control flow of an [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] package that performs an incremental load of change data, the second task is to ensure that the change data for the selected interval is ready. This step is necessary because the asynchronous capture process might not yet have processed all the changes up to the selected endpoint.  
 
 > [!NOTE]  
@@ -247,7 +247,7 @@ manager: "jhubbard"
   
 #### To configure an optional Script task to log an error condition  
   
-1.  If you want to report the error or timeout by writing a message to the log, configure logging for the package. For more information, see [Enable Package Logging in SQL Server Data Tools](../../integration-services/performance/enable-package-logging-in-sql-server-data-tools.md).  
+1.  If you want to report the error or timeout by writing a message to the log, configure logging for the package. For more information, see [Enable Package Logging in SQL Server Data Tools](../../integration-services/performance/integration-services-ssis-logging.md#ssdt).  
   
 2.  Inside the For Loop container, add a Script task.