1189
Chapter 52: Building, Deploying, and Managing ETL Workfl ows in Integration Services
52
production systems at this moment that utilize this deployment model, and therefore this
method deserves careful consideration.To access Package confi gurations, fi rst make sure that your project is in Package
Deployment Mode. The words (package deployment model) will be beside the project name
in Solution Explorer. If it is not in package deployment mode, change it by right clicking
on the project and selecting Convert to Package Deployment Model from the menu.
Open the Confi gurations dialog box by going to the SSIS menu. Select SSIS ➪ Package
Confi gurations. Confi gurations are applied to the package in the order they are listed here.
To add a new confi guration, ensure that confi gurations are enabled by clicking the box
beside Enable package confi gurations, and click Add to start the Package Confi guration
Wizard. Choose the desired Confi guration Type (storage location). There are essentially
three categories to consider:■ (^) Registry and Environment Variable: These types can hold a single property only.
■ XML File and SQL Server Table: Each of these confi guration types can hold any
number of property settings.
■ Parent Package Variable: Enables access to the contents of a single variable from
the calling package.
On Indirect Configurations
Although complicated, you can effectively use fi le confi gurations to make File Deployments to internal
environments, such as Test, QA, and Production, seamless. At the beginning of development, you can
set up an indirect File confi guration to reference an Environment Variable on each server, with those
environment variables having the same name. The Environment variable on each server contains the
location of the XML File on that server, which in turn contains the rest of the confi gurations for that
specifi c server. After you successfully implement the confi gurations, you can deploy packages to each
environment without the developer needing to manually confi gure a connection manager again. See
“Adding Package Confi gurations” at http://msdn.microsoft.com/en-us/library/ms365339
.aspx for more information.
Most confi guration types enable the storage location to be identifi ed either directly or via
an environment variable. The environment variable approach can be useful when the stor-
age location (such as fi le directory) must change between environments. When the con-
fi guration type and location are specifi ed, the Select Properties to Export option enables
the properties that change between environments to be chosen. Complete the wizard by
reviewing the selections and giving the confi guration a name.
You can reuse confi gurations between packages if the names of the objects containing the
properties to be set are the same between packages. For example, packages that use the
same names for their connection managers could share a confi guration that sets server
c52.indd 1189c52.indd 1189 7/31/2012 10:29:31 AM7/31/2012 10:29:31 AM
http://www.it-ebooks.info