Knight's Microsoft SQL Server 2012 Integration Services 24-Hour Trainer

Chapter 53

Deploying Packages to the Package Catalog

In SQL Server 2005, 2008, and still in the package deployment model, you would deploy packages into SQL Server’s msdb database or to the filesystem. Now, in SQL Server 2012’s project deployment model, you deploy to the SSIS catalog (ssisdb database). Deploying to this model enables you to activate some of the newer features in SSIS, like environments and parameterization of packages (to name just a few). Deploying packages is simple using the Integration Services Deployment Wizard.

NOTE Because the older package deployment model is legacy, deploying packages to this model is not covered in this lesson in length.

Using the Deployment Wizard

The Deployment Wizard is the easiest way to deploy packages to the catalog. You can access the wizard through SSDT by right-clicking a project and selecting Deploy. You can also access it through Management Studio or by double-clicking an .ISPAC file. The wizard installs your packages by asking the administrator a few questions. It also creates the .ISPAC file, which is a single file that can be handed to a customer or to the DBA to install your project.

Once the wizard is open and you bypass the opening screen, you’re asked which server and folder you want to deploy your project to (see Figure 53-1). (A folder is a container for a number of projects.) Click Next and Deploy to push your packages to the server. You’ll also be warned if the packages are already on the server. Remember ...