At this point, you understand the options for moving an SSIS framework to the latest version of SSIS, and you've upgraded the logging portion of the framework using a hybrid approach. The final step in the framework upgrade is handling your configurations. Let's walk through an existing configuration implementation and how you can upgrade it by combining your existing implementation with the standard SSIS framework.
A typical "old-school" configuration scheme is described in the SSIS PDS book or in this blog post here: http://jessicammoss.blogspot.com/2008/05/ssis-configuration-to-configuration-to.html. Starting in SSIS 2012, the configuration scheme uses environments and parameters when using the Project Deployment Model, as discussed here: http://msdn.microsoft.com/en-us/library/hh213290(v=sql.110).aspx.
In both scenarios, the core ideas in a configuration scheme are:
- Provide the ability to move packages through environments without having to touch the packages
- Provide one location where connection strings / variables are stored, so in case a value changes, you don't have to change the value in multiple places
To enable our hybrid approach, we will utilize the SSIS 2012+ catalog as our "master" version of the configuration values and modify the previous framework to use its data. This example counts on the following assumptions. If your system is different, you may need to make some modifications to the implementation described here.
- Assumption for the old framework: All configuration entries modify Variables, rather than Connections or other object types.
- Assumption for the new framework: You have a CommonConfigurations environment on each server that holds your values for your development, test, and production servers, as well as an environment for each package that would have its own package level values.
To tie the two systems together, we will use the environments stored in the 2012+ catalog to pass to the earlier framework. The earlier framework retrieves all of its information from a table called dbo.SSIS Configurations, so we can just replace that table with a view that points to the new catalog!
Start by renaming your old table to [SSIS Configurations Old]:
EXEC sp_rename 'dbo.SSIS Configurations', 'SSIS Configurations Old';GO
Next, create a view named [SSIS Configurations] that reads from the SSIS catalog:
CREATE VIEW dbo.[SSIS Configurations]ASSELECT CAST(e.name AS NVARCHAR(255)) as ConfigurationFilter, CAST(ev.value AS NVARCHAR(255)) AS ConfiguredValue, CAST('\Package.Variables[User::' + ev.name + '].Properties[Value]'AS NVARCHAR(255)) AS PackagePath, CAST(ev.type AS NVARCHAR(20)) AS ConfiguredValueTypeFROM [SSISDB].[catalog].[environment_variables] evLEFT JOIN [SSISDB].[catalog].[environments] eON ev.environment_id=e.environment_idGO
Compare the output from SSIS Configurations and SSIS Configurations Old, and add any additional variables needed to the environment in the SSIS catalog. From now on, you will add new configurations only to the new catalog. You have one place to keep the "master" values and you only change them in one place!
Keep in mind that based on your framework implementation, not all of this may be applicable. However, I hope that it gives you something to think about as you are evaluating your framework upgrade options!