The SSIS Catalog (SSISDB) was first introduced in SQL Server 2012 and enabled faster and easier SSIS package deployment (particularly in SQL Server failover clusters) since (by its use) all packages and metadata would now live inside its database, and any other remaining metadata within the instance. This is, of course, a huge improvement over traditional SSIS Package store deployment (and covered in future posts), but for now, we will focus solely on simple standalone deployment.
Create the SSIS Catalog on your SQL Instance
Creating the SSIS Catalog for your instance is fairly straightforward, simply navigate to (and right-click) the Integration Services Catalog node in your instance via SSMS and select Create Catalog…
The Create Catalog wizard is a single page and all you really need to provide is a password which will be used to protect the encryption key which secures your SSIS Catalog secrets.
Note also in the wizard above, the panel message stating “You can manage the encryption key by creating a backup. If you migrate or move the Integration Services catalog to another SQL Server instance, you can restore the key to regain access to encrypted content“. The relevance of this operation will become obvious in later posts when we discuss deployment of the SSIS Catalog to an Availability Group.
You might also notice the option Enable automatic execution of Integration Services stored procedure at SQL Server startup. All this does is to automatically execute (or not) the SSIS cleanup job whenever the instance is started. You can view the automatic startup state of stored procedures by running the following code segment:
SELECT name,is_auto_executed FROM sys.procedures
If you want to change the automatic startup state of stored procedures then you can use the sp_procoption stored procedure.
Once your SSIS Catalog is created you should see the Catalog within the Integration Services Catalog node, a database called SSISDB under the Databases node, and a job called SSIS Server Maintenance Job under the SQL Server Agent Jobs node.
As you have seen, configuring your SQL Server for the SSIS Catalog is incredibly easy and regardless of your current SSIS package deployment strategy is something that you should use going forward (and also consider migrating your existing packages). In future posts, we will also cover SSIS Catalog deployment in a highly available configuration via an Availability Group (I will add the links here once they are published).
Want more Bitesize SSIS tips? Then keep an eye open for the other posts in the series!