CODEWITHSUNDEEP
ssissql-server-2012package
Henrov
Henrov

Reputation: 1610

package configurations vs project configurations

I am wondering what considerations can lead to choosing package-configurations over project-configurations (or vice-versa) on Sql Server 2012.

I for example was told that using package-configurations it was easier to migrate ETL's from one machine to another.

edit: the question is about package configurations vs project configurations, not about package-parameters vs project parameters

Upvotes: 0

Views: 445

Answers (2)

Henrov
Henrov

Reputation: 1610

It seems there is nothing that package-configuration can do which Project-configuration cannot do. The opposite is true however.

Upvotes: 0

Tab Alleman
Tab Alleman

Reputation: 31785

If multiple packages in the same project are going to share the same parameter, and you want to be able to change it once and have that change affect all packages, you would make it a project parameter.

If only one package should use it, and you should be able to change it without affecting other packages in the same project, then you should make it a package parameter.

This is the only factor I consider when deciding.

Upvotes: 1

Related Questions