Package Configuration File Editor
This utility identifies package configuration paths that are not valid and enables you to correct the paths without having to open the package in Business Intelligence Development Studio (BIDs).
Package configuration paths can become invalid when packages are moved from development environments to production environments. Typically, people don’t have development/Client tools like BIDS in their Production and this tool targets those environments.
You can load packages into the tool that are stored in SQL Server, the SSIS Package Store, or in a file system.
In this release of the utility, you cannot do the following:
- Load packages that are protected by a password (protection level is set to EncryptAllWithPassword/EncryptSensitiveWithPassword).
.NET Framework 3.5
SSIS 2008 or 2008 R2
Supported Operating Systems
Windows 7, XP, 2008, Vista, 2008
Features in Current Release
- Load a package stored in the SSIS Package Store.
- Load a package stored on a server. Click the ellipsis button to browse for packages in a SQL Server folder.
- Use Windows Authentication, or provide a username and password, to connect to the server.
- Load packages stored in server subfolders.
- Load packages stored in a file system folder. Subfolders are not implemented in this version of the tool.
- Easily spot a configuration path that is not valid and edit the path in the tool. When you click
Apply Changes, the updated configuration path is stored in the package.
Additional Resources for Package Configurations
Best Practices for Integration Services Configurations
Defining a Configuration Approach for Integration Services Packages
Understanding Integration Services Package Configurations