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

Section 9

Administering SSIS

• Lesson 52: Creating and Configuring the SSIS Catalog
• Lesson 53: Deploying Packages to the Package Catalog
• Lesson 54: Configuring the Packages
• Lesson 55: Configuring the Service
• Lesson 56: Securing SSIS Packages
• Lesson 57: Running SSIS Packages
• Lesson 58: Running Packages in T-SQL and Debugging Packages
• Lesson 59: Scheduling Packages

Chapter 52

Creating and Configuring the SSIS Catalog

One of the most significant differences between previous versions of SSIS and SQL Server 2012 is the introduction of the SSIS catalog. The catalog only applies for those who are in the project deployment model and gives you many new features for administering and configuring packages. It also enables you to run packages in T-SQL or through PowerShell.

Creating the Catalog

Behind the scenes, a catalog is simply a database where your packages are stored and configured. As packages run, it stores operational information about the packages’ run and any errors. Because the packages are in a database called SSISDB, much of their management can be done through T-SQL or PowerShell, that’s in addition to the normal way of managing them, which is through Management Studio.

The easiest way to create the SSIS catalog (you have only one catalog per database instance) and its accompanying database is with Management Studio. In Management Studio, connect to your database engine and navigate to the Integration Services node in Object Explorer. Right-click the Integration Services ...