Export (0) Print
Expand All

Creating Package Configurations

Updated: 15 September 2007

You create package configurations by using the Package Configuration Organizer dialog box and the Package Configuration Wizard. (To access these tools, in Business Intelligence Development Studio, on the SSIS menu, click Package Configurations.)

ms141132.note(en-US,SQL.90).gifNote:
To become better acquainted with the concepts explained in this section, see Deploying Packages Tutorial and Lesson 3: Adding Package Configurations of Creating a Simple ETL Package Tutorial.

In the Package Configuration Organizer dialog box, you can enable packages to use configurations, add and delete configurations, and set the preferred order in which configurations should be loaded.

ms141132.note(en-US,SQL.90).gifNote:
When package configurations load in the preferred order, configurations load from the top of the list shown in the Package Configuration Organizer dialog box to the bottom of the list. However, at run time, package configurations might not load in the preferred order. In particular, Parent Package Configurations load after configurations of other types.

From the Package Configuration Organizer dialog box, you run the Package Configuration Wizard, which guides you through the steps to create a configuration. On the wizard pages, you choose the configuration type, select whether you want to access the configuration directly or use environment variables, and select the properties to save in the configuration.

ms141132.note(en-US,SQL.90).gifNote:
If multiple configurations set the same object property, the value loaded last is used at run time.

The following examples show the target properties of a variable and a package as they appear on the Completing the Wizard page of the Package Configuration Wizard.:

\Package.Variables[User::TodaysDate].Properties[RaiseChangedEvent]

\Package.Properties[MaximumErrorCount]

\Package.Properties[LoggingMode]

\Package.Properties[LocaleID]

\Package\My SQL Task.Variables[User::varTableName].Properties[Value]

The configurations update these properties:

  • The RaiseChangedEvent property of user-defined variable, TodaysDate.
  • The MaximumErrorCount, LoggingMode, and LocaleID properties of the package.
  • The Value property of user-defined variable, varTableName, within scope of the task, My SQL Task.

The "\Package" represents the root, and periods (.) separate the objects that define the path to the property that the configuration updates. The names of variables and properties are enclosed in brackets. The term Package is always used in configuration, regardless of the package name; however, all other objects in the path use their user-defined names.

After the wizard finishes, the new configuration is added to the configuration list in the Package Configuration Organizer dialog box.

ms141132.note(en-US,SQL.90).gifNote:
The last page in the Package Configuration Wizard, Completing the Wizard, lists the target properties in the configuration. If you want to update properties when you run packages by using the dtexec command prompt utility, you can generate the strings that represent the property paths by running the Package Configuration Wizard and then copy and paste them into the command prompt window for use with the set option of dtexec.

The following table describes the columns in the configuration list in the Package Configuration Organizer dialog box.

Column Description

Configuration Name

The name of the configuration.

Configuration Type

The configuration type.

Configuration String

The location of the configuration. The location can be a path, an environment variable, a registry key, a parent package variable name, or a table in a SQL Server database.

Target Object

The name of the object with a property that has a configuration. If the configuration is an XML configuration file, the column is blank, because the configuration can update multiple objects.

Target Property

The name of the property. If the configuration writes to an XML configuration file or a SQL Server table, the column is blank, because the configuration can update multiple objects.

Release History

15 September 2007

Changed content:
  • Added note about how package configurations load.

14 April 2006

Changed content:
  • Added note to describe behavior when multiple configurations apply to the same object.

5 December 2005

Changed content:
  • Added a note about using the wizard to generate property paths.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft