Legacy Package Deployment1:package Deployment Model Overview

The so-called legacy package Deployment model refers to the package Deployment model, which appears earlier compared to project Deployment model, Management is rough, Legacy (Traditional). Under the package Deployment model, you can create a package configurations that stores Property/value Pair. Configure the properties of project, generate deployment utility, and use deployment utility to deploy packages to the file System or integration Servic.

Package Deployment Model Overview:

SQL Server integration Services includes tools and wizards, it simple to deploy packages from the development com Puter to the production server or to other computers.

There is four steps of the package deployment process:

1. The first optional step is optional and involves creating package configurations that update properties of PA Ckage elements at run time. The configurations is automatically included when you deploy the packages.

2. The second step is to build the integration Services project to create a package deployment utility. The deployment utility for the project contains the packages, the want to deploy

3. The third step are to Copy the deployment folder that is created when you built the integration Services project to the target computer.

4. The fourth step is to run, on the target computer, the package installation Wizard to install the packages T o The file system or to an instance of SQL Server.

related Tasks

For information on how to create a deployment utility, see Create a deployment utility.

For information what to deploy packages using the deployment utility, see deploy packages by using the deployment Uti Lity.

For information on how to create the package configurations, see Create Package configurations.

Reference Documentation:

https://msdn.microsoft.com/en-us/library/ms137592 (v=sql.110). aspx

Legacy Package Deployment1:package Deployment Model Overview