1184
Part IX: Business Intelligence
Things to consider:■ Parameters can be used only with the Project Deployment model.■ (^) Parameters are read-only at design time; their values can be set at deployment and
execution. Package Parameter values can be set by Execute Package tasks.
■ (^) Parameters can be scoped to the Project level or the Package level.
■ To distinguish them from Variables, Parameters are prefi xed by a $, followed
by either Project or Package to indicate the scope. Thus, if there were a Project
Parameter, a Package Parameter, and a User Variable, each with the name Foo, then
they appear as $Project::Foo , $Package::Foo, and User::Foo, respectively, under the
variables node in the Expression Builder.
You create and confi gure project parameters in the Project Parameters Editor, shown in
Figure 52-12. To open this, click the project.params button in Solution Explorer. It is
located underneath the Miscellaneous folder.
To create Package level parameters, click on the third tab in the SSIS designer, between the
Data Flow and the Event Handlers tabs. In both of these editors, click on Add Parameter
button to add a new parameter.
FIGURE 52-12
The Project Parameters Editor.
The options for confi guring Parameters are as follows:
■ (^) Name: Give the parameter a meaningful name.
■ (^) Datatype: Assign the proper datatype.
■ (^) Value: Default Design time value.
■ (^) SensitiveOnServer: All SSIS Projects are deployed to the SSIS catalog. The
SensitiveOnServer fl ag indicates whether the parameter receives special treatment
to hide its value. If fl agged yes, it is encrypted at the time of deployment and
masked in UI, and its value is not available in logs.
■ (^) Required: This fl ag signifi es whether the value of the Parameter must be changed
from its Default design-time value at run time. This is a useful property, which is
c52.indd 1184c52.indd 1184 7/31/2012 10:29:30 AM7/31/2012 10:29:30 AM
http://www.it-ebooks.info