April 4, 2016 at 2:11 pm
Hello SSC friends,
I have been tasked with creating a dynamic SSIS config file for several packages. I will need to pass in different environment variables for FTP sites and environments (dev, qa, uat, prod, etc). I am not sure how to accomplish this.
Does anyone have experience with this? And if so, can you please point me in the right direction?
Thank you all in advance for your help!
The are no problems, only solutions. --John Lennon
April 4, 2016 at 2:16 pm
Which version of SSIS are you using?
If 2012 or later, there is no need to use a config file for this.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
April 4, 2016 at 2:26 pm
Phil Parkin (4/4/2016)
Which version of SSIS are you using?If 2012 or later, there is no need to use a config file for this.
Config files are still used with SSIS 2012, 2014, and believe 2016 it has not changed either...if you are using package deployment model. Only if you are using Project Deployment model that you can utilize configuration within the SSISDB catalog.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 4, 2016 at 2:31 pm
SQLTougherGuy (4/4/2016)
Hello SSC friends,I have been tasked with creating a dynamic SSIS config file for several packages. I will need to pass in different environment variables for FTP sites and environments (dev, qa, uat, prod, etc). I am not sure how to accomplish this.
Does anyone have experience with this? And if so, can you please point me in the right direction?
Thank you all in advance for your help!
I thought there was a piece on using configuration files in SSIS in the Stairway series but do not see one right off.
The basic documentation might give you a good start: Step 2: Enabling and Configuring Package Configurations. This has not changed much since SSIS 2005.
This is also a good walk through on use of the configuration files as well: Understanding Integration Services Package Configurations
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
April 4, 2016 at 2:39 pm
Hi Phil - I am using 2014. Which other methods do you recommend for this?
The are no problems, only solutions. --John Lennon
April 4, 2016 at 5:23 pm
SQLTougherGuy (4/4/2016)
Hi Phil - I am using 2014. Which other methods do you recommend for this?
I recommend the following:
a) Use the project deployment model, to take advantage of the benefits offered by having your packages in SSISDB (eg native logging, project-level connections and parameters)
b) Use SSISDB 'Environments' to hold the values of the various config items. See here[/url].
Once you have the environments set up, you can 'Configure' your SSIS project and package parameters to use the values of the environment variables at run time.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply