Merge pull request #1167 from douglaslMS/ssis-cons-mon0410

Consolidated 19 topics into others, deleted, redirected.

Author: v-thepet

.openpublishing.redirection.json

@@ -361,6 +361,101 @@
   {
    "source_path" : "docs/integration-services/variable-grid-options.md",
    "redirect_url": "/sql/integration-services/variables-window",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/service/configure-the-integration-services-service-as-a-cluster-resource.md",
+   "redirect_url": "/sql/integration-services/service/integration-services-ssis-in-a-cluster",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/view-events-for-the-integration-services-service.md",
+   "redirect_url": "/sql/integration-services/service/service/events-logged-by-the-integration-services-service",
+   "redirect_document_id": true
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/import-and-export-packages-ssis-service.md",
+   "redirect_url": "/sql/integration-services/service/service/package-management-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/import-package-dialog-box-ui-reference.md",
+   "redirect_url": "/sql/integration-services/service/service/service/package-management-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/export-package-dialog-box-ui-reference.md",
+   "redirect_url": "/sql/integration-services/service/service/service/package-management-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/package-backup-and-restore-ssis-service.md",
+   "redirect_url": "/sql/integration-services/service/service/service/package-management-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/view-integration-services-packages-in-sql-server-management-studio-ssis-service.md",
+   "redirect_url": "/sql/integration-services/service/service/service/package-management-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/manage-the-integration-services-service.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/set-the-properties-of-the-integration-services-service.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/grant-permissions-to-integration-services-service.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/configuring-the-integration-services-service-ssis-service.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/connect-to-integration-services.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/connect-to-a-remote-integration-services-server-ssis-service.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/configure-a-windows-firewall-for-access-to-the-ssis-service.md",
+   "redirect_url": "/sql/integration-services/service/service/integration-services-service-ssis-service",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/create-the-ssis-catalog.md",
+   "redirect_url": "/sql/integration-services/service/service/ssis-catalog",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/catalog-properties-dialog-box.md",
+   "redirect_url": "/sql/integration-services/service/service/ssis-catalog",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/backup-restore-and-move-the-ssis-catalog.md",
+   "redirect_url": "/sql/integration-services/service/service/ssis-catalog",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/upgrade-the-ssis-catalog-ssisdb.md",
+   "redirect_url": "/sql/integration-services/service/service/ssis-catalog",
+   "redirect_document_id": false
+  },
+  {
+   "source_path" : "docs/integration-services/service/service/always-on-for-ssis-catalog-ssisdb.md",
+   "redirect_url": "/sql/integration-services/service/service/ssis-catalog",
    "redirect_document_id": false
   }
 

docs/integration-services/add-copy-of-existing-package.md

@@ -1,25 +1,25 @@
----
-title: "Add Copy of Existing Package | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/14/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "integration-services"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-f1_keywords: 
-  - "sql13.dts.designer.addcopyexistingpackage.f1"
-helpviewer_keywords: 
-  - "Add Copy of Existing Package dialog box"
-ms.assetid: ed530b0d-438d-4c93-8e91-13f2b2b6a8b2
-caps.latest.revision: 13
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Add Copy of Existing Package
+---
+title: "Add Copy of Existing Package | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/14/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "integration-services"
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+f1_keywords: 
+  - "sql13.dts.designer.addcopyexistingpackage.f1"
+helpviewer_keywords: 
+  - "Add Copy of Existing Package dialog box"
+ms.assetid: ed530b0d-438d-4c93-8e91-13f2b2b6a8b2
+caps.latest.revision: 13
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Add Copy of Existing Package
   Use the **Add Copy of Existing Package** dialog box to add a copy of a package stored in [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)], the file system, or the SSIS Package Store to an [!INCLUDE[ssISnoversion](../includes/ssisnoversion-md.md)] project.  
 
 ## Options  
@@ -43,9 +43,7 @@ manager: "jhubbard"
 
 ## See Also  
  [Save Copy of Package](http://msdn.microsoft.com/library/7b44c0d7-d8fa-4491-8836-0899f621d3a8)   
- [Import Package Dialog Box UI Reference](../integration-services/service/import-package-dialog-box-ui-reference.md)   
- [Export Package Dialog Box UI Reference](../integration-services/service/export-package-dialog-box-ui-reference.md)   
  [Save Packages](../integration-services/save-packages.md)   
- [Import and Export Packages (SSIS Service)](../integration-services/service/import-and-export-packages-ssis-service.md)  
+ [Integration Services Service (SSIS Service)](../integration-services/service/integration-services-service-ssis-service.md)
 
 

docs/integration-services/install-windows/install-integration-services.md

@@ -1,29 +1,29 @@
----
-title: "Install Integration Services | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/14/2017"
-ms.prod: "sql-server-2016"
-ms.reviewer: ""
-ms.suite: ""
-ms.technology: 
-  - "integration-services"
-ms.tgt_pltfrm: ""
-ms.topic: "article"
-helpviewer_keywords: 
-  - "Integration Services, installing"
-  - "SSIS, installing"
-  - "installing Integration Services, about installing Integration Services"
-  - "SQL Server Integration Services, installing"
-  - "Setup [Integration Services], about installing Integration Services"
-  - "installing Integration Services"
-  - "Setup [Integration Services]"
-ms.assetid: bd20fd3a-414b-4581-959d-ebba4ddf5a55
-caps.latest.revision: 106
-author: "douglaslMS"
-ms.author: "douglasl"
-manager: "jhubbard"
----
-# Install Integration Services
+---
+title: "Install Integration Services | Microsoft Docs"
+ms.custom: ""
+ms.date: "03/14/2017"
+ms.prod: "sql-server-2016"
+ms.reviewer: ""
+ms.suite: ""
+ms.technology: 
+  - "integration-services"
+ms.tgt_pltfrm: ""
+ms.topic: "article"
+helpviewer_keywords: 
+  - "Integration Services, installing"
+  - "SSIS, installing"
+  - "installing Integration Services, about installing Integration Services"
+  - "SQL Server Integration Services, installing"
+  - "Setup [Integration Services], about installing Integration Services"
+  - "installing Integration Services"
+  - "Setup [Integration Services]"
+ms.assetid: bd20fd3a-414b-4581-959d-ebba4ddf5a55
+caps.latest.revision: 106
+author: "douglaslMS"
+ms.author: "douglasl"
+manager: "jhubbard"
+---
+# Install Integration Services
   [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] provides a single Setup program to install any or all of its components, including [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]. Through Setup, you can install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] with or without other [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] components on a single computer.    
 
  This topic highlights important considerations that you should know before you install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]. Information in this topic will help you evaluate the installation options so that you can make selections that result in a successful installation.    
@@ -54,14 +54,14 @@ manager: "jhubbard"
 > [!NOTE]    
 >  In previous versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], by default when you installed [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] all users in the Users group had access to the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service. When you install [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)], users do not have access to the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service. The service is secure by default. After [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is installed, the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] administrator must run the DCOM Configuration tool (Dcomcnfg.exe) to grant specific users access to **SQL Server Integration Services 13.0**.    
 >     
->  For instructions on how to grant permissions, see [Grant Permissions to Integration Services Service](../../integration-services/service/grant-permissions-to-integration-services-service.md).    
+>  For instructions on how to grant permissions, see [Integration Services Service (SSIS Service)](../../integration-services/service/integration-services-service-ssis-service.md).    
     
  If you are using the Setup Wizard to install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], you will use a series of pages to specify components and options. The following table lists only those pages in the Setup Wizard where the options that you select affect your installation of [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]:    
 
 |Page|Recommendations|    
 |----------|---------------------|    
 |**Feature Selection**|Select **Integration Services** to install the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service and to run packages outside the design environment.<br /><br /> For a complete installation of [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], together with the tools and documentation for developing and managing packages, select both **Integration Services** and the following **Shared Features**:<br /><br /> -<br />                    **SQL Server Data Tools** to install the tools for designing packages.<br /><br /> -<br />                    **Management Tools - Complete** to install [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] for managing packages.<br /><br /> -<br />                    **Client Tools SDK** to install managed assemblies for [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] programming.<br /><br /> Many data warehousing solutions also require the installation of additional [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] components, such as the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)], [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssASnoversion](../../includes/ssasnoversion-md.md)], and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)].<br /><br /> **Installing on a 64-bit Computer** On a 64-bit computer, selecting **Integration Services** installs only the 64-bit runtime and tools. If you have to run packages in 32-bit mode, you must also select an additional option to install the 32-bit runtime and tools:<br /><br /> -If the 64-bit computer is running the x86 operating system, select **SQL Server Data Tools** or **Management Tools - Complete**.<br /><br /> -If the 64-bit computer is running the [!INCLUDE[vcpritanium](../../includes/vcpritanium-md.md)] operating system, select **Management Tools - Complete**.<br /><br /> **Installing on a Dedicated Server for ETL** To use a dedicated server for extraction, transformation, and loading (ETL) processes, we recommend that you install a local instance of the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] when you install [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]. [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] typically stores packages in an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)] and relies on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent for scheduling those packages. If the ETL server does not have an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], you will have to schedule or run packages from a server that does have an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)]. This means that the packages will not be running on the ETL server, but instead on the server from which they were started. As a result, the resources of the dedicated ETL server are not being used as intended. Furthermore, the resources of other servers may be strained by the running ETL processes<br /><br /> <br /><br /> Note: Some [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] components that you can select for installation on the **Feature Selection** page of the Setup Wizard install a partial subset of [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] components. These components are useful for specific tasks, but the functionality of [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] will be limited. For example, the **Database Engine Services** option installs the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] components required for the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Import and Export Wizard. The **SQL Server Data Tools** option installs the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] components required to design a package, but the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is not installed and you cannot run packages outside of [!INCLUDE[ssBIDevStudio](../../includes/ssbidevstudio-md.md)]. To ensure a complete installation of [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], you must select **Integration Services** on the **Feature Selection** page.|    
-|**Instance Configuration**|Any selection that you make on the **Instance Configuration** page does not affect [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] or the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service.<br /><br /> You can only install one instance of the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service on a computer. You connect to the service by using the computer name.<br /><br /> By default, the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is configured to manage packages that are stored in the **msdb** database in the instance of the Database Engine that is installed at the same time as [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]. If an instance of the Database Engine is not installed at the same time as [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is configured to manage packages that are stored in the **msdb** database of the local, default instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)]. To manage packages that are stored in a named instance or a remote instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], or in multiple instances of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], you have to modify the configuration file. For more information about how to modify this configuration file, see [Configuring the Integration Services Service &#40;SSIS Service&#41;](../../integration-services/service/configuring-the-integration-services-service-ssis-service.md).|    
+|**Instance Configuration**|Any selection that you make on the **Instance Configuration** page does not affect [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] or the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service.<br /><br /> You can only install one instance of the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service on a computer. You connect to the service by using the computer name.<br /><br /> By default, the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is configured to manage packages that are stored in the **msdb** database in the instance of the Database Engine that is installed at the same time as [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]. If an instance of the Database Engine is not installed at the same time as [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is configured to manage packages that are stored in the **msdb** database of the local, default instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)]. To manage packages that are stored in a named instance or a remote instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], or in multiple instances of the [!INCLUDE[ssDE](../../includes/ssde-md.md)], you have to modify the configuration file. For more information about how to modify this configuration file, see [Integration Services Service &#40;SSIS Service&#41;](../../integration-services/service/integration-services-service-ssis-service.md).|    
 |**Server Configuration**|Review the settings for the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service on the **Service Accounts** tab of the **Server Configuration** page.<br /><br /> If Windows 7 or Windows Server 2008 R2 is installed, the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is registered to run under the NT Services\MsDtsServer130 virtual account, and the **Startup Type** is **Automatic**.  You do not have to enter a password for the virtual account. If Microsoft Vista or Windows Server 2008 is installed, the [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] service is registered to run under the built-in Network Service account, and the **Startup Type** is **Automatic**. You do not have to enter a password for the built-in Network Service account.|    
 
  By default, in a new installation, [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] is configured not to log events that are related to the running of packages to the Application event log. This setting prevents too many event log entries when you use the Data Collector feature of [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]. The events that are not logged are EventID 12288, "Package started," and EventID 12289, "Package finished successfully." To log these events to the Application event log, open the registry for editing. Then, in the registry, locate the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\130\SSIS node, and change the DWORD value of the LogPackageExecutionToEventLog setting from 0 to 1.