SQL 2012 comes with a complete new structure to handle SSIS projects in your SQL environment. It’s still allowed to deploy SSIS projects in the “old school” style, but I would recommend to learn the new way very soon. It’s giving you more flexibility and most certain does what we have been building by hand all these years. Or at least for me, I created a SSISEnvironment database that holded package configurations and made this as flexible as possible by building my packages in such a way that only one Windows environment variable could change the entire package running environment from development to production and back….. And now this is the new SQL 2012 standard, thanks to I think a lot of others that where using this setup in the old school SSIS deployment.
Enough history, let’s go!
The new SSIS Project deployment is only working when you have CLR enabled on your SQL Server instance, you can do this by running the following script:
After CLR is enabled you can create your SSIS Catalog from SQL Server Management Tool:
When the catalog is created you can create folders in the catalog. One of the advantage of using folders in a SQL 2012 SSIS Catalog is that now you can set security on these folders so you can target them to specific administrators that need to manage a specific project.
And thats is all folks, the SSIS Project catalog is ready to deploy a SSIS project to. But how to do that will be explained in a other blog.