Add xml config file on the SSDT 2012 and upper version of the SSDT

The 2012 release of SSIS introduces a new model for configuration and deployment called the Project deployment model. As part of that change, the old way of doing configuration (environment, XML, parent package, registry, and table) is not an option. In the project deployment model, we get parameters and environments.

Read package configuration: http://bageshkumarbagi-msbi.blogspot.com/2014/12/package-configuration.html

There is two way to add file configuration.

1.       Convert to Package Deployment Model or

2.       Use configuration properties

In SSIS 2005 and 2008, we could access package configurations by simply right-clicking on an empty space in the package and selecting Package Configurations similar to what is shown below.

However, if we are using SSIS 2012 or 2014 in project deployment mode (the default setting for new projects), this option no longer exists.

   

1^st way

We need to convert this to ‘Convert to Package Deployment Model’

  

We will get the wizard to convert this package deployment.

   

Click ok

 

  

Click ok.

Now we are able to see the package configuration on the package.

  

2^nd  way

Even though the option no longer appears in this shortcut menu, it can still be accessed directly by using the package (configuration properties) properties. In the package properties window, there is a collection called Configurations that will allow us to set one or more package configurations.

Clicking on the ellipsis next to this collection brings up the familiar package configurations menu, in which we can create XML, environment variable, or table storage configurations.

   

There are a couple of things to keep in mind on using package configurations in SSIS 2012 and beyond. First of all, we can use package configurations in addition to newer configuration methods (including package parameterization and SSIS environments). However, my recommendation is that we choose just one configuration method per project to avoid confusion or conflicting values. Also, be aware that the way package configuration values are logged differs from the way package parameter and SSIS environment values are logged in the SSIS catgol