Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

SSIS Properties Expand / Collapse
Author
Message
Posted Tuesday, February 1, 2011 8:45 PM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: 2 days ago @ 6:49 PM
Points: 389, Visits: 1,042
Comments posted to this topic are about the item SSIS Properties

Andy Leonard
CSO, Linchpin People
Follow me on Twitter: @AndyLeonard
Post #1057176
Posted Tuesday, February 1, 2011 8:46 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 5:52 PM
Points: 2,270, Visits: 3,789
I was not sure about the answer. Just guessed it and got it right

Mohammed Moinudheen
Post #1057177
Posted Tuesday, February 1, 2011 11:29 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, May 31, 2013 4:24 AM
Points: 1,417, Visits: 197
Was expecting some reference to support. Still not sure about the answer.

Thanks,



Thanks,
Ashesh


Post #1057205
Posted Wednesday, February 2, 2011 1:14 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 12:53 AM
Points: 2,502, Visits: 2,384
I think that the answer is FALSE, because the question asks
you CANNOT override a property from the command-line.


Then, the explanation says that
the command line always “wins”
, that means you CAN override a property.

http://msdn.microsoft.com/en-us/library/ms162810.aspx
Post #1057241
Posted Wednesday, February 2, 2011 1:23 AM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Today @ 6:19 AM
Points: 3,917, Visits: 5,109
Carlo Romagnano (2/2/2011)
I think that the answer is FALSE, because the question asks
you CANNOT override a property from the command-line.


Then, the explanation says that
the command line always “wins”
, that means you CAN override a property.

http://msdn.microsoft.com/en-us/library/ms162810.aspx


The answer, in context, states that, in SSIS 2005, the command line always “wins”, bit with SSIS 2008, the configutation "wins"


____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
Post #1057248
Posted Wednesday, February 2, 2011 1:26 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 5:25 AM
Points: 939, Visits: 885
Not sure about this. Please explain.

The /Conf[igFile] parameter of dtexec

Specifies a configuration file to extract values from. Using this option, you can set a run-time configuration that differs from the configuration that was specified at design time for the package. You can store different configuration settings in an XML configuration file and then load the settings before package execution by using the /ConfigFile option.

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. To understand how package configurations are applied, see Package Configurations and Behavior Changes to Integration Services Features in SQL Server 2008 R2.


and also SET Option

The following shows how to use the /SET option, which lets you change the value of any package property or variable when you start the package from the command line.


Details here: http://msdn.microsoft.com/en-us/library/ms162810.aspx

Regards,
Iulian
Post #1057249
Posted Wednesday, February 2, 2011 1:59 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:26 AM
Points: 13,622, Visits: 10,509
Difficult question, but surely nice to know. Good work Andy!

Regarding the speculations about the correct answer being False, read the following BOL page:

http://msdn.microsoft.com/en-us/library/ms141682.aspx

At the section Understanding How Package Configurations Are Applied at Run Time, the steps are described in which order the configurations are applied.
It says literally:


However, these command-line options do have some restrictions:
* You cannot use the /Set or the /Connection option to override single values that are also set by a configuration.
* You cannot use the /ConfigFile option to load configurations that replace the configurations that you specified at design time.


Furthermore, the section links to a MSDN page with behaviour changes from 2005 to 2008. There is explicitly stated (as mentioned by Andy in the explanation):


In SQL Server 2005 Integration Services, events occur in the following order:
1.The utility first applies the design-time configurations. (Design-time configurations are the configurations that you created and associated with the package when you designed the package in BI Development Studio.)
2.The utility then applies the run-time options that you specified on the command line when you started the utility.

In SQL Server 2008 Integration Services, events occur in the following order:
1.The utility first applies the design-time configurations.
2.The utility then applies the run-time options that you specified on the command line when you started the utility.
3.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.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1057259
Posted Wednesday, February 2, 2011 4:24 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Yesterday @ 11:26 AM
Points: 8,718, Visits: 9,266
I am thoroughly confused, and must do some more reading.

Here's what MSDN Understanding Integration Services Package Configurations says:
In SQL Server 2008 Integration Services, package configurations are applied twice, before and after applying the options of the DTExec command prompt utility. This should be seen as an improvement, since you can now use the /SET, /CONF or /CONN options of the DTExec utility to alter the original definition of the configurations.

That seems to state quite clearly that you can now (in 2008) do more with the command line than in 2005.

But this is contradicted elsewhere: dtexec Utility says when describing the /configfile option
Specifies a configuration file to extract values from. Using this option, you can set a run-time configuration that differs from the configuration that was specified at design time for the package. You can store different configuration settings in an XML configuration file and then load the settings before package execution by using the /ConfigFile option.
but then goes on to say
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.

Those two statements come one right after the other: "You can change things"; "You can't change things, just add things that you didn't previously specify". One can only wonder whether the authors are doing their best to confuse!


Tom
Post #1057339
Posted Wednesday, February 2, 2011 5:03 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, July 4, 2014 9:03 AM
Points: 1,415, Visits: 796
So, is the correct answer 'FALSE'?
Post #1057374
Posted Wednesday, February 2, 2011 5:07 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:26 AM
Points: 13,622, Visits: 10,509
paul s-306273 (2/2/2011)
So, is the correct answer 'FALSE'?


No, it is TRUE.

You cannot use the /Set or the /Connection option to override single values that are also set by a configuration.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1057380
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse