375 reputation
38
bio website
location
age
visits member for 2 years, 4 months
seen Oct 2 '13 at 20:29

SQL Server DBA in York, PA


Sep
24
awarded  Autobiographer
Aug
21
awarded  Enlightened
Aug
21
awarded  Nice Answer
Oct
25
awarded  Notable Question
Oct
20
awarded  Student
Jul
23
awarded  Popular Question
Jun
13
awarded  Yearling
Apr
22
comment How to override SSIS 2008 package config file path?
I'm starting to think MS is lying and you can't actually use /SET to change the design-time config file location.
Apr
22
comment How to override SSIS 2008 package config file path?
the problem is, that syntax /SET \Package.Configurations[Config].Properties[ConfigurationString];"' + @FileName + '"' doesn't work. Give it a try and you'll see. None of the /SET options in the connect link you posted work. The people in that thread are trying to find the same thing I am, nobody seems to know the syntax for /SET to change the config location.
Apr
22
comment How to override SSIS 2008 package config file path?
That's not very clean though, it will generate warnings about the missing config file.
Apr
22
comment How to override SSIS 2008 package config file path?
@Marian agreed they are. This very reason "if the original config file does exist, then the value is taken from the config file and even the /SET is ignored (this is used only in the case above);" is exactly why I need to use /SET to change the config file location, so it doesn't go looking for the original dev path. Microsoft says you're supposed to be able to "Use the /Set option at run time to load package configurations from a location other than the location you specified at design time" I just need to figure out how to do that, nobody seems to know!
Apr
22
comment How to override SSIS 2008 package config file path?
Yes, using /CONF you can specify a run-time configuration that differs from the configuration specified at design time, however that wording is confusing. It should say "a run-time attribute", because the word configuration is ambiguous. I promise you, if you have a config file that you created at design time that changes an attribute of something, you can not change it again with a file specified by /CONF. The values in the design-time config will override it. That's why you have to use /SET to change the config file path instead. It's all in the documentation I posted.
Apr
22
comment How to override SSIS 2008 package config file path?
More supporting evidence from here: You can use the /Connection or /Set option at run time to load package configurations from a location other than the location that you specified at design time.
Apr
22
awarded  Critic
Apr
22
comment How to override SSIS 2008 package config file path?
/CONFIG will not override the attributes that were set by the config file that was specified at design-time. The idea behind my deployment model would be that the developers would build their package and create a config file with test values in it, most likely that file will be on a test file share. When their package is released it will be saved to the SSIS server and the job that calls it will /SET the config file to point to a different file that contains prod settings.
Apr
22
asked How to override SSIS 2008 package config file path?
Dec
15
awarded  Nice Answer
Dec
14
awarded  Supporter
Dec
14
comment Profiler TextData output is null
The duration it shows is for the total connection duration.
Dec
14
answered Profiler TextData output is null