Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS Properties


SSIS Properties

Author
Message
Andy Leonard
Andy Leonard
Mr or Mrs. 500
Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)Mr or Mrs. 500 (539 reputation)

Group: General Forum Members
Points: 539 Visits: 1092
Comments posted to this topic are about the item SSIS Properties

Andy Leonard
Data Philosopher, Enterprise Data & Analytics
M&M
M&M
SSCrazy
SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)SSCrazy (2.6K reputation)

Group: General Forum Members
Points: 2597 Visits: 3898
I was not sure about the answer. Just guessed it and got it right :-)

M&M
Ashesh
Ashesh
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1423 Visits: 197
Was expecting some reference to support. Still not sure about the answer.

Thanks,


Thanks,
Ashesh

Carlo Romagnano
Carlo Romagnano
Hall of Fame
Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)Hall of Fame (3.6K reputation)

Group: General Forum Members
Points: 3632 Visits: 3237
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
Stewart "Arturius" Campbell
Stewart "Arturius" Campbell
SSCertifiable
SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)SSCertifiable (5.8K reputation)

Group: General Forum Members
Points: 5834 Visits: 7143
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”
Iulian -207023
Iulian -207023
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1200 Visits: 1226
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
Koen Verbeeck
Koen Verbeeck
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16558 Visits: 13210
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 SQLKover.

MCSA SQL Server 2012 - MCSE Business Intelligence
TomThomson
TomThomson
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10787 Visits: 12026
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

paul s-306273
paul s-306273
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1928 Visits: 1061
So, is the correct answer 'FALSE'?
Koen Verbeeck
Koen Verbeeck
SSCoach
SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)SSCoach (16K reputation)

Group: General Forum Members
Points: 16558 Visits: 13210
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 SQLKover.

MCSA SQL Server 2012 - MCSE Business Intelligence
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search