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 for more than a week 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 the problem was inside the Dataflow (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 a new package or recreate it.
Hope this helps,
Andy
|||Thanks for the quick replies. "...Visual Studio environment...running for days on end": Yeah that's me alright. We're not using any source control utilities, but I was in the habit of leaving VS open for days while working on projects. Not any more. I save frequently, but obviously that's not enough.
I could see and edit the constraints in Package Explorer, and tasks that allow only one connection would correctly return an error if I tried to add another constraint, but they were invisible in Control Flow designer. Closing and restarting the project and/or VS didn't help. Selecting all tasks in the container and dragging them outside the container made the connecters visible again. Then just drag everything back and all is well. Thanks for the tip.
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, I’m impressed with how stable SS05 and VS05 are--especially considering how much more complex and feature-filled these products are compared to their predecessors.
|||
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, I’m 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
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.
没有评论:
发表评论