May 5, 2011 at 2:32 pm
dg227 (5/5/2011)
1. (in SSIS 2008) create a package with a variable set to X ... output this variable name and value to a file, email, or whatever, so that you can verify it when executed2. create/add a config file to the package with that variable, also set the value to X
3. save & deploy the package
4. after deploying the package (which has the saved value of X), change the config file so that the variable is now set to Y in the xml file
5. run dtexec on the command line, use the /CONFIG switch to point to that config file with the updated value of Y
That's correct.
From here:http://msdn.microsoft.com/en-us/library/ms162810(v=SQL.100).aspx
You can use the /ConfigFile option to load additional configurations at run time that you did not specify at design time. However, you cannot use the /ConfigFile option to replace configured values that you also specified at design time.
What you want to do is use /set, not /config.
From here:http://msdn.microsoft.com/en-us/library/bb500430.aspx
In SQL Server 2008 Integration Services, events occur in the following order:
The utility first applies the design-time configurations.
The utility then applies the run-time options that you specified on the command line when you started the utility.
Finally, the utility reloads and reapplies the design-time configurations.
Because the events occur in this order, you can dynamically redirect a configuration by using the /SET command-line option to change the configuration string.
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
May 5, 2011 at 2:42 pm
Yup - I've seen that.
Are you able to get that to work to /SET a configuration file when using dtexec? In testing, I can use that to work and set specific, individual variables, but never managed to get it to work and /SET a configuration file path/connection/string at run-time, despite BOL saying it can be used for that. However, I haven't seen an example of anyone actually using this successfully ... have you? If so, what's the exact syntax?
In the end, by not being able to use the /SET switch with a config file, and with the /CONFIG switch option effectively nixed (or, is it 'nuked' in 2008? lol), we made the switch to table configs, which work great, but I'd be interested to see a successful use of /SET with a config file.
Please let me know - thanks!
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply