Has anyone seen precedence constraints disappear in a package after closing and opening again? In this case, it's not package-wide. Only constraints inside one Foreach Loop container disappeared. Any idea what causes this to happen? p.s: Yes, I did Save All.Most of these contraints were saved in the package formore than aweek anyway.

I have not seen that. Is your package under any source control software? is that the case compare it against previous versions. A similar issue has been reported for many of us; but theproblem was inside theDataflow (when using VSS as source control)though....

Hi M. Glenn, Yep, I've seen it too. I've seen this and other strange behavior when my Visual Studio environment has been running for days on end (it happens...). My solution is to shut it down and restart the environment. Sometimes the metadata for the objects remains out of sync and the only way to get it back is to either copy it and paste it into anew package or recreate it. Hope this helps, Andy

M.Glenn wrote: BTW, I'm using VS 2005 Pro--installed after SS05/BIDS. I wonder if those using BIDS without a full VS 2005 install are experiencing this issue. Actually, Im impressed with how stable SS05 and VS05 are--especially considering how much more complex and feature-filled these products are compared to their predecessors. Oh my word. A realist! Thanks M Glenn. You've restored my faith in the community following some particularly galling diatribes of late!

Jamie, those guys must not realize how much progress these products have made in terms of functionality, stability, performance and ease-of-use features (although overall complexity is an unavoidable companion of added functionality). Add to this a world-class customer feedback/support infrastructure (including newsgroups like this one). We all have complaints about Microsoft, but that shouldn't completely blind someone to what's been accomplished here. The SS and VS "2005" releases are nothing short of amazing. And whoever thought of selling SS05 Developer Edition for $50 is a genius. A year ago I couldn't even get our CIO to spring for that. Ironically, there are so many compelling reasons to upgrade it created a problem of how to fit it all in an executive summary. But DBA's and developers could recognize something special early on. I shelled out $50 from my own pocket and got wowed right off the bat just watching the install routine! Before long I was hounding the CIO without mercy. He eventually gave in when some funds came available. Recently, I automated report creation, delivery and notification to 40+ healthcare providers with an SSIS package so simple it would make folks who hang out here yawn. But it made me and the CIO look like geniuses. That's what I call progress!

Hi M.Glenn, Cool! I have to agree with Jamie - it's nice to read about someone's successes with the product. The forum is similar to a doctor's office - no one shows up and says "Hi folks, everything's fine! See ya!" They usually pop in when something bad is happening or about to happen. Thanks,Andy

Andy Leonard wrote: The forum is similar to a doctor's office - no one shows up and says "Hi folks, everything's fine! See ya!" They usually pop in when something bad is happening or about to happen. Good analogy. Helps keep the complaints in perspective.

I had this problem today (yes June 2009!), I have VS.Net 2008 with VSS. it appears to be a display issue, I had to move the tasks inside the Foreach loop container right and left, until the arrows(precedence constraints) are back. The other option is to recreate the package from scratch but this is expensive and you may lose some of your code if you do not memorize what you had there in this package.

That problem shows up whenever I nest containers 2 or more levels deep(ForEach, Sequence, For Loop, etc). The constraints are still there (i.e. you get an error if you try to add one) just not rendered on the display surface. There are no other side effects other than the lack of display. To get them to display again just select the object and then click on the objects perimeter near the small green arrow, then the constraint will redraw. You don't need to actually move the object. A PIA but not a show stoper

yes exactly, I have one loop that contains a sequence container, the disappearance of precedence constraints is inside the sequence container (I have about 7 tasks there). in my case, I have to completely move the task around to fix the display issue.

Hello,I have the same issue here. But not with BIDS 2005 but with BIDS 2008. So not the full VSS version.Indeed the issue appearswhen Ihave a ForEach Loop with a Sequence container in it. Replacing the taks makes them appear again until I reopen the packes.My quick solution in this case is to pick up de SEQC container and drag it out of the FELC and then put it back... in again. I still hope for a better solution from Microsoft....I see that there has been a connect issue for SQL 2005 (BIDS), it says a hotfix should be availble soon... why is the issue still here?https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=383138&wa=wsignin1.0

one of the most annoying complaints that i frequently come across in the ssis dev community is: SSIS SUCKS! that's all! no reasoning behind it. no problem description. it is usually after a little prying that i find out that the complainer has little to no experience with ssis.Duane Douglas, MCAD, MCITP | http://www.ssisbi.com | Please mark the post(s) that answered your question.

Yes, this is still an issue. I first encountered it waaaayyyy back when SQL 2005 was initially realeased. Now it's rearing its ugly head again. The task connectors don't render, even though they are still there. DON'T PANIC! DON'T PANIC! DON'T PANIC! DON'T PANIC! DON'T PANIC! As it has already been stated, just select the first of the two tasks and move it until the connector reappears. If you're use an expression constraint and have the blue fx icon that appears next to the connector, zooming in and out may result in having the icon rendering several times larger than it should. Clicking on the connector will bring it back down to normal size. Also, sometimes it can get just plain stupid. We're actually using it with Team Foundation Server, so it's easier to maintain backup. I've had issues where after checking out the package, it tells me that there's an invalid reference to an object and that it can't find it. Appearantly the real issue was with all of the data making it from the server to my PC. I closed out of Visual Studio, re-opened it, re-loaded the package and PRESTO! No more invalid reference. The most important thing is to not panic. It's also helpful to keep copies of queries and script code in separate files outside of the actual package. Screen shots can also be helpful if you do find yourself having to redo an entire package from scratch. - Computers are stupid.