August 1, 2014 at 11:17 am
Hi,
I have done with the SSIS Package and it's working as expected in my local machine, I have one problem is that how I can give my XML configuration file path as input to my SSIS package dynamically during runtime, because in local Iām having in C:\Extract\Config.dtsconfig. But in higher environment the path will be different. Is there any way to set this configuration file path?
When I tried with .\Config.dtsconfig in Package Configuration Wizard on the cursor focusing out it's giving the pull path again.
Kindly Guide me.
___
Known Is An Drop,Unknown Is An Ocean....
Njoy Programming š
August 1, 2014 at 11:47 am
windows_mss (8/1/2014)
Hi,I have done with the SSIS Package and it's working as expected in my local machine, I have one problem is that how I can give my XML configuration file path as input to my SSIS package dynamically during runtime, because in local Iām having in C:\Extract\Config.dtsconfig. But in higher environment the path will be different. Is there any way to set this configuration file path?
When I tried with .\Config.dtsconfig in Package Configuration Wizard on the cursor focusing out it's giving the pull path again.
Kindly Guide me.
First a quick question, which version are you on?
The config is initialized before the execution so no luck there. That means that unless you dynamically create/modify the package, it cannot be done. A workaround would be storing the config in a database and use the likes of sys variables to choose which config to use.
š
August 1, 2014 at 12:23 pm
I'm using VS 2008 BIDS.
___
Known Is An Drop,Unknown Is An Ocean....
Njoy Programming š
August 1, 2014 at 12:28 pm
windows_mss (8/1/2014)
I'm using VS 2008 BIDS.
No option to do dynamic file config from within the package then, either dynamically modified/created package or database configuration are your best bets. If you need any help with these, just ping back (and ask for Koen:-D).
š
August 1, 2014 at 4:47 pm
At a previous employer we established a fixed directory on the c: drive of our development and production Data Warehouse servers. This fixed directory contained an XML configuration file that was used by our SSIS packages to point to where the actual configuration files resided on each server since this was different between development and production. All our packages looked in this directory to determine where to look for the actual configuration files.
You could also use a system variable to contain the same information regarding the location of configuration files. We went with the XML file as it was easier to maintain and allowed us to expand locations depending on information in the package as well. IIRC when using a system variable you can only point to one location. You would have to verify that to be sure.
August 1, 2014 at 5:21 pm
Lynn Pettis (8/1/2014)
You could also use a system variable to contain the same information regarding the location of configuration files. We went with the XML file as it was easier to maintain and allowed us to expand locations depending on information in the package as well. IIRC when using a system variable you can only point to one location. You would have to verify that to be sure.
This is correct. We use that in our environments as we use a dedicated SSIS Server with the configuration table on that. You can, however, have multiple system variables setup and have the configuarions link differently. I don't use XML configs however, but I know I've setup multiple data sources for the configurations via 3 different environmental variables, then had the rest of the configs read from different sources based on which data source they inherit from.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
August 2, 2014 at 6:02 am
Evil Kraig F (8/1/2014)
Lynn Pettis (8/1/2014)
You could also use a system variable to contain the same information regarding the location of configuration files. We went with the XML file as it was easier to maintain and allowed us to expand locations depending on information in the package as well. IIRC when using a system variable you can only point to one location. You would have to verify that to be sure.This is correct. We use that in our environments as we use a dedicated SSIS Server with the configuration table on that. You can, however, have multiple system variables setup and have the configuarions link differently. I don't use XML configs however, but I know I've setup multiple data sources for the configurations via 3 different environmental variables, then had the rest of the configs read from different sources based on which data source they inherit from.
The only XML file we had was the one on the C: Drive (actually in its own directory on the C: drive). All the other configuration information was stored in a dedicated SQL database on each server. One thing we hadn't implemented was encryption for the passwords. Most of the connections in the configs, though, were trusted configs. Not sure if that was any better, but the only people who knew the passwords were the DBAs. Network servers had no access the any of the SQL Server instances on the servers we supported. Granted, they could change a password or add themselves to the DBA group in AD and gain access, but I wasn't go to tell them that.
June 20, 2019 at 10:58 am
Hi,
Could you kindly help. Can this be done on Vs 2017 in SSIS please? Trying to create a config file using a db. Thanks in advance.
June 21, 2019 at 6:14 am
I am sure it can, unfortunately it has been over nine years since I did anything with SSIS so my knowledge is not what it used to be.Ā One of those things you tend to forget when you no longer work with the technology.
July 12, 2019 at 11:23 pm
I'm not sure i fully understand but you can modify the command line in the job for the dtexec call and provide a config file path but its not dynamic, but you could setup multiple jobs running the same package using different configs.
Why do you want the config to be dynamic? So you want to run the job in the morning with one config but in the evening with a different one or something like that?
Based on your post you indicate an attempt to use a relative path for the config file, relative to what, the deployment folder? Are you saying you want a package from folder X to use one config and folder Y to use a different config where the config used depends on where the package get deployed?
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply