October 23, 2008 at 3:11 am
First of all, hello to all from a newcomer to this forum!!!
Sooo... I opened this package i was working in ssis, and then found that most of the arrows were gone. This hasn't been the first time this has happened to me, but in this case, there's a restriction by function for each of the parallel dataflows. It is meant to avoid duplicating any data load process in the parallel tasks and i want it to be visible for maintenance purposes. the expression is this one : ((@cont+@Id_carga)%@N_cargas)==0&&@N_cargas>=@Id_carga
Let me show you what is being drawn:
So... any clues on a fix for this? are you experiencing this or am i the only one? it there any available patch? How could the restriction between the two modules be edited then?
Thank you VERY much!!!
Francisco Isla.
October 25, 2008 at 6:31 am
Absolutely nobody has a clue on this and/or has never happened to anyone?
Thanks in advance.
November 3, 2009 at 9:44 am
my arrows are sometimes invisible to... any clues?
November 3, 2009 at 11:09 am
Hi,
Under my indication, a new bug was opened in Microsoft connect back then. They acknowledged the z-order problem in the rendering and scheduled it to be fixed for the next revision with a major GUI revamp.
That was a few weeks ago... so... Does that mean we're out of luck and we shall wait for BIDS 201*??
Please, anyone experience this, go to the case url https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=377714
There you can do many things to raise the importance of the bug so that they might consider patching the current versions. Vote it as important / add a coment (like i just did), mark a "I can replicate it"... if you can spare two minutes, please do it, and it might help.
Regards,
Francisco.
November 3, 2009 at 11:31 am
No clue. I haven't run into this problem and neither have any of my coworkers so far either.
I'm interested if you should learn more about this problem.
November 3, 2009 at 11:46 am
Lynn Pettis (11/3/2009)
No clue. I haven't run into this problem and neither have any of my coworkers so far either.I'm interested if you should learn more about this problem.
Well, in the two years i've been developing in BIDS I've learnt how to co-habitate with the problem. So far it has been a piece of cacke to make it shows its tail in XP and 2003server (32 and 64 bits). Microsoft has acknowledged the problem and says it will be fixed in the next major release. For complex packages (3 or more levels of nesting) is definetely a showstopper, especially when using the container restrictions as a core part of the control flow logic for parallelizing loads. In there, you NEED to know that there's a restriction and its logic, and it's a pain to maintain.
Regards,
Francisco.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply