CODEWITHSUNDEEP
sql-serverssis
Steve
Steve

Reputation: 579

SSISDB and Environments

I am attempting to set up an SSIS Project Deployment Model with Environment specific variables. I am in part using this tutorial as a guideline, SSIS Parameters and Environments, as well as Deploy Integration Services (SSIS) Projects and Packages.

Do Environments not work like I would plausibly expect them to? I need different connection strings for different environments. So I created those project level parameters in the SSIS solution and set the connection managers to use these Expressions. I deployed the project to the database and created the Environments I wanted (Development, Production)

Now I would expect when I configure the SQL job and set the environment as I need to, the correct variables would be pulled for the connection strings I need. As you can see in the screen shot SSMS is complaining that the development parameters don't exist in the Production environment (duh!).

So I have to kind of wonder, have I gone down the wrong rabbit hole?

Production - Use these connection strings Development - Use these other connection strings

enter image description here

Upvotes: 1

Views: 245

Answers (1)

Piotr Palka
Piotr Palka

Reputation: 3159

You should have only one set of parameters in the SSIS project.
So instead of two parameters ODSDevelopment and ODSProduction you will have one parameter ODSConnectionString.
Then in the environments you will set up ODSConnectionString to point to Production or Development, depending on the environment.
In other words, word 'Production' may be used only in the environment name, but never in the parameter name.

Upvotes: 3

Related Questions