October 28, 2014 at 2:49 pm
Are the run time package parameter values also stored in the integration Services Catalogs in SSIS 2012 project deployment model. I have ONE SSIS package deployed in SSISDB Catalog with package parameters from which i am trying to create two sql agent job steps with DIFFERENT parameter values. This can be easily done in package deployment model but I can't seem to find a way to do the same in the project deployment model. Any suggestions?
October 29, 2014 at 2:06 am
The easiest way (in my opinion) is to create two environments. Each environment has the same environment variable, but with a different value. In the catalog, the parameter is configured with this environment variable. In the SQL Agent job you can just choose the environment you need.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 29, 2014 at 12:02 pm
Koen Verbeeck (10/29/2014)
The easiest way (in my opinion) is to create two environments. Each environment has the same environment variable, but with a different value. In the catalog, the parameter is configured with this environment variable. In the SQL Agent job you can just choose the environment you need.
Koean,Thanks.
That sounds do-able work around. But I was rather looking for an actual solution. I am sure Microsoft thought about this. The proposed workaround can get pretty confusing/messy if you have a bunch of parameters and are actual implementing different Environment from the same the intergration services catalogs.
October 30, 2014 at 2:14 am
gravitysucks (10/29/2014)
Koen Verbeeck (10/29/2014)
The easiest way (in my opinion) is to create two environments. Each environment has the same environment variable, but with a different value. In the catalog, the parameter is configured with this environment variable. In the SQL Agent job you can just choose the environment you need.Koean,Thanks.
That sounds do-able work around. But I was rather looking for an actual solution. I am sure Microsoft thought about this. The proposed workaround can get pretty confusing/messy if you have a bunch of parameters and are actual implementing different Environment from the same the intergration services catalogs.
It's a matter of discipline. I find environments more visible and easy to configure than setting parameters directly in the Agent job.
Anyway, you can set parameters directly in the SQL Agent job. Go to configuration / parameters and supply values there.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply