Describes several SSIS deployment methods and ssis deployment methods.

Describes several SSIS deployment methods and ssis deployment methods.
Introduction

If you have developed a good SSIS package and can run it perfectly locally, each task will be highlighted with a green pass sign. In this case, you need to publish the package to a server and configure it properly to make it run at a specified time. As developers, we may not be able to do this directly in the production environment. This requires a development or test environment to complete the entire deployment test, because DBA sometimes does not allow you to directly access the production environment.

This article describes how to deploy packages locally to the server. The project deployment model introduced in SQLServer 2012 is no longer repeated, because the SSIS2012 reporting deployment model is also used for similar methods.

Reprinted please mark the Source: http://www.cnblogs.com/wenBlog/

Purpose

The deployed package has the following forms:

• The file system is stored in the folder you choose.
• The SSIS package is stored in a file system table managed by the SSIS service, in the-% Program Files % \ Microsoft SQL Server \ 100 \ DTS for SQL Server 2008 folder.
• The MSDB database is stored in the dbo. sysssispackages table.

Next, let's take a look at the four main deployment methods:

• Traditional Mode
• Manual mode
• Command Method
• Practical Methods

The methods are described in detail.

Traditional Mode

Use the built-in deployment method to publish a package to the server: first, SSISDeploymentManifest (SSIS project) is an XML file used to describe which packages need to be deployed to the server. If you double-click a project, a wizard will help you publish the package to the server.

Follow these steps:

Figure 1

Manual mode

 

For those who can remotely control the server (DBA ...), You can do anything manually, for example, manually deploying a package.

For those who prefer to process BIDS, the following operations can be performed:

Figure 2

Command Method

If you are a guy who loves command line very much, you can also directly use command line to deploy the package. The typical CMD line is as follows:

dtutil /FILE “C:\myPackages\myPackage.dtsx” /DestServer myServer /Copy SQL;myPackage

Note: The target package name does not contain the. dtsx extension.

Usage

 

Finally, I would like to introduce how to deploy the package to the server (using BIDS Helper ). A free plug-in. This small plug-in introduces a large number of features to BIDS, the most valuable of which is to simplify the deployment function.

Figure 3

 

The biggest advantage is that all files can be deployed at one time: Right-click your project and select deployment. All packages will be deployed.

Summary

This article briefly introduces several different methods for deploying packets to the server. Each of them gets the same result. Therefore, you can choose the most comfortable deployment method. You are also welcome to add new methods (TFS, SVN, github deployment, etc. are not described here)

 

References: https://msdn.microsoft.com/en-us/library/ms140117%28v= SQL .105%29.aspx