Database Reference
In-Depth Information
CHAPTER 17
Configuration
SQL Server 2012 introduced a new, parameter-based configuration model for SSIS. This
new model is meant to simplify the configuration process and make it easier for users to
identify where values are coming from at runtime. Although 2005/2008-style package
configurations are still supported in SQL Server 2012 and SQL Server 2014, the two
configuration models are not meant to be mixed. In fact, the menu option to use them
will only appear when you are using the file deployment model and on packages that
have been upgraded from previous versions. New packages created in SQL Server 2014
will use the new parameter model by default.
This chapter describes the new parameter model and how it can be used to configure
package properties at runtime. We'll look at how parameters are exposed in the SSIS
Catalog and how you can set parameter values as part of your build process using Visual
Studio configurations. Finally, we'll look at design patterns that you can use to augment
the functionality provided by the built-in parameter model, providing dynamic runtime
configuration.
Parameters
SSIS parameters allow packages to define an explicit contract, much like function para-
meters do in programming languages like C#. Unlike package configurations, paramet-
ers are exposed to the callers, like SQL Server Agent, or the Execute Package task, so
users are able to see exactly what a package needs to run. Parameters are essentially
read-only package variables in a special namespace. They follow the same type system
as package variables and will appear in all of the same UIs that variables do (for ex-
Search WWH ::
Custom Search