In a previous post, SQL Server Integration Services tools to have – Expression Editor & Tester, I discussed a tool that is extremely useful for preparing and maintaining expressions. Expressions are extremely common now to enforce dynamic and mobile SSIS packages. Tools like the editor make that task more efficient. Another tool that has recently been provided on Codeplex is the Configuration File Editor.

Overview

Given an SSIS package that consists of two packages, Package.dtsx and Package1.dtsx, the packages have a configuration file that allows a setting in Packge.dtsx for the execute package task. The value that can be altered is the package name property. This makes the task of the initiating package to be more dynamic on what package it can call.

In a production setting and more commonly in my own practices, Business Intelligence Studio or any version of Visual Studio is not allowed as a standard installation. This is to prevent unwanted use of resources on the server. Servers should be built and maintained for their distinct purpose. A database server’s purpose is not to be a development ready machine. SSIS Configuration Editor assists in not having those IDEs on the servers by allowing a thin and simple method to configure configuration files.

In the initial screens of the editor, the server and the package folder are shown. The package source is also available for both a SQL Server and File System store.

The first nice feature is the evaluation of the configuration file. Notice the red font in the above image. This indicates the configuration file is missing or there are permission issues getting to the file. Even if you do not intend to edit the files, this feature can prove valuable to validate the configuration files on a scheduled basis.

Once the issue with the file is resolve, the font returns to black. Now, the editor cannot edit the internals of the configuration files. The purpose is to have multiple configuration files and a quick method for you to alter the configuration file that is used per that package. In a transport or mobile package setting, this is extremely useful.