The basis steps of creating and using a SSIS 2016 Control Flow Template (I will call them CFT’s in the following) were described in my first blog post around this topic (>>read it again here<<).
How to configure?
In this post I would like to have a deeper look into the configuration options of CFTs. The edit dialog of a template instance can be opened by selecting the context-menu entry “Edit…” of that instance.
What to configure?
The dialog that is opened afterwards shows all the possible (at current date) configuration options of SSIS templates. The content-parts of the template are grouped into either Executables, Properties, Variables or Connection Managers.
- Executables – Entries listed here are the controls / components that are contained in the template itself. In my example you’ll see the three SQL script tasks and beneath their properties and eventually defined variables.
- Properties – Those are the “high-level” properties of the template itself (in my case the template container is a sequence container)
- Variables – You’ll find the variables of your template in this part of the configuration area. In my demo I added one variable to the template. This variable and it’s properties are listed here.
- Connection Manager – In the separate tab for Connection Managers (CM) you’ll find the CMs defined in your template. In the screenshot you can see the CM from the template and the properties that are available for configuration.
How to actually configure it..?
Property values (in this example for Connection Managers) can be overwritten if you select the checkbox and write the new value in the “value” column. Yes – no error in the text. In SQL Server 2016 CTP3 only entered values are possible. No expression binding, no binding to variable values! Maybe this will be changed in a future CTP or RTM version!
Property values for Executables can be overwritten by simply selecting the property in the left Treeview and entering the new value in the appropriate column.
If your configuration changes are done – just accept them by clicking OK and storing the template configuration settings.
Current observed limitations & Wrap-Up:
- In the current implementation (CTP3) all properties [or at least a set of defined by Microsoft] are available for configuration. It is not possible for a template developer to define a list of required configuration options. That would really enhance the development experience.
- Configuration values can only be entered as text. No expression, no variable bindings are currently supported.
- If you changed configuration values in a template you do not really see it in the SSIS package. No visual hint or something like this!
- CFT – a first implementation. Seems like a good start but – for my opinion – it needs some more polishing (especially expressions and variable bindings in configuration context)!
- One of the possible usage scenarios I could image that CFTs will work are the “exchange” of for example Hive-Scripts or external batch files in an “Execute Process Task”.