Hi all,
I am pretty new to SSIS and i found some, (to me) unexpected behaviour. Maybe you guys can help me out understanding it.
I am currently building a multi package ETL solution, that uses parent-package configurations to "distribute" variable values from the "root" package to the lower level and "leaf" packages. Each package contains some 8 parent-package variables.
When i ran the entire solution (i.e. the whole tree) I found that some packages aren't getting the correct values for some of their variables. It seems that if a parent-package configuration that wasn't configured correctly (misspelled parent variable name in this case) blocked the other parent-package configurations in the same package from evaluating. When i moved the correct parent-package configuration to execute prior to the incorrect configuration, it ran just ok.
So apperently parent-package configurations are evaluated one by one, and if one of them fails, the "later" configurations aren't evaluated any more.
Is this a feature? or a bug?
Why don't i get a warning in the error list? Should i maybe configure my BIDS in a different fashion?
Hope someone can help me out.
Cheers,
Tom Kronenburg
Tom,
I am not aware of that behaivor using parent-package variables. What I know though is that parent package based configurations are allways resolved in the last place no matter how 'high' they are in the package configuration wizard; which may yield unexpected results if any other configuration depends on a parent-package variable one.
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=264502
|||Rafael,
Thanks, but that was not really what i had problems with. I have only parent-package variables, and the order in which they are presented in the "Package configuration organizer" does present some problems.
E.g. My first parent package configuration has a reference to a variable with a different datatype then expected. (i.e. the configuration CustNo expects an int, and gets a string)
The second parent package configuration is correct.
The third parent package configuration expects a variable with a different name (e.g. it expects to get a variable CustNam and the parent only provides CustName
The fourth is correct again.
When running this package, it will fail 1 and 3, evaluate 2 correctly and never evaluate (is that the correct term?) 4.
In the progress tab i will see warnings for the failure of 1 and 3, and a notice that 2 is evaluated correctly, but i will never see any mention of 4.
I guess it's a bug, but it just might be intended to work that way and somewhere the properties of my bids are not set correctly.
Tom
|||I just reproduced the issue you described. It looks like any parent package variable that comes after an invalid one (when the warning message is: Configuration from a parent variable "xxx" did not occur because there was no parent variable. Error Code: 0xC0010001) is just ignored.
I would suggest to open a bug in the SQL Server connect site http://connect.microsoft.com/SQLServer/Feedback ; if you do so, place a link here so others can validate and vote.
[Microsoft follow-up]
|||The bug is reported, vote through https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=276366
|||Tom,
I have unmarked this thread as answered so it can show up in the Microsoft follow up report.
BTW, thanks for openning the bug in the connect site, I have casted my vote
|||This is a bug and we are aware of it. The bug will be fixed in the next release.
If you need a hotfix for the problem, please contact CSS
|||Greetings,
This is a known issue; the fix for the bug has been implemented and should be available in an upcoming release of SQL Server.
-David
sql
No comments:
Post a Comment